-
Notifications
You must be signed in to change notification settings - Fork 3
Closed
1 / 11 of 1 issue completedLabels
scopingDevnet scoping issueDevnet scoping issue
Description
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
Sub-issues
Metadata
Metadata
Assignees
Labels
scopingDevnet scoping issueDevnet scoping issue