Contracts and verification

All Keel contracts are deployed on Mezo testnet (chain id 31611), and each one has verified source code on the Mezo explorer (explorer.test.mezo.org, a Blockscout instance).

The source of truth for addresses is shared/deployments/testnet.json.

#Current (v2): new guardians and new claim links

#Earlier (v1): existing guardians and links keep working

Each user's guardian is a minimal-proxy clone of an implementation. The explorer shows the clone's code as the verified implementation's.

#Treasury

The protocol share of keeper tips (20% of the tip, hard-capped at 50%) and KeelPro payments go to the treasury set on KeelGuardianFactoryV2 and KeelPro: 0x5C22A7612D3B67C68bA84873F16C01bc06041ADD, today the team's deployer wallet. It's a plain address, not a contract; the admin can point it at a multisig.

#Mezo contracts Keel uses

#How the sources were verified

• Tool: contracts/scripts/verify-blockscout.py submits the exact compiler input hardhat used (standard JSON) to the explorer's verification API.
• Compiler: solc 0.8.24+commit.e11b9ed9, optimizer on with 100 runs, EVM version london, license GPL-3.0.
• Source set: only the files listed in each contract's own metadata, which is the same set solc hashed into the bytecode.
• Constructor arguments: detected from the creation transaction.

python contracts/scripts/verify-blockscout.py              # every contract in shared/deployments/testnet.json
python contracts/scripts/verify-blockscout.py 0x85579b…    # one address

Screenshots of each verified page are in docs/images/verified.