An open-source service for verifying Ethereum smart contract source code, supporting Solidity and Vyper.
Sourcify is an open-source service that verifies the source code of Ethereum smart contracts, ensuring that the deployed bytecode on-chain matches the original Solidity or Vyper source code. It solves the problem of trust and transparency in smart contract deployments by providing a reliable verification mechanism. The service supports full verification using metadata integrity hashes and operates across multiple EVM-compatible chains.
Smart contract developers, blockchain auditors, and projects deploying on Ethereum or other EVM chains who need to prove the authenticity and integrity of their contract source code.
Developers choose Sourcify because it is fully open-source and promotes open standards, unlike proprietary verification services. It offers full verification capabilities, automated monitoring, and a commitment to transparency, making it a trusted community-driven alternative.
Source code verification service for Ethereum smart contracts
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Uses Solidity metadata and its integrity hash to ensure exact matches between source and deployed code, enabling 'full verification' as emphasized in the README.
Promotes interoperability through initiatives like the Verifier Alliance, avoiding proprietary silos and fostering transparency across the ecosystem.
Supports various EVM chains via an extensible server and monitor, with documented instructions for adding new chains, enhancing flexibility.
The monitor service listens for new contract deployments and auto-submits them for verification if source code is on IPFS, reducing manual effort.
Requires running multiple services (server, database, monitor) in a monorepo, which can be intricate compared to simpler, single-endpoint verification APIs.
Only works with EVM-compatible chains, excluding other smart contract platforms, which restricts its use in broader blockchain ecosystems.
Automated verification assumes source code is published on IPFS; if not, manual intervention is needed, potentially disrupting seamless automation.