[koenmtb1]

Moves main to Aztec 6.0.0 so AztecScan can index the v6 testnet rollup. It also adds what's needed to run v6 next to v5 rather than instead of it. Each major version of a network becomes its own deployment, picked from a version dropdown, and a retired one stays browsable without a node.

Mainnet is still on Aztec 5.0.0, so mainnet (and testnet v5) move to the new release/v5 branch; see #11. The one open item is a live-node check (below).

Commits

1. fix: parse boolean env vars strictly. z.coerce.boolean() read "false" as true for six env switches (also in release/v5: Node 24.22.1 (eMudhra), strict boolean env parsing, ARCHIVE_MODE #11).
2. feat(explorer-api): add ARCHIVE_MODE. Serve a retired rollup from Postgres alone: no Kafka, no reconciliation, source verification returns 503 (also in release/v5: Node 24.22.1 (eMudhra), strict boolean env parsing, ARCHIVE_MODE #11).
3. chore: upgrade to Aztec 6.0.0.
   • 6.0.0 publishes under new scopes: @aztec-labs/*, plus @aztec-foundation/l1-artifacts and @aztec-foundation/bb.js. Imports, deps and root resolutions move to them.
   • The 6.0.0 L1 ABIs match the deployed contracts of the canonical testnet rollup exactly (0x1f435a7f…, version 679261766): every Rollup/Inbox/Outbox/FeeJuicePortal selector is in the bytecode, and recent logs decode.
   • createAztecNodeClient now takes an options object.
   • Genesis blocks are added for the v6 rollups, so the L1 listener doesn't scan Sepolia from block 8.1M.
4. feat(message-registry): optional KAFKA_NAMESPACE. v5 and v6 testnet share L2_NETWORK_ID=TESTNET. Topics and consumer groups derive only from that, so two stacks on one Kafka would read each other's blocks. When set, KAFKA_NAMESPACE=v6 prefixes every topic and group (v6.TESTNET__NEW_BLOCK_EVENT). Unset, every name is unchanged.
5. feat(explorer-ui-v2): version picker.
   • VITE_NETWORK_VERSION names this build's version.
   • VITE_CHICMOZ_ALL_UI_URLS entries can carry a version and status: Network|URL[|version[|status]], with status canonical (default), live or archived. Old two-field entries still work.
   • The network picker always goes to a network's canonical version; a separate version picker lists the network's versions.
   • Non-canonical builds show a banner pointing at the canonical one; archived builds drop the WebSocket and live tip.
6. fix(compiler): 6.x compilers.
   • From 6.0.0, aztec-nr lives at aztec-labs-eng/aztec-nr (the AztecProtocol/aztec-nr mirror stops at v5.2.1), and azteclabs/aztec no longer ships nargo.
   • Dockerfile.compile-contracts installs the pinned Noir release (1.0.0-rc.3 for 6.0.0, sha256-checked) only when the base image has none, and prefetches aztec-labs-eng/aztec-nr only for tags that exist there, plus poseidon v0.3.0/v0.4.0. It still builds the 4.x/5.x compilers.
   • build_contract_compiler.sh picks azteclabs/aztec for 6.x.
   • event-cannon: Nargo pins move to the new repo, the v6 consume_l1_to_l2_message signature is handled, and createSchnorrAccount gets a signing key.
7. chore(event-cannon): regenerated artifacts. Compiled with the 6.0.0 compiler image on a native amd64 GitHub runner (bb's transpile and VK steps need CPU features x86 emulation lacks), then aztec codegen. All three artifacts are transpiled and stamped aztec_version 6.0.0.
8. fix(contract-verification): run tests in child processes. On Linux, vitest 0.34's worker-thread pool exits 1 after every test passes; this package's tests load the Aztec SDK, native modules included. Reproduced on ubuntu-latest (default pool exits 1, --no-threads exits 0). Also in release/v5: Node 24.22.1 (eMudhra), strict boolean env parsing, ARCHIVE_MODE #11.

Verification

• Shared packages and all deployed services build and lint clean (aztec-listener, ethereum-listener, explorer-api, websocket-event-publisher, compiler-orchestrator, auth, explorer-ui-v2).
• yarn test passes: contract-verification 4, message-registry 3, auth 105, aztec-listener 41, explorer-api 62, explorer-ui-v2 9.
• The PR build workflow (yarn install && yarn build && yarn test on ubuntu-latest) passes.
• The UI was driven in headless Chrome as archived Testnet v5 and as canonical Testnet v6, dark and light; no page errors.

Known gaps

• Not run against a live v6 node. Block fetch and parseBlock against a real V6 node are untested; no public testnet endpoint answered. The first v6 RPC node from the foundation-iac change is the place to check this before pointing listeners at it.
• Compile jobs download the CRS. 6.x contracts with private functions fetch the CRS from crs.aztec-labs.com at compile time to derive verification keys. Production compile jobs already have network (they git clone the source), so this works; warming the CRS in the image would only make jobs faster.

Deploying

This needs foundation-iac changes, which come in a separate PR:

• per-network CHICMOZ_REF;
• a new testnetv6 network with KAFKA_NAMESPACE=v6;
• a rpc_networks entry on azteclabs/aztec:6.0.0 (the image validation currently only allows aztecprotocol/aztec);
• versioned UI config in deploy-ui.sh.

🤖 Generated with Claude Code