Category: smart-contract verification infrastructure / open contract-repository and dataset / self-hostable verifier stack
Summary: Sourcify is best cataloged as open verification and public-data infrastructure rather than as a mere block-explorer feature or contract-verification convenience tool. The official README and docs present a full stack for source-code verification across EVM chains: a verification server API, a reusable verification library, a monitoring service that watches for contract creations, a public contract repository and signature database, browser and UI flows, and a self-hosting path. The strongest categorization clue is that Sourcify is explicitly trying to replace closed, siloed contract verification with an open-source, open-data, open-standards substrate that other verifiers, researchers, and applications can build on.
What it does:
Verifies Ethereum smart contracts and related EVM-chain contracts using Solidity metadata and other supported verification inputs, with support for Solidity, Vyper, and Yul in official materials
Exposes an HTTP verification server and API for submitting source files, standard JSON input, compiler versions, and creation transaction hashes
Ships lib-sourcify as a reusable verification library that developers can embed directly into applications or browser-based flows
Runs a monitoring service that listens for new contract creations on supported chains and auto-submits contracts for verification when metadata is available on IPFS
Maintains an open repository and dataset of verified contracts plus a signature database built from extracted function, event, and error signatures
Provides verification UI flows, repository browsing surfaces, and a documented path for running self-hosted Sourcify infrastructure
Shares verified contract data with other verifiers and positions itself within the broader Verifier Alliance effort rather than as a closed destination product
Key claims:
The official README calls Sourcify a source-code verification service for Ethereum smart contracts and says it is committed to open-source, open-data, and open-standards smart-contract verification
The intro docs argue that dominant verification services are too closed, centralized, and siloed, and explicitly position Sourcify as an antidote to black-box verification and locked-up contract data
The intro docs say Sourcify shares its whole dataset daily in modern data formats, exposes richer artifacts than legacy verifiers, and forwards new verifications to known verifiers through open collaboration efforts
The README says Sourcify leverages Solidity metadata and integrity hashes to find exact matches and fully verify Solidity contracts rather than stopping at looser source-code matches
The docs for the verification UI show support for single-file, multi-file, metadata, and standard-JSON verification workflows, while recommending framework-native or standard-JSON paths to preserve exact compilation inputs
The README breaks the system into a verification server, database, chain monitor, core library, compiler wrappers, UI, and repository browser, which is a much broader operating surface than a one-page explorer verifier
The lib-sourcify README shows a reusable developer-facing package with typed compilation and verification flows, configurable RPC and IPFS gateways, authenticated RPC support, and browser-compatible compiler patterns
Whitepaper: No canonical standalone Sourcify whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official docs, the canonical repository README, and the lib-sourcify package README; see ../whitepapers/sourcify-primary-sources-2026-05-03.md.