docs: update Mainnet contract addresses for Cobalt

[0xth4nh]

What changed? Why?

Mainnet's public L1 address table still pointed at the pre-Cobalt AggregateVerifier and Nitro verifier, and it omitted contracts the mainnet upgrade deployed. This follows the Sepolia update in #2003.

• Point AggregateVerifier at the live game type 621 implementation.
• Replace NitroEnclaveVerifier with NitroValidator, matching the current Sepolia label, at NITRO_VALIDATOR() on the TEE registry.
• Add CertManager, P384Verifier, and ProtocolVersionsProxy.
• Leave ZkVerifier unchanged. ZK_VERIFIER() on the new AggregateVerifier is still 0xB88D95bDf6972508942d184866890c1834219B75.

Notes to reviewers

AggregateVerifier is gameImpls(621) on DisputeGameFactory (0x43edB88C…), which matches config/mainnet/addresses.json from the Cobalt upgrade task. NitroValidator is NITRO_VALIDATOR() on TEEProverRegistryProxy. ProtocolVersionsProxy is the proxy.

How has it been tested?

• Compared the updated rows with live mainnet eth_calls against https://ethereum.publicnode.com: gameImpls(621) on 0x43edB88C4B80fDD2AdFF2412A7BebF9dF42cB40e and NITRO_VALIDATOR() / ZK_VERIFIER() on the registry and verifier.
• Confirmed CertManager, P384Verifier, and ProtocolVersionsProxy have code on mainnet and match config/mainnet/addresses.json from the Cobalt upgrade task.

Screenshots

N/A (address table only; not rendered locally)

Made with Cursor

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
base	🟢 Ready	View Preview	Sep 29, 2026, 6:22 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

[cb-heimdall]

✅ Heimdall Review Status

Requirement	Status	More Info
Reviews	✅ 1/1	Denominator calculation Show calculation 1 if user is bot 0 1 if user is external 0 2 if repo is sensitive 0 From .codeflow.yml 1 Additional review requirements Show calculation Max 0 0 From CODEOWNERS 0 Global minimum 0 Max 1 1 1 if commit is unverified 0 Sum 1