Context
Benzo's Avalanche C-Chain mainnet (43114) deploy went live on 2026-07-09: the full eERC converter stack (10 contracts) is deployed wrapping real Circle USDC (tokenId 1) / EURC (tokenId 2), the Groth16 phase-2 ceremony completed, the auditor key is set on-chain, all 10 contracts are Snowtrace-verified, and the CCTP onramp was proven end-to-end. That deploy workstream is done — see the now-closed #120 (network wiring + deploy:mainnet guardrails + initial auditor custody), #121 (production ceremony + regenerated verifiers), #122 (README + go/no-go), and master tracker #123.
Source of truth for the current state:
docs/MAINNET_GO_NO_GO.md — GO recorded 2026-07-09, with the remaining post-deploy items.
contracts/deployments/avalanche.json — live mainnet manifest (real tx hashes / block numbers / verifiedAt).
contracts/deployments/benzonet.json — BenzoNet L1 (68420) manifest.
README.md "What remains" + "Honest limitations".
This tracker collects the genuinely-open follow-up work those documents flag as not-yet-done: mainnet post-deploy hardening (admin custody, external audit, onramp, open ceremony) and BenzoNet L1 production-readiness (validators, read-privacy, gas runway), plus a license-compliance checklist. It is not a re-plan of the completed deploy — anything already shipped in #120–#123 is deliberately excluded.
These are planning issues only — filing or working them performs no deployment, no ceremony, and no key operations.
Children
Mainnet C-Chain (43114) hardening
BenzoNet L1 (68420) production-readiness
Cross-cutting
Out of scope (already shipped — see closed issues)
Note
- BenzoNet manifest contracts are currently
verified: false (not source-verified on the Blockscout explorer). This is folded into the multi-validator re-stand issue rather than filed standalone.
Context
Benzo's Avalanche C-Chain mainnet (
43114) deploy went live on 2026-07-09: the full eERC converter stack (10 contracts) is deployed wrapping real Circle USDC (tokenId 1) / EURC (tokenId 2), the Groth16 phase-2 ceremony completed, the auditor key is set on-chain, all 10 contracts are Snowtrace-verified, and the CCTP onramp was proven end-to-end. That deploy workstream is done — see the now-closed #120 (network wiring +deploy:mainnetguardrails + initial auditor custody), #121 (production ceremony + regenerated verifiers), #122 (README + go/no-go), and master tracker #123.Source of truth for the current state:
docs/MAINNET_GO_NO_GO.md— GO recorded 2026-07-09, with the remaining post-deploy items.contracts/deployments/avalanche.json— live mainnet manifest (real tx hashes / block numbers /verifiedAt).contracts/deployments/benzonet.json— BenzoNet L1 (68420) manifest.README.md"What remains" + "Honest limitations".This tracker collects the genuinely-open follow-up work those documents flag as not-yet-done: mainnet post-deploy hardening (admin custody, external audit, onramp, open ceremony) and BenzoNet L1 production-readiness (validators, read-privacy, gas runway), plus a license-compliance checklist. It is not a re-plan of the completed deploy — anything already shipped in #120–#123 is deliberately excluded.
These are planning issues only — filing or working them performs no deployment, no ceremony, and no key operations.
Children
Mainnet C-Chain (
43114) hardeningsecurity(mainnet):transferOwnableadmin off the hot deploy key to a multisig / cold wallet (top priority)security(mainnet):commission an independent security audit of the mainnet eERC deploymentsecurity(mainnet):harden the CCTP onramp beyond the single 0.1 USDC test burnceremony:run an open multi-party Groth16 phase-2 ceremony with independent external participantssecurity(mainnet):auditor key custody hardening + on-chain rotation runbookBenzoNet L1 (
68420) production-readinessinfra(l1):move BenzoNet off a single validator to a multi-validator PoA setinfra(l1):enablevalidatorOnlyread-privacy for a production BenzoNetinfra(l1):BenzoNet gas/fee sustainability + P-Chain runway guardrailsCross-cutting
docs(compliance):eERC Ecosystem-License v1.1 compliance checklist for all mainnet/L1 deliverablesOut of scope (already shipped — see closed issues)
deploy:mainnet+ initialsetAuditorPublicKey— [contracts] Avalanche C-Chain (43114) network wiring, guard-railed deploy:mainnet, and mainnet auditor custody #120.avalanche.jsonverifiedAt).rpc.benzo.space) + Blockscout explorer — Redeploy the identical eERC stack to BenzoNet and verify on its explorer #32 / Stand up a token-gated Blockscout explorer for BenzoNet #29.Note
verified: false(not source-verified on the Blockscout explorer). This is folded into the multi-validator re-stand issue rather than filed standalone.