How to Deploy and Verify a Hedera Smart Contract with Foundry

Discover how to deploy and automatically verify your Hedera smart contract. Learn how to verify a pre-existing contract and check a contracts verification status.

What you will accomplish


Before you begin, you should be familiar with the following:

Also, you should have the following set up on your computer ⬇
Check your prerequisites set up ⬇

Open your terminal, and enter the following commands.

git --version
code --version
node --version
npm --version
forge --version
cast --version

Each of these commands should output some text that includes a version number, for example:

git --version
git version 2.39.2 (Apple Git-143)

code --version

node --version

npm --version

forge --version
0.2.0 (3cdee82 2024-02-15T00:19:38.655803000Z)

cast --version
0.2.0 (3cdee82 2024-02-15T00:19:38.543163000Z)

If the output contains text similar to command not found, please install that item.

Get started

Set up project

To follow along, start with the main branch, which is the default branch of this repository. This gives you the initial state from which you can follow along with the steps as described in the tutorial.

forge manages dependencies by using git submodules. Clone the following project and pass --recurse-submodules to the git clone command to automatically initialize and update the submodule in the repository.

git clone --recurse-submodules
Alternative with `git` and HTTPS

If you haven't configured SSH to work with git, you may wish use this command instead:

git clone --recurse-submodules

Install the submodule dependencies

In your terminal, enter the projects root directory

cd foundry-deploy-and-verify-smart-contract  

Next, run the following command to install the dependencies

forge install

Obtain your ECDSA Hex Encoded Private Key

In order to deploy your smart contract you will need access to your ECDSA hex encoded private key. You can find your ECDSA hex encoded private key by logging into Hedera Portal.

If you need to create a Hedera account, follow the create a hedera portal profile faucet tutorial.

Keep your private key accessible as it will be needed in the following steps.

Choose your Testnet RPC_URL

Choose one of the options over at How to Connect to Hedera Networks Over RPC

Keep the Testnet RPC_URL accessible as it will be needed in the next step.

Deploy and Automatically Verify Your Contract on Hedera Testnet

In your terminal, replace the value of "HEX_Encoded_Private_Key" with your ECDSA account's private key and replace "RPC_URL" with a Testnet URL in the command below:

forge create --rpc-url "RPC_URL" --private-key "HEX_Encoded_Private_Key" --verify --verifier sourcify --verifier-url src/TodoList.sol:TodoList
Example forge create command
forge create --rpc-url --private-key 0x348ce564d427a3317b6536bbcff9290d69395b06ed6c486954e971d960fe87ac --verify --verifier sourcify --verifier-url src/TodoList.sol:TodoList

Sourcify is a Solidity source code and metadata verification tool.

Hashscan is a Hedera Mirror Node Explorer that integrates with Sourcify to provide a verification service located at

Learn more

You should see output similar to the following:

[⠒] Compiling...
[⠔] Compiling 22 files with 0.8.23
[⠘] Solc 0.8.23 finished in 3.43s
Compiler run successful!
Deployer: 0xdfAb7899aFaBd146732c84eD83250889C40d6A00
Deployed to: 0x3b096B1c56A48119CB4fe140F1D26196590aF46C
Transaction hash: 0x32f6a03b569a934d8d1e20bb29a20fe1008f0b3bf9ab41e1f26ed88bb28b3c05
Starting contract verification...
Waiting for sourcify to detect contract deployment...
Start verifying contract `0x3b096B1c56A48119CB4fe140F1D26196590aF46C` deployed on 296

Submitting verification for [TodoList] "0x3b096B1c56A48119CB4fe140F1D26196590aF46C".
Contract successfully verified

Open the Hashscan explorer in your browser by copying the Deployed to EVM address and replacing <Deployed_Contract_EVM_Address> in the link below:<Deployed_Contract_EVM_Address>


You should see a page with:

  • The title "Contract" (1)

  • An "EVM Address" field that matches the value of Deployed To in the output above. (2)

  • A section titled "Contract Bytecode" with a green verified tag. (3)

  • Two tabs titled "Source" and "Bytecode". (4)

Verify A Pre-Existing Contract on Testnet

You may have a pre-existing contract that has not been verified yet.

Deploy a contract without verifying by running this command in your terminal:

forge create --rpc-url "RPC_URL" --private-key "HEX_Encoded_Private_Key" src/TodoList.sol:TodoList

In order to verify a pre-existing smart contract you will need:

  • the contract EVM address with 0x prefix

  • the contract name or path to the contract

  • the chain ID

In your terminal, replace <CONTRACT_ADDRESS> with the contract EVM address you wish to verify.

forge verify-contract --chain-id 296 --verifier sourcify --verifier-url  <CONTRACT_ADDRESS> src/TodoList.sol:TodoList
  • The chain ID for Mainnet is 295.

  • The chain ID for Testnet is 296, which is what you are using.

  • The chain ID for Previewnet is 297.

You should see output similar to the following:

Start verifying contract `0xC08d3Cf01739C713BaD1cf65FD4127CB90550568` deployed on 296

Submitting verification for [TodoList] "0xC08d3Cf01739C713BaD1cf65FD4127CB90550568".
Contract successfully verified

Check Contract Verification Status

In your terminal, replace <CONTRACT_ADDRESS> with the contract EVM address you wish to verify.

forge verify-check --chain-id 296 --verifier sourcify --verifier-url <CONTRACT_ADDRESS>

You should see output similar to the following:

Checking verification status on 296
Contract successfully verified


Congratulations, on completing the tutorial on how to verify smart contracts on Hedera Testnet.

You have learned how to:

Last updated