# ๐Ÿ“ <L2 Name> L2 Multiprover Product Design Requirements Overview ## Basic Context - **L2 Name:** - **Your Role (engineering, product, research, infra, etc.):** --- ## Proving Requirements 1. **Top priorities for your proving system today:** _(e.g. speed, cost, auditability, decentralization, resilience)_ 2. **Failure modes you are most concerned about with a single prover setup:** - [ ] Soundness bug (invalid state transition proving) - [ ] Prover downtime / liveness failure - [ ] Upgrade centralization / governance risk - [ ] Other: _________ 3. **Desired target for proof finality / settlement times:** _(e.g. 1 hour, < 1 day, doesnโ€™t matter, etc.)_ --- ## Multiprover Integration 4. **Which proving systems are you currently evaluating or using?** - [ ] ZK prover (e.g. Succinct, RiscZero, etc.) - [ ] Optimistic prover - [ ] TEE-based prover - [ ] Other: _________ 5. **How important is multiproving for your roadmap in the next 12โ€“18 months?** - [ ] Not important - [ ] Nice-to-have - [ ] Important - [ ] Critical 6. **Biggest blockers to adopting multiproving in your L2:** _(e.g. engineering effort, prover maturity, infra cost, governance complexity, etc.)_ --- ## Product & User Context 7. **Who are the primary users or stakeholders you are optimizing proof systems for?** - [ ] Bridge operators / liquidity providers - [ ] Application developers - [ ] Retail users - [ ] Institutional users - [ ] Governance / protocol security - [ ] Other: _________ 8. **Why would these users value multiproving?** _(e.g. faster bridging, lower risk of downtime, compliance, stronger decentralization guarantees, etc.)_ 9. **What trade-offs are you willing to make to serve those users?** _(e.g. accept higher infra costs for faster finality, accept slower finality for stronger decentralization, etc.)_ --- ## Resourcing 10. **Is your team currently investing engineering resources into multiproving?** - [ ] Yes โ€” actively building - [ ] Yes โ€” exploratory research / prototyping - [ ] Not yet, but planning to - [ ] No plans currently 11. **If yes, what areas are you focused on?** _(e.g. prover implementation, infra integration, market interface, testing, other)_ --- ## Open Input 12. **What would you want from a โ€œmultiprover marketโ€ (if one existed)? i.e. more than one prover** 13. **Any other requirements or concerns we should keep in mind?** ---