Skip to content

Complete post-centralization contract and service cleanup #999

Description

@SegueII

Background

After the centralized sequencer rollout, the batch submitter must become an independent role with its own key, authorization, staking, and slash responsibility. Legacy L1 staking and sequencer-set dependencies also need to be removed from current write paths while preserving historical sync and verification.

This issue tracks the repository implementation in chapters 2–12 of the centralization cleanup spec.

Scope

  • Add the upgradeable Submitter contract and replace L1Staking authority in Rollup.
  • Remove bitmap/signature inputs from current batch submission and record the responsible submitter address.
  • Preserve frozen pre-upgrade ABIs and historical selector decoding for old blocks.
  • Add Submitter deployment/registration and a fail-closed Legacy L1Staking retirement tool.
  • Replace dynamic batch and validator dependencies with explicit static configuration after the upgrade boundary.
  • Simplify tx-submitter to the current fresh-blob write path and canonical cold-start recovery.
  • Update node derivation, shadow prover, challenger, and gas oracle to resolve canonical submissions across the cutover.
  • Add reproducible bindings, deterministic tests, runtime configuration, and blocking CI workflows.

Acceptance criteria

  • Submitter lifecycle, pending-batch responsibility, exit, refund, and slash behavior are covered by contract tests.
  • Rollup storage compatibility and old/new selector behavior are verified.
  • Historical readers continue to decode and resolve pre-cutover batches canonically.
  • Contracts, bindings, common, node, tx-submitter, prover, gas-oracle, and ops checks pass.
  • Production-only values are not inferred from development defaults.

Out of scope / follow-up gates

This issue does not execute the production upgrade. Real RPC deployment, Legacy L1Staking fork/relay rehearsal, Safe/ProxyAdmin cutover, multi-role node rehearsal, cold-start/reorg/blob E2E, Docker validation, branch protection, and the spec's chapters 13–18 production decommissioning/operations gates require separate evidence and approval.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions