Hedera Mainnet and Testnet are now supported on the main Sourcify instance at sourcify.dev, the same decentralized, open-source verification service used by many EVM chains. Developers deploying smart contracts on Hedera can verify them using standard tooling with no custom plugins or Hedera-specific configuration required. Existing verification workflows will continue to work uninterrupted.
What This Means for Hedera Developers
Hedera Mainnet (chain ID 295) and Testnet (chain ID 296) are now listed as supported chains on sourcify.dev. Standard EVM developer tooling works for Hedera contract verification without modification. Any smart contract verified on Sourcify will be shown as verified on Hash-Scan.
Hardhat – the standard @nomicfoundation/hardhat-verify plugin works with Hedera, using the default Sourcify verifier.
npx hardhat verify --network hedera_testnet Foundry – forge verify-contract works with the default Sourcify verifier, with no custom verifier URL required.
forge verify-contract $CONTRACT_ADDRESS src/MyContract.sol:MyContract \
--chain-id 296 \
--verifier sourcify
Remix IDE – the built-in Sourcify verification integration works for Hedera contracts with no additional configuration.
Direct API – Sourcify’s REST API supports Hedera chains for programmatic verification, enabling CI/CD integration and automated verification pipelines.
# Verify a contract on Hedera Mainnet
curl -X POST "https://sourcify.dev/server/v2/verify/295/0xYourContractAddress" \
-F "files=@MyContract.sol" \
-F "files=@metadata.json"
# Retrieve verified contract data
curl "https://sourcify.dev/server/v2/contract/295/0xYourContractAddress?fields=all"
What is Sourcify?
Sourcify is a decentralized smart contract source code verification service.It accepts Solidity source code, recompiles it with the original compiler settings, and compares the output against the deployed on-chain bytecode. If the bytecodes match, the contract is verified, and its source code becomes publicly accessible through the Sourcify repository.
Sourcify supports two levels of verification:
- Exact Match – the recompiled bytecode matches the on-chain bytecode byte-for-byte, including the CBOR-encoded metadata hash. This cryptographically proves that the exact source files and compilation settings were used.
- Partial Match – the bytecodes are functionally identical but differ in the metadata hash portion, which can change due to differences in comments, variable names, or file paths.
Ecosystem-Wide Visibility
Contracts verified on sourcify.dev are visible across the broader EVM verification ecosystem. Any tool, explorer, or analytics platform that reads from the Sourcify repository, including HashScan can surface verified Hedera contract source code. With main instance support, Hedera contract verifications now participate in the same shared ecosystem alongside many EVM Chains meaning that verifications are seamless as they require no additional configuration to verify deployed contracts on Hedera.
Sourcify also co-leads the Verifier Alliance alongside Blockscout and Routescan, a shared database of verified contracts with over 100,000 entries. As Hedera contracts are verified on the main instance, they become part of this cross-chain verification dataset meaning no custom configuration for builders along with being able to view their verified contracts on any supported chain from one place.
Getting Started
Developers can now verify Hedera smart contracts on the main Sourcify instance today. The verification workflow is identical to other supported EVM chains.
To deploy and verify a smart contract on Hedera using Hardhat or Foundry, follow the step-by-step tutorials in the Hedera documentation:
For direct API access, the Sourcify API documentation and supported chains list are available at docs.sourcify.dev.
Manual verification on Hash-Scan will now redirect you to the main Sourcify instance verification page where you will be able to select Hedera Mainnet (295) or Hedera Testnet (296) to verify your smart contract by uploading the smart contract files for verification. This verification will be reflected on Hash-Scan.
