What is deployed
Hedera gives every contract two names: a native 0.0.x id and the
0x EVM address the same bytecode answers to. Both point at one contract,
and HashScan accepts either. A mandate is signed against the EVM address,
because that is what the guard reads when it recovers a signature.
| Contract | Hedera id | EVM address |
|---|---|---|
| MandateGuard | 0.0.10308333 | 0xbe2a2ae52854dabdcb7c22c8be21559a7ac7a391 |
| MandateRegistry | 0.0.10308330 | 0x21a807ed474c79b0a2c3015587f77c8c3a58411c |
| VenueRegistry | 0.0.10308332 | 0xef2f5147a2143550ccf678ad57f782881d74f8cc |
| Intent commitments | 0.0.10309023 | HCS topic — Hedera-native, no EVM address |
Every contract is source-verified. Addresses are read from
packages/contracts/deployments/296.json and never hardcoded: Hedera testnet
can be reset, and one deploy command restores the whole system.