Rollup Operator Control Planes
This note narrows control-surfaces, routing-and-defaults, and permissions-and-policy to rollup stacks, managed chain operators, proving paths, and chain-brand defaults.
Questions worth asking:
- Who actually keeps the chain live: sequencer, prover, gateway, bridge operator, or managed vendor?
- Which defaults are inherited from the stack steward or hosted operator?
- Where do proof mode, bridge packaging, or fallback execution become the real control surface?
Canonical comparison set
- Stack steward and canonical-default case: optimism
- Execution-venue and adjacent operator stack: base and coinbase-developer-platform
- Managed rollup operator wrappers: caldera and conduit
- Sequencing and gateway chokepoint case: based-op
- Proof-mode and fallback-rights case: op-succinct
- Canonical issuer / bridge rails that may still define the real path beneath a chain brand: circle-usdc and cctp
Useful traversal questions
- Did the chain choose its own control plane, or inherit one from a vendor or stack steward?
- Is the key default bridge, proof path, gateway, or operator package being treated as if it were just
the chain? - When the visible chain brand fails, who still decides the fallback?