[Contract Verification] Vyper Verification #681
-
EnvironmentTestnet Block ExplorerIssue Type
Contract Addressdoesnt matter Compiler TypeSingle file zkSolc Versionn/a Solc Versionn/a Contract Namen/a Contract Coden/a Constructor Argumentsn/a Hardhat Verify Plugin VersionNo response Repo Link (Optional)No response Additional Detailsmatter-labs/block-explorer#285 It looks like vyper work on the API for the block explorer. Does anyone have an example of this per chance? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
To verify Vyper contracts on the ZKsync Era network using the Hardhat plugin, you need to ensure that the Vyper smart contracts list in your project's "contracts" folder is exactly the same as it was during the deployment of the specific Vyper contract. This is crucial because any discrepancy will result in a "bytecode doesn't match any of your local contracts" error. It's strongly recommended to verify your Vyper smart contracts immediately after their deployment to minimize such issues. For more detailed guidance on using the Hardhat plugin for Vyper verification, you can refer to the hardhat-zksync-verify-vyper documentation. If you are looking for examples of Vyper work on the API for the block explorer, unfortunately, I couldn't find specific examples in the provided documentation. You might want to check the official repositories or community forums for more detailed examples or guidance. Your feedback helps us serve you better. If this fully addresses your question, please give it a thumbs up. If it doesn't, please give it a thumbs down. This will inform the community and team so we can improve our support. |
Beta Was this translation helpful? Give feedback.
Here's an example of how the request looks: