fix(PRIV-2004): allow dev multiproof on Base Sepolia (84532)#348
Merged
robriks merged 1 commit intoJun 18, 2026
Conversation
The dev-multiproof production-chain guard in SystemDeploy classified Base Sepolia (84532) as a production chain, so the deploy reverted on the L3 devnet that settles to Base Sepolia. Base Sepolia is a public testnet, not a value-bearing chain, so drop it from the blocklist while keeping the guard for Ethereum mainnet (1) and Base mainnet (8453). Co-authored-by: Cursor <cursoragent@cursor.com>
hughy
approved these changes
Jun 18, 2026
robriks
deleted the
markusosterlund/priv-2004-systemdeploy-dev-multiproof-production-chain-guard-wrongly
branch
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
SystemDeploy(_assertValidMultiproofInput) classified Base Sepolia (84532) as a production chain and reverted before any L1 contracts were initialized.block.chainid == 84532), and it is a public testnet, not a value-bearing chain — so it's a valid dev-multiproof target.84532from the blocklist while keeping the guard for Ethereum mainnet (1) and Base mainnet (8453), so mainnet protection is preserved.Why this approach
Considered and rejected:
devnet.json→ loses multiproof devnet coverage.Impact this unblocks
devnet-setupexit 1 was cascading: downstream containers (builder, client, consensus, batcher, base-rpc, zk-prover) stayed inCreated, the ALB health check on:8545never responded, the ASG terminated the instance, and the deploy halted withHaltError: Found terminating instances.Linear: PRIV-2004
Made with Cursor