# Working Group to Accelerate L2 Multiproving #1
:octopus:
The Internet
November 10th, 2025
---
## Agenda
- Breakout Group Updates
- OP Stack (Paul)
- Arbitrum Stack (Lumi)
- L2 Multiprover Market Structure (Dmarz sub in for Davide)
- Path to PoC Recap
- Open Discussion
---
## Breakout Group Update: OP Stack (Paul)
---
## Breakout Group Update: Arbitrum Stack (Lumi)
---
## Breakout Group Update: L2 Multiprover Market Structure (Dmarz)
---
## Path to PoC Recap
Many different requirements, teams, and resource commitments. Where are we in the joint overall process?
---
## Path to PoC Recap
```mermaid
%%{init: {
"theme": "base",
"themeVariables": {
"fontSize": "20px",
"fontFamily": "Inter, Segoe UI, Helvetica, Arial, sans-serif",
"primaryColor": "#0b1220",
"primaryTextColor": "#e5e7eb",
"primaryBorderColor": "#6366f1",
"lineColor": "#94a3b8"
},
"flowchart": {
"htmlLabels": false,
"useMaxWidth": false,
"rankSpacing": 35,
"nodeSpacing": 28,
"curve": "linear"
}
}}%%
flowchart TB
PR["Product Requirements"]
DG["Design Goals"]
ARCH["Architecture"]
IMPL["Implementation"]
POC["PoC on Sepolia"]
PR --> DG --> ARCH --> IMPL --> POC
classDef step fill:#0b1220,stroke:#6366f1,stroke-width:1.6px,color:#e5e7eb,rx:12,ry:12;
class PR,DG,ARCH,IMPL,POC step;
```
---
## Product Requirements
| Stakeholder | Requirements Link |
| -------- | -------- |
| Vitalik | [PFF](https://ethereum-magicians.org/t/a-simple-l2-security-and-finalization-roadmap/23309)|
| Base| |
| OP Mainnet | |
| Unichain | |
| Arbitrum | |
| Bridge | |
| Solver | |
---
## Design Goals
We have a set of design goals from [PFF](https://ethereum-magicians.org/t/a-simple-l2-security-and-finalization-roadmap/23309):
> 1. Provide instant finality in the normal case
> 2. Satisfy the core stage 2 criteria, particularly (i) the requirement that if the “trustless” proof systems work, then nothing “semi-trusted” (either TEE or security council) is able to override them, (ii) the 30-day upgrade delay
> 3. Avoid short-term over-reliance on ZK. Today, ZK proof systems still have a high enough rate of bugs, and shared code, that it is very plausible that either (i) there is a bug in shared code that affects multiple proof systems, or (ii) an attacker finds and holds on to a bug in one proof system for long enough that they discover a bug in the other.
---
## Architecture
- PFF defines the protocol
- Unified API and system component interactions still TBD
---
## Implemenation
- ZK Proof Systems
- OP Succinct and Arb Succinct
- Kailua
- TEE
- OP Enclave
- Automata TEE Architecture
- Optimistic
- traditional OP and Arb dispute games
- Integration
---
## Next Steps
---
## Next Steps
Aggregate and Finalize Stake holder input
| Stakeholder | Requirements Link | Owner |
| -------- | -------- | -------- |
| Vitalik | [PFF](https://ethereum-magicians.org/t/a-simple-l2-security-and-finalization-roadmap/23309)| ✅ |
| Base| | |
| OP Mainnet | | |
| Unichain | | |
| Arbitrum | | |
| Linea | | |
| Bridge | | |
| Solver | | |
---
## Next Steps
Schedule Break Out Calls
- Multiprover Marketstructure Breakout @davide
- More?
---
## Discussion
---
## Thank you! :octopus:
{"title":"L2 Multiproving Call #2","description":"View the slide with \"Slide Mode\".","contributors":"[{\"id\":\"46d133a8-ca00-497f-bd84-8daeeef5a067\",\"add\":6191,\"del\":2721,\"latestUpdatedAt\":1762720634287}]"}