Web3 Dictionary Logo
Web3 Dictionary
Contribute

Categories

AllBlockchainDappsDAOsDeFiNFTsRegulationSecuritySmart ContractsTokenomicsWalletsWeb3 GamingOthers
  1. Web3 Dictionary
  2. Security
  3. Verification
Security

Verification

The process of confirming that smart contract source code matches the deployed bytecode on the blockchain.

Last Updated

2026-03-29

Related Concepts

Smart Contract
Web3-Explorer Logo

Web3 Security

AD

Security frameworks, smart contract reviews, and compliance alignment to reduce risk and protect users.

Review Security Services

What is Verification?

Verification is the process of proving that a smart contract's public source code matches the bytecode actually deployed on-chain. Verified contracts display their readable source code on block explorers like Etherscan.

How does Verification work?

  1. A developer uploads source code and compilation settings to a verifier like Etherscan or Sourcify.
  2. The verifier recompiles the code with identical settings and compares the output bytecode to what is on-chain.
  3. If they match, the source code is marked verified and displayed publicly.

Why does Verification matter?

Unverified contracts are black boxes impossible to audit or trust. Verification enables anyone to read the code and confirm it does what the project claims.

Scammers routinely deploy unverified contracts to hide malicious functions.

Key features of Verification

  • Proves deployed bytecode matches published source code
  • Enables public code review by anyone
  • Displayed on Etherscan and other block explorers
  • Standard practice for all credible projects

Examples of Verification

All Uniswap contracts are verified anyone can read the AMM logic on Etherscan. An unverified token contract is a major red flag before providing liquidity or investing.

External References

  • Smart Contract Security
  • OpenZeppelin Security Audits