feat: add zeronet system deploy task#746
Open
rayyan224 wants to merge 6 commits into
Open
Conversation
Adds a new task folder for deploying the full L1 system on zeronet using SystemDeploy.s.sol from the sibling contracts repo. Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com>
Collaborator
🟡 Heimdall Review Status
|
Populates previously TODO fields using existing zeronet/.env values: - finalSystemOwner <- PROXY_ADMIN_OWNER - superchainConfigGuardian <- CB_MULTISIG - sp1Verifier <- RISC_ZERO_SET_VERIFIER - fee vault recipients <- CB_MULTISIG (all four) Still TODO: p2pSequencerAddress, zkRangeHash, zkAggregationHash, multiproofConfigHash, multiproofGenesisOutputRoot Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com>
Populates TODO fields using values from the most recently executed tasks: - zkRangeHash / zkAggregationHash <- 2026-06-13-upgrade-zk-and-tee-hash - multiproofConfigHash <- 2026-04-01-activate-multiproof (CONFIG_HASH) - multiproofGenesisOutputRoot / multiproofGenesisBlockNumber <- most recent anchor reset (2026-06-13) Only remaining TODO: p2pSequencerAddress (not present in any task file) Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com>
Starting from scratch on Hoodi L1, so multiproofGenesisBlockNumber resets to 0. multiproofGenesisOutputRoot needs to be filled with the actual L2 genesis output root once op-node genesis is created. Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com>
…ctions Sets multiproofGenesisBlockNumber/OutputRoot to current zeronet finalized state (block 4179448). These values must be refreshed to a recent block immediately before deploying since the proof node only retains recent history. README now includes the cast commands to fetch fresh values. Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com>
…er() Read directly from SystemConfig (0xcc7c...ea80) on Hoodi L1. deploy-config/zeronet.json now has no remaining TODO fields. Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
zeronet/2026-06-24-system-deploy/task folder for running a full L1 system deployment on zeronetforge script SystemDeploy.s.sol:SystemDeploydirectly from the siblingcontracts/repo (nodeploy.sh)deploy-config/zeronet.jsonis kept inside the task folder and passed viaDEPLOY_CONFIG_PATH; known values are pre-filled, remaining fields are markedTODOTest plan
TODOfields indeploy-config/zeronet.json(ZK hashes, fee vault recipients, guardian, p2p sequencer, etc.)make simulateto dry-run the deployment with no broadcastmake deploywith Ledger connected to broadcast the full system deployment