Skip to content

Update smart contract verification documentation to include Sourcify support #116

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Nov 12, 2025
+5 −5
Merged

Update smart contract verification documentation to include Sourcify support #116

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
6582a65
Update smart contract verification documentation to include Sourcify …
alcuadrado Oct 31, 2025
ced656d
Apply suggestion from @Copilot
schaable Nov 3, 2025
a933522
Apply suggestion from @Copilot
schaable Nov 3, 2025
6c014ec
Apply suggestion from @manuelwedler
schaable Nov 3, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions src/content/docs/docs/guides/smart-contract-verification.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ sidebar:
import Install from "@hh/Install.astro";
import Run from "@hh/Run.astro";

Smart contract verification is used to prove that a deployed contract's bytecode comes from a specific source code. This allows users and tools to inspect the original source on block explorers, like Etherscan and Blockscout.
Smart contract verification is used to prove that a deployed contract's bytecode comes from a specific source code. This allows users and tools to inspect the original source on block explorers, like Etherscan and Blockscout, and verification services, like Sourcify.

In this guide, you'll learn how to verify your contracts using the `hardhat-verify` plugin.

Expand Down Expand Up @@ -64,7 +64,7 @@ In the previous version of the Etherscan API, you needed a different API key for

:::

To verify contracts on Blockscout, you don't need to set an API key, nor any config.
To verify contracts on Blockscout and Sourcify, you don't need to set an API key, nor any config.

You can also disable a block explorer by setting its `enabled` property to `false`. For example, you can disable Blockscout verification like this:

Expand Down Expand Up @@ -112,13 +112,13 @@ If you want to use a different build profile, you can pass the `--build-profile`

## Verifying contracts on different block explorers

The plugin currently supports Etherscan and Blockscout. You can use subtasks to verify on each of the block explorers:
The plugin currently supports Etherscan, Blockscout, and Sourcify. You can use subtasks to verify on each of the block explorers:

<Run command="hardhat verify etherscan ..." />

They have the same interface, but verify on a different block explorer.
These subtasks have the same interface, but verify on different services.

Running `verify` without any subtask will verify on both Etherscan and Blockscout.
Running `verify` without any subtask will verify on Etherscan, Blockscout, and Sourcify.

## Verifying on a block explorer of a different network

Expand Down