Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EIP-1167 clones verification, verification with bytecode #189

Open
rapidddenis opened this issue Jun 13, 2024 · 3 comments
Open

EIP-1167 clones verification, verification with bytecode #189

rapidddenis opened this issue Jun 13, 2024 · 3 comments

Comments

@rapidddenis
Copy link

rapidddenis commented Jun 13, 2024

As developer I want to call tenderly.verify() with clone and implementation addresses

@dule-git
Copy link
Contributor

Hello @rapidddenis,

Can you describe the behaviour you want in more detail?
Please provide the beginning state, the expected behaviour and the desired results. 😄

Thanks!

@rapidddenis
Copy link
Author

rapidddenis commented Oct 24, 2024

@dule-git idea is to verify minimal proxies deployed with https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/proxy/Clones.sol which byte code is not part of artifacts (verification task have no clue about it)

@dule-git
Copy link
Contributor

As I understand from your request, you want to have Minimal Proxies verified on Tenderly.

We are already providing this feature by automatically detecting the Minimal Proxies as they are deployed on Tenderly.
Here are some examples of Minimal Proxies that we are verifying without any need for client action:

If you have a case that we are not verifying the Minimal Proxy you have in mind, you can send us the network and address of the proxy and we can route it through our support flow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants