Skip to main content

Vyper Verify

KaiaScan supports verifying Vyper contracts in addition to Solidity.
Vyper contracts are verified through the KaiaScan web interface:

Verification Steps​

  1. Open the contract verification page and enter your deployed contract address.
  2. Set Compiler Type to Vyper.
  3. Select the compiler version used to compile your contract.
  4. Choose a source code format:
    • Vyper (Single File): upload or paste a single .vy source file.
    • Vyper (Standard-Json-Input): upload the standard JSON input (e.g. generated by vyper -f standard_json), which includes multiple sources and compiler settings.
  5. Select the EVM version if your contract was compiled with a non-default target, then submit.

If your contract was deployed with constructor arguments, provide them in the same way as for Solidity verification.

Optimizer settings

Unlike Solidity, there are no optimizer options to configure for Vyper single-file verification. When using Standard-Json-Input, compiler settings are taken from the JSON itself.

Supported Compiler Versions​

Vyper 0.3.0 and later is supported. Contracts compiled with older versions cannot be verified.

Match Types​

Vyper verifications typically result in a partial match.
Vyper bytecode does not embed a full source metadata hash the way Solidity does, so a byte-exact (perfect) match generally cannot be reproduced. A partial match still confirms that the submitted source code compiles to the deployed runtime bytecode.

Tooling Support​

API-based verification through development tools (Hardhat @nomiclabs/hardhat-vyper, Foundry, Brownie, ApeWorX, etc.) is not currently supported for Vyper. The Hardhat Verify and Foundry Verify guides apply to Solidity contracts only.
Please use the KaiaScan web interface to verify Vyper contracts.

Troubleshooting​

If you encounter any issues during the verification process, please contact us through our support page with details about the error.

Contact Support for Contract Verification Issues

Additional Resources​