<!-- #Ethereum #Multiproving #ZKProving -->
# Working Group to Accelerate L2 Multiproving #0
<center><img src="https://hackmd.io/_uploads/HJ4xeyznxx.png" alt="drawing" width="300"/></center>

## Transcript and Recording
- [:link: Kick Off Document](https://hackmd.io/@dmarz/Skg44oOYxl)
- [:link: Presentation Link](https://hackmd.io/@dmarz/By19lvyhxg)
- [:link: Gemini Transcript](https://docs.google.com/document/d/1TfjdzVRIqJe4hMvDmRDwxmsUjo_nviZlal7uKMmpmds/edit?usp=sharing)
- [:link: Video Recording](https://drive.google.com/file/d/1w3BGOh6_ErCFfYFF3M2--sz-X6Ug71CJ/view?usp=sharing)
- [:link: Call Chat](https://drive.google.com/file/d/13yNtKPvxbY83cCrygjAACSvchlAUJ1Dv/view?usp=sharing)
- [:link: Google Form to Register for Calls](https://docs.google.com/forms/d/1BKo_L7xZ0C3Hzf2_t6mpOOfXHIluYs0s0-KvpJj18Ao/edit)

## AIWHIL Summary (AI With Human In Loop)

- Went through the [group charter](https://hackmd.io/@dmarz/Skg44oOYxl)
- Participants shared updates on their multi-prover projects and discussed collaborative next steps, with individuals volunteering to be coordinators for the OP Stack multi-prover POC, arbitrum PoC, and the multiprover market structure design document
- The need for a cohesive view of what product requirements each L2 we're focusing on came up and yielded good action items.
- [Pragmatic Fast Finality](https://ethereum-magicians.org/t/a-simple-l2-security-and-finalization-roadmap/23309) design was discussed briefly and complexity quickly arose as a counter argument for using it with PoCs.

graph TD
    %% Define CSS styles for nodes
    classDef mainPhase fill:#ADD8E6,stroke:#333,stroke-width:2px,color:#333,font-weight:bold;
    classDef subPhase fill:#DDA0DD,stroke:#6A5ACD,stroke-width:1.5px,color:#333;

    A["Phase One<br/>coordinator: dmarz"]:::mainPhase --> B["OP Stack multiprover PoC<br/>coordinator: Paul (OP)"]:::subPhase;
    A --> C["Arbitrum multiprover PoC<br/>coordinator: Lumi (Arb)"]:::subPhase;
    A --> D["Design goals document for a multiprover market interface<br/>coordinator:  Davide (PBSF)"]:::subPhase;

- [:link: Multiprover Product Design Requirements Survey Template](https://hackmd.io/@dmarz/Hk-JXJM3le)

## Design Questions Raised
- What emergency actions are acceptable in case of proof systems disagree or liveness failure?
- What are the product requirements L2s are solving for?
- What are the most thoroughly tested solutions that can be deployed in the next 6 - 12 months across ZK and TEE provers?

## Action Items
- Multiprover Product Requirements Docs: Base (Henri), Arbitrum (Lumi), ZkSync (Deli), Linea (Rudi) [can use this template](https://hackmd.io/@dmarz/Hk-JXJM3le).
- Paul to schedule a follow up call with Base and any other OP Stack chains to discuss what proving stacks teams have the most confidence in shipping ASAP.
- Davide to schedule initial Prover Market Structure call.
- Dmarz to schedule next call in 1 month.