[U17] [Devnet Request]: Interop - Alphanet

[mslipper]

Name

Interop Alphanet

Scope

Initial scope for launch includes interop + two vanilla chains. Final scope (before Betanet) will be one vanilla and one rollup boosted chain.

• Isthmus feature complete to support proof system
  • Feb 24 Holesky, March 5 Sepolia L1 pectra updates
• Does not need to include the final expiry window, could be updated in the betanet
• Supervisor able to support multiple nodes/operate with conductor
• Runs with conductor and similar architecture as op mainnet with sentry nodes
  • Reth as a full node, no txpool and interop sequencing
• Suite of network acceptance tests to run against the network
  • Owner needs to take over the full scope
  • For both valid and invalid interop messages
    • Baseline throughput with interop messages
    • Burst throughput with interop messages
    • Latency for inclusion of an interop message
• Blocktimes: one chain with 2 seconds and one chain with 1 second
• Shared dispute game factory and anchor state registry
• All fault proof contracts code complete
• op-program, kona, cannon, op-challenger all updated for interop
• [NOT BLOCKING] Rollup Boost + rbuilder on one of the chains. Not needed for launch - must show stability of rbuilder for at least 1 week before betanet
• Grafana dashboards, monitoring and alerting

Configurations

• deploy latest contracts from develop
• op-batcher/v1.11.5 PREFER_LOCAL_SAFE_L2=true
• op-challenger/v1.3.4-rc.1
• op-dispute-mon/v1.4.0
• op-program: Use whatever is the latest in develop.
• op-geth/v1.101503.2-rc.3
• op-node/v1.12.3-dev.1
• op-supervisor/v0.2.0-dev.1
• op-proposer/v1.10.1-rc.1

[dmarzzz]

hola, just learning about this tracker, super helpful!

I see the due date on this is Feb 10th but the previous item "Interop Stable" is also Feb 10th, does that mean this is the devnet to be included in the audit?

[op-aaron]

(Note: This represents the final state of the Alphanet. For launch we will have 2 Vanilla chains)

Chain 1 should have the rollup boost - The expectation is this devent will mirror Unichain’s configs meaning 1sec blocktime & rollup boost

Chain 2 can be Vanilla - The expectation is this devnet will reflect OP Mainnet configs (no rollup boost & 2sec blocktimes). It should also be running a reth backup sequencer.

[trianglesphere]

When is interop able to be ran? UL is interested in running a chain in an interop set.

[op-aaron]

Note: We've retargeted this for release on Monday, March 3rd

[zhwrd]

Batcher needs a new flag (tbd)

[protolambda]

Regarding the batcher flag: it's PREFER_LOCAL_SAFE_L2 that should be set.
This was introduced here: ethereum-optimism/optimism#14587

It prevents situations where the batcher can get stuck (if it waits for cross-safe instead of local-safe then the batcher on the other chain can disrupt operation, or even cause a type of cross-chain dead-locking situation in rare situations when combined with flashblocks).

[axelKingsley]

Just making sure that this ticket has a reference to the Topology Design Doc @tynes and I put together this week, which is approved by @zhwrd and ready for merge.

ethereum-optimism/design-docs#218

[protolambda]

op-batcher release to use: op-batcher/v1.11.5

We'll cut dev releases for op-node and op-supervisor now

[protolambda]

op-geth release to use: v1.101503.2-rc.3

[protolambda]

Dev releases, tentatively for RC Alpha devnet launch:

op-node/v1.12.3-dev.1

op-supervisor/v0.2.0-dev.1

Docker builds in progress.

op-node is a dev release because we're not going through a full release cycle for just this.

op-supervisor is a dev release because we expect to change some minor things like additional metrics.

[protolambda]

@Inphi I believe is preparing a new op-proposer release (unless the diff is not critical), to include the latest proposer functionality for interop

@Inphi created the tag: op-proposer/v1.10.1-rc.1

[zhwrd]

devnet configs: https://devnets.optimism.io/interop-rc-alpha.html