Skip to content
Glossary

Verified Source Code

Verified source code is a contract's human-readable code matched against its on-chain bytecode on a block explorer -- it confirms what's deployed, not that the code is safe.

Verified source code is a smart contract’s human-readable source code that has been submitted to a block explorer and automatically matched against the compiled bytecode actually running on-chain. Once verified, anyone can read exactly what the deployed contract does.

Why it matters

Verification turns an opaque contract into a readable one, letting anyone — not just the deployer — check what functions exist, who can call them, and whether the contract’s behavior matches what a project claims about it.

What it doesn’t prove

Verified source code confirms the published code matches what runs on-chain; it does not confirm the code is safe, free of bugs or hidden logic, or has been reviewed by anyone independent. A contract can be fully verified and still contain a deliberate trap or an exploitable flaw — verification and a security audit are different things.

Example

A reader checks a token’s contract page on a block explorer, confirms the source code is marked verified, and reads the transfer function directly to check for an unusual tax or blacklist logic that might not match the project’s public description of the token.

About the author

The Crypto Online Editorial Team

A collective byline for a claim-verification desk. Every piece is human-edited and checked against a primary record; AI assistance is disclosed in our editorial guidelines.

All work by the team → Methodology Corrections

Not financial advice. Human-edited; AI-assisted drafting is disclosed in our editorial guidelines. Spotted an error? See how corrections work.