How does Sourcify compare to Etherscan verification?

Sourcify is open-source and focuses on full verification using Solidity metadata, promoting transparency and standards, while Etherscan is a proprietary service often used for partial verification with a centralized platform.

How to verify a contract on Sourcify?

Use the web UI at sourcify.dev for manual submission, or integrate via the API. Ensure your contract includes Solidity metadata for full verification, as detailed in the documentation.

Does Sourcify support Vyper contracts?

Yes, Sourcify supports both Solidity and Vyper contracts, with compiler wrappers for both languages, as mentioned in the README under supported compilers.

What is full verification in Sourcify?

Full verification leverages the Solidity metadata hash to ensure the deployed bytecode exactly matches the source code, unlike partial verification which may only check for functional equivalence.

How does Sourcify's automated monitor work?

The monitor service listens to EVM chains for new contract deployments and automatically submits them for verification if the source code is published on IPFS, as described in the services section of the README.

Can I self-host Sourcify for a private network?

Yes, Sourcify is open-source and can be self-hosted by setting up the server, database, and monitor services, but it requires configuration for custom chains, as per the chain support instructions.

Open-Awesome

sourcify

MITTypeScriptsourcify-server@3.17.1

An open-source service for verifying Ethereum smart contract source code, supporting Solidity and Vyper.

Visit Website GitHub

943 stars535 forks0 contributors

What is sourcify?

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.

Target Audience

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.

Value Proposition

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.

Overview

Source code verification service for Ethereum smart contracts

Use Cases

Best For

Verifying Solidity smart contracts before deployment to mainnet
Auditing smart contracts to ensure source code matches deployed bytecode
Projects requiring transparent and open-source verification tools
Automatically monitoring new contract deployments for verification
Building tools that interact with verified contract metadata
Ensuring compliance with open standards in blockchain development

Not Ideal For

Projects deploying on non-EVM chains like Solana or Cosmos, as Sourcify only supports EVM-compatible blockchains.
Teams requiring commercial support and service-level agreements, since Sourcify is community-driven with no guaranteed response times.
Developers needing quick, partial verification without Solidity metadata, as Sourcify's full verification depends on metadata integrity hashes.
Applications where immediate verification is critical and IPFS publication isn't reliable, limiting automated monitoring effectiveness.

Pros & Cons

Pros

Full Verification Integrity

Uses Solidity metadata and its integrity hash to ensure exact matches between source and deployed code, enabling 'full verification' as emphasized in the README.

Open Standards Commitment

Promotes interoperability through initiatives like the Verifier Alliance, avoiding proprietary silos and fostering transparency across the ecosystem.

Multi-Chain Extensibility

Supports various EVM chains via an extensible server and monitor, with documented instructions for adding new chains, enhancing flexibility.

Automated Deployment Monitoring

The monitor service listens for new contract deployments and auto-submits them for verification if source code is on IPFS, reducing manual effort.

Cons

Complex Self-Hosting Setup

Requires running multiple services (server, database, monitor) in a monorepo, which can be intricate compared to simpler, single-endpoint verification APIs.

Limited Chain Support

Only works with EVM-compatible chains, excluding other smart contract platforms, which restricts its use in broader blockchain ecosystems.

Dependency on IPFS

Automated verification assumes source code is published on IPFS; if not, manual intervention is needed, potentially disrupting seamless automation.

Frequently Asked Questions

Related Projects

orbit-db

Peer-to-Peer Databases for the Decentralized Web

Stars8,798

Forks596

Last commit2 months ago

ipfs-companion

Browser extension that simplifies access to IPFS resources on the web

Stars2,158

Forks338

Last commit1 day ago

Public Gateway Checker

Checks which public gateways are online or not

Stars2,099

Forks383

Last commit1 month ago

ipfs-deploy

Zero-Config CLI to Deploy Static Websites to IPFS

Stars1,171

Forks117

Last commit1 year ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub