Contract addresses

The eleven modules a deployment can be composed from, on Robinhood Chain, chain ID 4663. Every module is optional except the treasury and the registry entry.

Activity

How to verify

1. Confirm you are on chain ID 4663. An address is only meaningful together with its chain — the same characters on another network are a different contract, or nothing at all.
2. Read the address from a source you control. Copy it from this page only to compare it against what your own node or your chosen explorer reports.
3. Check the bytecode hash matches the published artifact for that module version, not just the module name.
4. Check the source verification status. A module that reports its source as unpublished has not been verified by anyone, including us.
5. Read the owner and the timelock delay. A module behind AlmeruTimelock cannot be changed without a queued transaction and a visible delay.
6. Simulate any call before you sign it, and confirm the target address in your wallet matches character for character — not just the first and last four.

The threat model these steps come from is in the security model. Module responsibilities are described in protocol architecture, and the programmatic reads are in the REST API and the SDK reference.

Module reference

What each module is for, and which deployments use it, is listed against every entry in the registry. Miner-specific modules are covered in the miner protocol.