Verifying contracts and Debugging

Verifying Contracts

After you deploy your smart contracts to Katana (mainnet) / Bokuto (testnet), you will want to verify them on the block explorer.

Verifying contracts on Katanascan

1. You will need Foundry nightly release
2. You will need Etherscan’s multichain API key
3. Don’t use --verifier-url, but use instead the chain name; example:

forge verify-contract --watch --chain katana 0xc094c224ce0406bc338e00837b96ad2e265f7287 src/GmWorld.sol:GmWorld --verifier etherscan --etherscan-api-key YourEtherscanApiKey

Verifying contracts on Blockscout

You can either follow Blockscout’s instructions for e.g. Foundry, Hardhat, or do it through the UI.

You will need the Blockscout URL for the environment you’re targeting:

• Katana Blockscout Explorer
• Bokuto Blockscout Explorer

Debugging

Katana has Tenderly as one of its infrastructure partners. This means you can leverage their transaction debugging and simulation tooling.

Here’s an example of a failed transaction and associated stack trace.