Verify & Publish Contract (Foundry)

This guide verifies and publishes a deployed contract on SATUCHAIN Testnet Explorer using Foundry. Explorer API: https://testnet.satuchain.com/api

---

Requirements

• Contract already deployed on SATUCHAIN Testnet

• Contract address

• Exact compiler settings used at deployment (solc version, optimizer runs, viaIR, evmVersion)

• Foundry installed (forge, cast)

SATUCHAIN Testnet:

• RPC: https://rpc-testnet.satuchain.com

• Chain ID: 17081945

• Explorer: https://testnet.satuchain.com

---

1) Install Foundry (if needed)

curl -L https://foundry.paradigm.xyz | bash
foundryup

Verify:

forge --version
cast --version

---

2) Set Environment Variables

Linux/macOS:

export SATU_RPC_URL="https://rpc-testnet.satuchain.com"
export SATU_API_URL="https://testnet.satuchain.com/api"
export SATU_CHAIN_ID="17081945"

Windows PowerShell:

$env:SATU_RPC_URL="https://rpc-testnet.satuchain.com"
$env:SATU_API_URL="https://testnet.satuchain.com/api"
$env:SATU_CHAIN_ID="17081945"

---

3) Build (Must Match Deployment)

forge build

Important: Your foundry.toml must match the deployment build (optimizer, runs, evm_version, via_ir).

---

4) Verify Contract (No Constructor Args)

forge verify-contract \
  --chain-id $SATU_CHAIN_ID \
  --rpc-url $SATU_RPC_URL \
  --verifier blockscout \
  --verifier-url $SATU_API_URL \
  <CONTRACT_ADDRESS> \
  src/Storage.sol:Storage

Replace:

• <CONTRACT_ADDRESS> with your deployed address

• src/Storage.sol:Storage with your file path and contract name

---

5) Verify Contract (With Constructor Args)

If your contract has constructor params, provide the encoded args:

forge verify-contract \
  --chain-id $SATU_CHAIN_ID \
  --rpc-url $SATU_RPC_URL \
  --verifier blockscout \
  --verifier-url $SATU_API_URL \
  <CONTRACT_ADDRESS> \
  src/MyToken.sol:MyToken \
  --constructor-args <ENCODED_ARGS>

To encode constructor args:

cast abi-encode "constructor(string,string)" "MyToken" "MTK"

Use the output as <ENCODED_ARGS>.

Example:

ENCODED=$(cast abi-encode "constructor(string,string)" "MyToken" "MTK")

forge verify-contract \
  --chain-id $SATU_CHAIN_ID \
  --rpc-url $SATU_RPC_URL \
  --verifier blockscout \
  --verifier-url $SATU_API_URL \
  0xYourContractAddress \
  src/MyToken.sol:MyToken \
  --constructor-args $ENCODED

---

6) Check Verification Status

forge verify-check \
  --chain-id $SATU_CHAIN_ID \
  --verifier blockscout \
  --verifier-url $SATU_API_URL \
  <GUID>

<GUID> is returned by the forge verify-contract command.

---

7) Confirm on Explorer

Open: https://testnet.satuchain.com/address/<CONTRACT_ADDRESS>

You should see the contract marked Verified, with Source Code and ABI available.

---

Troubleshooting

Bytecode mismatch

• Wrong solc version, optimizer settings, runs, viaIR, or evmVersion compared to deployment.

Constructor args incorrect

• Encode args using cast abi-encode and verify they match the original deployment.