Vyper theorytheory 0/50 · 0%
Tooling · hard

40. Deploying and verifying a Vyper contract

From compiled artifact to a verified on-chain contract.

Deployment sends a transaction whose data is the compiled bytecode plus ABI-encoded constructor arguments. Once mined, verification services (like Etherscan) recompile your exact source with the exact compiler version to prove the deployed bytecode matches, so users can read and trust the source.

vyper my_contract.vy -o build/
# produces build/my_contract.json with abi + bytecode

Because Vyper's version pragma is strict, always record the exact compiler version used at deploy time — verification will fail if you later try to verify with a mismatched version.

Check your understanding

  1. 1. What does contract verification prove?

  2. 2. Why must you record the exact compiler version used?

  3. 3. What does the deployment transaction's data contain?