← Opportunities

OP Stack Zero Knowledge Proof

Funder
Optimism Foundation · Foundation Mission Request (Season 4) 🟡 Some evidence
Type / status
rfp · closed
Amount
250,000 OP · ≈ $27k
Deadline
2023-06-28 (past)
“Submit by: June 28th at 19:00 GMT”
Ecosystems
optimismethereum
Categories
zkinfrainteroperabilityresearch
Tech stack
gorustmipsrisc-vwasmplonkkzghalo2
Apply
https://github.com/ethereum-optimism/ecosystem-contributions/issues/61
Source
https://github.com/ethereum-optimism/ecosystem-contributions/issues/61
Fit
31% · weak fit · The team's expertise in Aleo/Leo and Rust aligns with the zk and infra categories, but their ecosystem is aleo, not optimism/ethereum, making them an outsider applicant for this OP Stack ZK proposal.
Trust
100% · model self-report 95% · first seen 2026-10-23 · v8
Verified
2026-10-27 · by extraction

The Optimism Foundation requested proposals to implement a zero-knowledge proof system for the OP Stack fault proof program using a golang-supported ISA (MIPS, RISC-V, or WASM). Up to three teams would be selected, each receiving a baseline grant of 250k OP locked for one year. Applicants had to submit a proposal by June 28, 2023, including architecture choice, tradeoffs, milestones, and team details. The RFP is now marked as abandoned.

Eligibility: Open to Alliances meeting the Fledgling tier (eligible to receive up to 350k OP). Teams must provide KYC, accept a one-year token lock, and comply with grant policies including clawback for missed milestones.

Pipeline

Override status:

Funder track record · does Optimism Foundation actually pay grants?

🟡 Some payout evidence · 5 grantees found · last payout 2026-06-14 · ⚠ 1 complaint · checked 2026-11-06 · 0 forum reports, 5 web pages read, 2 unverifiable claims dropped

Proven payer: at least 3 named grantees and one payout in the last 90 days. Every grantee below is quoted word for word from its source. When a source does not date a grant, the date is when that page or post was published.

Red flags

GranteeAmountDateEvidence
Modeup to $5.3 million in OP tokens (approximately 2 million OP)2026-06-14“Mode has secured up to $5.3 million in OP tokens (approximately 2 million OP) to fuel user growth incentives.” source
Superstate—2026-06-14“Superstate received grants to develop institutional-grade infrastructure for tokenized real-world assets (RWA).” source
Foundry—2026-01-08“past recipients include Foundry, Viem and Velodrome Finance. The last monthly results, for December 2025, were published on January 8, 2026.” source
Viem—2026-01-08“past recipients include Foundry, Viem and Velodrome Finance. The last monthly results, for December 2025, were published on January 8, 2026.” source
Velodrome Finance—2026-01-08“past recipients include Foundry, Viem and Velodrome Finance. The last monthly results, for December 2025, were published on January 8, 2026.” source

Trust breakdown (4/4 checkable facts verified)

SignalWeightResultNote
deadline0.35100%quoted in source
amount0.25100%figure appears in source
apply link0.075100%link in source
funder0.075100%named in source
source quality0.1550%social or search hit
model confidence0.195%model self-report
corroborationbonus+10%8 sources

Fit breakdown (against the ORG_* profile)

SignalWeightResultNote
model fit0.540%model rated 40%
ecosystem overlap0.250%optimism, ethereum vs aleo
category overlap0.1550%zk, infra, interoperability, research vs zk, privacy, infra, dev_tooling, security, interoperability
tech overlap0.133%go, rust, mips, risc-v, wasm, plonk, kzg, halo2 vs rust, leo, zk

Sources (8)

RoleDocumentFromFetched
primaryFoundation Mission Request: OP Stack Zero Knowledge Proof [ABANDONED] · Issue #61 · ethereum-optimism/ecosystem-contributions · GitHubWeb discovery: ecosystem sweep2026-10-23
primaryFoundation Mission Request: OP Stack Zero Knowledge Proof [ABANDONED] · Issue #61 · ethereum-optimism/ecosystem-contributions · GitHubWeb discovery: ecosystem sweep2026-10-23
primaryFoundation Mission Request: OP Stack Zero Knowledge Proof [ABANDONED] · Issue #61 · ethereum-optimism/ecosystem-contributions · GitHubWeb discovery: ecosystem sweep2026-10-24
primaryFoundation Mission Request: OP Stack Zero Knowledge Proof [ABANDONED] · Issue #61 · ethereum-optimism/ecosystem-contributions · GitHubWeb discovery: ecosystem sweep2026-10-24
primaryFoundation Mission Request: OP Stack Zero Knowledge Proof [ABANDONED] · Issue #61 · ethereum-optimism/ecosystem-contributions · GitHubWeb discovery: ecosystem sweep2026-10-25
primaryFoundation Mission Request: OP Stack Zero Knowledge Proof [ABANDONED] · Issue #61 · ethereum-optimism/ecosystem-contributions · GitHubWeb discovery: ecosystem sweep2026-10-25
primaryFoundation Mission Request: OP Stack Zero Knowledge Proof [ABANDONED] · Issue #61 · ethereum-optimism/ecosystem-contributions · GitHubWeb discovery: ecosystem sweep2026-10-25
primaryFoundation Mission Request: OP Stack Zero Knowledge Proof [ABANDONED] · Issue #61 · ethereum-optimism/ecosystem-contributions · GitHubWeb discovery: ecosystem sweep2026-10-27

History (8)

vChangedFields
82026-10-27summary, amountMinUsd, amountMaxUsd
72026-10-25summary, amountMinUsd, amountMaxUsd
62026-10-25summary, amountMinUsd, amountMaxUsd
52026-10-25summary, amountMinUsd, amountMaxUsd
42026-10-24summary, amountMinUsd, amountMaxUsd
32026-10-24summary, amountMinUsd, amountMaxUsd
22026-10-23summary
12026-10-23created

Extracted text

[](/ethereum-optimism/ecosystem-contributions)

# Foundation Mission Request: OP Stack Zero Knowledge Proof \[ABANDONED\] #61

New issue

Copy link

New issue

Copy link

Closed

Closed

[Foundation Mission Request: OP Stack Zero Knowledge Proof \[ABANDONED\]](/ethereum-optimism/ecosystem-contributions/issues/61#top)#61

Copy link

Labels

[Foundation Mission RequestA request for proposals for a specific work item.](https://github.com/ethereum-optimism/ecosystem-contributions/issues?q=state%3Aopen%20label%3A%22Foundation%20Mission%20Request%22)A request for proposals for a specific work item.[Intent: Technical Decentralization](https://github.com/ethereum-optimism/ecosystem-contributions/issues?q=state%3Aopen%20label%3A%22Intent%3A%20Technical%20Decentralization%22)

## Description

[![@bdresser](https://avatars.githubusercontent.com/u/1016190?u=58eab6c87c6ecee317aa1e4bf866679dc8939309&v=4&size=48)](https://github.com/bdresser)

[bdresser](https://github.com/bdresser)

opened [on May 30, 2023](https://github.com/ethereum-optimism/ecosystem-contributions/issues/61#issue-1732662881)

Issue body actions

## Foundation Mission Request – OP Stack Zero Knowledge Proof

_To take on this project, submit a proposal to this thread by June 28. Read more about Missions [here](https://gov.optimism.io/t/token-house-missions/5881)._

*   **S4 Intent**: Technical Decentralization
*   **Foundation Mission (RFP):** Implement a zero knowledge proof which can prove Optimism’s [fault proof program](https://github.com/ethereum-optimism/optimism/blob/develop/specs/fault-proof.md#fault-proof-program) through an [instruction set architecture](https://en.wikipedia.org/wiki/Instruction_set_architecture) supported by the [golang compiler](https://gist.github.com/mcandre/b78112ed46f2360ddc59f33a78951d0e)
*   **Proposal Tier:** [Fledgling](https://gov.optimism.io/t/collective-trust-tiers/5877)
*   **Baseline grant amount**: 250k OP
*   **Accepting one or multiple proposals:** Multiple
*   **OP Labs or Optimism Foundation Sponsor**: Kelvin ([@smartcontracts](https://github.com/smartcontracts))
*   **Submit by**: June 28th at 19:00 GMT
*   **Selection by**: July 13th at 19:00 GMT

### **How will this Foundation Mission (RFP) will help accomplish the above Intent?**

Implementing a zero knowledge proof (ZKP) for OP Chains is a prerequisite to enable secure and low latency cross chain communication between L2 and L1, as well as directly between OP Chains. A ZKP for a well-supported instruction set architecture (ISA) that can prove the Optimism [fault proof program](https://github.com/ethereum-optimism/optimism/blob/develop/specs/fault-proof.md#fault-proof-program) acts as the foundation for a system that can prove any OP Stack based blockchain.

### **What is required to execute this Foundation Mission (RFP)?**

Completing this mission means implementing a zero knowledge proof (ZKP) system that can prove the Optimism [fault proof program](https://github.com/ethereum-optimism/optimism/blob/develop/specs/fault-proof.md#fault-proof-program) using an instruction set architecture (ISA) supported by the golang compiler such as MIPS, RISC-V, or WASM. This proof system must additionally be shown to work in practice by proving the state transition between two blocks for a standard configuration OP Stack chain.

Support for the fault proof program introduces additional requirements on top of proving a standard execution trace for an ISA. Specifically, the fault proof program introduces the notion of the [preimage oracle](https://github.com/ethereum-optimism/optimism/blob/develop/specs/fault-proof.md#pre-image-oracle) which uses special [system calls](https://en.wikipedia.org/wiki/System_call) to load external data into the program. Every [fault proof vm](https://github.com/ethereum-optimism/optimism/blob/develop/specs/fault-proof.md#fault-proof-vm) is responsible for implementing some mechanism by which the hash of some data is placed at a particular location in memory, a syscall is executed, and the preimage for that hash is then loaded into memory for the program to utilize. The preimage oracle is also used to bootstrap the program with initial inputs. Please refer to the [preimage oracle section of the fault proof program documentation](https://github.com/ethereum-optimism/optimism/blob/develop/specs/fault-proof.md#pre-image-oracle) for further information.

For this Mission, the Optimism Foundation will accept up to three submissions. Multiple parallel attempts at creating an OP Stack ZKP will increase chances of success and provide some friendly competition for building the best OP Stack ZKP.

Due to the wide design space, each solution will be evaluated based upon a few Solution Criteria. Due to the scope of this project, this RFP is not expected to be completed within governance Season 4 (June through September). Specific timelines will be discussed with each team that makes a submission.

The target grant payout for each submission will be 250k OP. Teams should discuss the solution criteria below with the Foundation, and may arrive at a different mutually agreeable grant amount dependent on the scope of their work.

### **Solution Criteria:**

1.  **Performance** — What is the compute cost to generate and verify the proof?
2.  **Latency** — How long does the proof take to generate?
3.  **Complexity** — How many lines of code is the prover / verifier?
4.  **Robustness** — How confident are we that there are no bugs?
5.  **Security** — What are the assumptions the system relies on for its security guarantees? (e.g. trusted setup)
6.  **OP Stack Compatibility** — Are there fundamental changes required to the OP Stack?
    1.  **Note 1**: It may be the case that small changes to the OP Stack are required to achieve an acceptable performance benchmark. One example of this includes introducing a ZKP-friendly batch submission accumulator to reduce the cost of proving transaction inclusion in the OP Chain. However, the fewer changes the better.
    2.  **Note 2:** The current OP Stack state transition function is defined in the fault proof program. Changes are evaluated with respect to this state transition function.

Proposals should include their target architecture and explicitly call out any tradeoffs their approach may have. Multiple proposals which select different tradeoffs may be accepted as each one can have their uses and bring value to the ecosystem.

### **How should the Foundation measure progress towards this Foundation Mission (RFP)?**

Progress can be measured based upon the completion of the following milestones:

1.  **Specification**: A specification for the ZKP design. Should include the criteria which the implementation will aim to satisfy.
2.  **PoC Check-in**: A demo of the ZKP being used to prove the OP Stack state transition. The specifics of the PoC are left up to the builder, but the idea is show off the viability of the concept.
3.  Executable demo proving the OP Stack state transition between two blocks: An implementation of the ZKP working end to end and integrated with a live OP Stack chain. This should include instructions which allow anyone to test the proving system themselves.

These milestones mark the completion of the proposal.

Once the proposal has been completed, a final major milestone is the adoption of the ZKP by Optimism Governance. At this point the ZKP may be voted in as a default option in the Superchain bridge, making it a core component of the OP Stack. This is outside of the scope of this proposal but is included here to illustrate the critical importance of this Mission and the massive impact these proofs may have.

## **How should RetroPGF badgeholders measure impact upon completion of this Foundation Mission (RFP)?**

*   Total number of token bridges using this proof system
*   Open-source ZKP research shared with the broader community making it easier for future ZKP builders
*   Fees collected by provers for their proving services

## Application instructions

_To apply for this RFP, please complete the form in the expandable section below and leave your response as a comment on this issue thread below. Submissions will be open until June 28, at which time the Foundation will review all submissions and select up to three individuals/teams to complete the work defined here._

Submission form

_Copy the entire application below and leave a comment on this issue with your answers completed. A representative from the Optimism Foundation may reach out using the contact info provided to request more information as necessary._

## Foundation Mission (RFP) Application

**Please verify that you meet the qualifications for submitting at the above [Tier](https://gov.optimism.io/t/collective-trust-tiers/5877/2)**

*   **Alliance Lead:** Please specify the best point of contact for your team
*   **Contact info:**
*   **L2 recipient address:**
*   **Please list the members of your Alliance and link to any previous work:**

Read more about Alliances [here](https://gov.optimism.io/t/season-4-alliance-guide/5873)

* * *

**What makes your Alliance best-suited to execute this Mission?**

*   \[...\]
*   \[...\]

**Please describe your proposed solution based on the above Solution Criteria (if applicable):**

*   \[...\]
*   \[...\]

**Please outline your step-by-step plan to execute this Mission, including expected deadlines to complete each peice of work:**

*   \[...\]
*   \[...\]

**Please define the [critical milestone(s)](https://gov.optimism.io/t/grant-policies/5833) that should be used to determine whether you’ve executed on this proposal:**

*   \[...\]
*   \[...\]

**Please list any additional support your team would require to execute this mission (financial, technical, etc.):**

*   \[...\]
*   \[...\]

**Grants are awarded in OP, locked for one year. Please let us know if access to upfront capital is a barrier to completing your Mission and you would like to be considered for a small upfront cash grant:** _(Note: there is no guarantee that approved Missions will receive up-front cash grants.)_

*   \[...\]

Please check the following to make sure you understand the terms of the Optimism Foundation RFP program:

*    I understand my grant for completing this RFP will be locked for one year from the date of proposal acceptance.
*    I understand that I will be required to provide additional KYC information to the Optimism Foundation to receive this grant
*    I understand my locked grant may be clawed back for failure to execute on critical milestones, as outlined in the [Operating Manual](https://github.com/ethereum-optimism/OPerating-manual/blob/main/manual.md#valid-proposal-types)
*    I confirm that I have read and understand the [grant policies](https://gov.optimism.io/t/token-house-grant-policies/5833)
*    I understand that I will be expected to following the public grant reporting requirements outlined [here](https://gov.optimism.io/t/suggested-public-reporting-requirements-for-grantees/4176)

\-- end of application --

* * *

Reactions are currently unavailable

## Activity

[Next](/ethereum-optimism/ecosystem-contributions/issues/61?timeline_page=1)

1.  [![](https://avatars.githubusercontent.com/u/1016190?s=64&u=58eab6c87c6ecee317aa1e4bf866679dc8939309&v=4)bdresser](/bdresser)
    
    added
    
    [Foundation Mission RequestA request for proposals for a specific work item.](/ethereum-optimism/ecosystem-contributions/issues?q=state%3Aopen%20label%3A%22Foundation%20Mission%20Request%22)A request for proposals for a specific work item.
    
    [on May 30, 2023](https://github.com/ethereum-optimism/ecosystem-contributions/issues/61#event-9380982219)
    
2.  [![](https://avatars.githubusercontent.com/u/1016190?s=64&u=58eab6c87c6ecee317aa1e4bf866679dc8939309&v=4)bdresser](/bdresser)
    
    added this to [Optimism Ecosystem Contributions 🔴✨](https://github.com/orgs/ethereum-optimism/projects/31)[on May 30, 2023](https://github.com/ethereum-optimism/ecosystem-contributions/issues/61#event-15225445018)
    
3.  [![](https://avatars.githubusercontent.com/u/1016190?s=64&u=58eab6c87c6ecee317aa1e4bf866679dc8939309&v=4)bdresser](/bdresser)
    
    added
    
    [Intent: Technical Decentralization](/ethereum-optimism/ecosystem-contributions/issues?q=state%3Aopen%20label%3A%22Intent%3A%20Technical%20Decentralization%22)
    
    [on May 30, 2023](https://github.com/ethereum-optimism/ecosystem-contributions/issues/61#event-9381004451)
    
4.  [![](https://avatars.githubusercontent.com/u/1016190?s=64&u=58eab6c87c6ecee317aa1e4bf866679dc8939309&v=4)bdresser](/bdresser)
    
    moved this to Open in [Optimism Ecosystem Contributions 🔴✨](https://github.com/orgs/ethereum-optimism/projects/31)[on May 30, 2023](https://github.com/ethereum-optimism/ecosystem-contributions/issues/61)
    
5.  ### wangtsiao commented on Jun 5, 2023
    
    [![@wangtsiao](https://avatars.githubusercontent.com/u/70847926?v=4&size=48)](/wangtsiao)
    
    [wangtsiao](/wangtsiao)
    
    [on Jun 5, 2023](https://github.com/ethereum-optimism/ecosystem-contributions/issues/61#issuecomment-1575950146)
    
    More actions
    
    I plan to give my zk solution and apply the foundation, but I am `Ember Tier`, am I eligible to apply? Because I see the `Proposal Tier` is `Phoenix`, which people generally don't have.
    
    Love the OP's zk plan! But would you lower the proposal tier, so that more developers familiar with zk can join and build?
    
    ❤️React with ❤️2Reacted by Chen Kai and Waylon Jepsen ✨
    
6.  ### GrapeBaBa commented on Jun 5, 2023
    
    [![@GrapeBaBa](https://avatars.githubusercontent.com/u/3657859?u=43bf5f96157816192eab4a1f6f40a6a9384e0a88&v=4&size=48)](/GrapeBaBa)
    
    [GrapeBaBa](/GrapeBaBa)
    
    [on Jun 5, 2023](https://github.com/ethereum-optimism/ecosystem-contributions/issues/61#issuecomment-1576281274)
    
    More actions
    
    > I plan to give my zk solution and apply the foundation, but I am `Ember Tier`, am I eligible to apply? Because I see the `Proposal Tier` is `Phoenix`, which people generally don't have.
    > 
    > Love the OP's zk plan! But would you lower the proposal tier, so that more developers familiar with zk can join and build?
    
    [@wangtsiao](https://github.com/wangtsiao) If you try this one, I am glad to join if you are not care.
    
    ❤️React with ❤️1Reacted by wangtsiao
    
7.  ### bdresser commented on Jun 8, 2023
    
    [![@bdresser](https://avatars.githubusercontent.com/u/1016190?u=58eab6c87c6ecee317aa1e4bf866679dc8939309&v=4&size=48)](/bdresser)
    
    [bdresser](/bdresser)
    
    [on Jun 8, 2023](https://github.com/ethereum-optimism/ecosystem-contributions/issues/61#issuecomment-1583207409)
    
    CollaboratorAuthor
    
    More actions
    
    [@wangtsiao](https://github.com/wangtsiao) [@GrapeBaBa](https://github.com/GrapeBaBa) apologies, this should have been listed as `Fledgling` tier per the descriptions [here](https://gov.optimism.io/t/collective-trust-tiers/5877#fledgling-tier-eligible-to-receive-up-to-350k-op-3) – I have updated the original RFP to clarify.
    
    If you find that an RFP you are interested in is listed at a Tier that you haven't reached yet, you can:
    
    *   Submit a proposal for a smaller part of the RFP
    *   Reach out to another Alliance that submits a proposal
    *   Post in the #alliances channel on Discord to see if anyone one else wants to join forces.
    
8.  ### wangtsiao commented on Jun 9, 2023
    
    [![@wangtsiao](https://avatars.githubusercontent.com/u/70847926?v=4&size=48)](/wangtsiao)
    
    [wangtsiao](/wangtsiao)
    
    [on Jun 9, 2023](https://github.com/ethereum-optimism/ecosystem-contributions/issues/61#issuecomment-1583876518)
    
    More actions
    
    [@bdresser](https://github.com/bdresser) Thanks for your clarification, love this RFP! BUIDL!
    
    ❤️React with ❤️1Reacted by bdresser
    
9.  ### ashutosh887 commented on Jun 10, 2023
    
    [![@ashutosh887](https://avatars.githubusercontent.com/u/71774735?u=569a0156f88bdec70e6d48067c9999e5728261d1&v=4&size=48)](/ashutosh887)
    
    [ashutosh887](/ashutosh887)
    
    [on Jun 10, 2023](https://github.com/ethereum-optimism/ecosystem-contributions/issues/61#issuecomment-1585786593)
    
    More actions
    
    [@bdresser](https://github.com/bdresser) I would like to work on this!
    
10.  ### bdresser commented on Jun 12, 2023
     
     [![@bdresser](https://avatars.githubusercontent.com/u/1016190?u=58eab6c87c6ecee317aa1e4bf866679dc8939309&v=4&size=48)](/bdresser)
     
     [bdresser](/bdresser)
     
     [on Jun 12, 2023](https://github.com/ethereum-optimism/ecosystem-contributions/issues/61#issuecomment-1587742708)
     
     CollaboratorAuthor
     
     More actions
     
     cross-posting a [proposal](https://gov.optimism.io/t/draft-op-stack-zero-knowledge-proof-mission-proposal/6089) for this RFP posted by [@wangtsiao](https://github.com/wangtsiao) on the governance forum
     
     🚀React with 🚀2Reacted by wangtsiao and Chen Kai
     
11.  ### bdresser commented on Jun 12, 2023
     
     [![@bdresser](https://avatars.githubusercontent.com/u/1016190?u=58eab6c87c6ecee317aa1e4bf866679dc8939309&v=4&size=48)](/bdresser)
     
     [bdresser](/bdresser)
     
     [on Jun 12, 2023](https://github.com/ethereum-optimism/ecosystem-contributions/issues/61#issuecomment-1587743455)
     
     Last edited by bdresser
     
     CollaboratorAuthor
     
     More actions
     
     > [@bdresser](https://github.com/bdresser) I would like to work on this!
     
     Glad to hear it [@ashutosh887](https://github.com/ashutosh887) ! I'd suggest posting in the #alliances channel on the Optimism Discord, or reaching out to other teams submitting proposals to see if anyone is looking for additional help.
     
12.  ### Abuchtela commented on Jun 27, 2023
     
     [![@Abuchtela](https://avatars.githubusercontent.com/u/84213452?v=4&size=48)](/Abuchtela)
     
     [Abuchtela](/Abuchtela)
     
     [on Jun 27, 2023](https://github.com/ethereum-optimism/ecosystem-contributions/issues/61#issuecomment-1610181574)
     
     More actions
     
     I would love to help work on this
     
13.  ### Cofson commented on Jun 28, 2023
     
     [![@Cofson](https://avatars.githubusercontent.com/u/41572590?v=4&size=48)](/Cofson)
     
     [Cofson](/Cofson)
     
     [on Jun 28, 2023](https://github.com/ethereum-optimism/ecosystem-contributions/issues/61#issuecomment-1611427459)
     
     More actions
     
     Submitted [one more proposal](https://gov.optimism.io/t/rfp-submission-op-stack-zero-knowledge-proof-zkmips/6298) - thanks for posting this RFP [@bdresser](https://github.com/bdresser) !
     
14.  ### O1Partners commented on Jun 28, 2023
     
     [![@O1Partners](https://avatars.githubusercontent.com/u/137942687?v=4&size=48)](/O1Partners)
     
     [O1Partners](/O1Partners)
     
     [on Jun 28, 2023](https://github.com/ethereum-optimism/ecosystem-contributions/issues/61#issuecomment-1611488039)
     
     More actions
     
     ## Foundation Mission (RFP) Application
     
     **Please verify that you meet the qualifications for submitting at the above [Tier](https://gov.optimism.io/t/collective-trust-tiers/5877/2)**
     
     *   **Alliance Lead:** Phil Kelly
     *   **Contact info:** [partners@o1labs.org](https://www.notion.so/O-1-Labs-DESIGN-HUB-ce737710ddea4bc0b6681691e47ddb7d?pvs=21)
     *   **L2 recipient address:** 0x3f190781756A87750251aDb081e3e2e55de4220d
     *   **Please list the members of your Alliance and link to any previous work:**
     *   [O(1) Labs](https://o1labs.org/) is responding to this RFP. O(1) Labs is a company that specializes in developing ZKP infrastructure and tooling for Web3. The team was formed in 2017, and comprises of 40+ cryptographers, engineers and other experts. We are globally distributed with team members in Europe, North America, South America and Asia.
     *    I understand my grant for completing this RFP will be locked for one year from the date of proposal acceptance.
     
     Our ZKP-related work includes:
     
     *   Incubating the [Mina](https://minaprotocol.com/) Protocol (the world's first ZKP-based, succinct, L1 blockchain)
     *   [SnarkyJS](https://docs.minaprotocol.com/zkapps/snarkyjs) (SDK for building client-side ZKP applications)
     *   [Kimchi](https://o1-labs.github.io/proof-systems/specs/kimchi.html) (plonk-based ZKP proving system that does not require trusted set up)
     *   [Pickles](https://o1-labs.github.io/proof-systems/specs/pickles.html) (halo2-style recursion library for Kimchi)
     
     * * *
     
     **What makes your Alliance best-suited to execute this Mission?**
     
     *   **We're one of the most experienced teams in the ZKP space, with a track record of successful delivery:** O(1) Labs has been working with ZKP technology since 2017 and we have proven our ability to deliver on leading class ZKP infrastructure. We incubated the Mina Protocol, which has been running in production since early 2021. We developed and released a SDK for client side ZKPs last year. We have delivered regular updates to both sets of code.
     *   **We have a deep bench across all relevant areas of expertise:** We are a ZKP-focused engineering organization, with dedicated teams and expertise (theory, design and implementation) across:
         *   Cryptography
         *   Protocol
         *   SDKs
         *   Infrastructure and automation
     *   **We prioritize [OSS](https://github.com/o1-labs) and build in the open.**
     *   **We're stable:** We are financially stable, with an experienced leadership team.
     *   **We're confident in our design:** Our proposed approach combines two well-tested stacks to optimize across OP Stack performance and interaction with Ethereum: Our own PLONK-ish proving system, which has been used in production for over 2 years, and the KZG scheme that the Ethereum community recently implemented to prepare for EIP-4844. This approach both delivers a good set of technical benefits, and carries a lower delivery and operational risk than a fully-new build.
     *   **We're enthusiastic and committed to this mission:** As a measure of our commitment, we have already invested resources in building working (partial-scope) POC code in response to this RFP. This gives us increased confidence in the design and the predicted performance of our proposed solution.
     
     **Please describe your proposed solution based on the above Solution Criteria**
     
     **Solution Overview (definition of some key terms are set out at the end of this section)**
     
     Our proposed solution is to implement a fault-proof-program-compatible MIPS VM with efficient instruction execution embedded inside a Nova-folding-style bn128-kzg-plonkish system with deep Keccak support for efficient pre-image oracle access.
     
     This would be used to prove arbitrary fault proof program execution traces. We believe we found a good point in the tradeoff-space that maximizes both OP stack compatibility and performance.
     
     The proof system would be Kimchi, a Halo2-like PLONKish system currently configured with an inner-product-argument style polynomial commitment scheme. Kimchi powers the Mina Protocol. It supports verifiable computation using traditional turing-machine-based instruction sets.
     
     Kimchi is designed to have a swappable backend and while the current implementation is defined over Pasta curves using an inner-product-argument-based polynomial commitment scheme (Pasta-IPA), the proposed implementation would swap in the KZG commitment scheme using the bn128 curves (bn128-KZG).
     
     ### Solution Overview
     
     [![MIPS\_zkVM\_(1)](https://private-user-images.githubusercontent.com/137942687/249509427-3d6612b8-99e5-49d6-8594-eca162768d39.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3OTI3NDk3MzYsIm5iZiI6MTc5Mjc0OTQzNiwicGF0aCI6Ii8xMzc5NDI2ODcvMjQ5NTA5NDI3LTNkNjYxMmI4LTk5ZTUtNDlkNi04NTk0LWVjYTE2Mjc2OGQzOS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYxMDIzJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MTAyM1QwOTU3MTZaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0zNGRiMDQ2MzE0ZmQ0NTA5MTJiOTdiMzI4OTI4NzFhMzk3ZWM1MzU5NDc2NTc2NDk5ZGYwZjMxZmExYzg5OTc4JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZyZXNwb25zZS1jb250ZW50LXR5cGU9aW1hZ2UlMkZwbmcifQ.VLHXPsF8yJ3Xn3JHuU76I3ou3VbdrB76rmVlm6m9kak)](https://private-user-images.githubusercontent.com/137942687/249509427-3d6612b8-99e5-49d6-8594-eca162768d39.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3OTI3NDk3MzYsIm5iZiI6MTc5Mjc0OTQzNiwicGF0aCI6Ii8xMzc5NDI2ODcvMjQ5NTA5NDI3LTNkNjYxMmI4LTk5ZTUtNDlkNi04NTk0LWVjYTE2Mjc2OGQzOS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYxMDIzJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MTAyM1QwOTU3MTZaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0zNGRiMDQ2MzE0ZmQ0NTA5MTJiOTdiMzI4OTI4NzFhMzk3ZWM1MzU5NDc2NTc2NDk5ZGYwZjMxZmExYzg5OTc4JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZyZXNwb25zZS1jb250ZW50LXR5cGU9aW1hZ2UlMkZwbmcifQ.VLHXPsF8yJ3Xn3JHuU76I3ou3VbdrB76rmVlm6m9kak)
     
     ### Solution Flow
     
     > The proposer feeds the inputs to the fault proof MIPS binary which the bn128-kzg Kimchi system can interpret and ZK-prove the execution trace. Just as before, pre-image syscalls are resolved using the unmodified OP Stack pre-image oracle system. Finally, the proof gets sent to a smart contract on Ethereum L1 and then, if valid, updates state on the L1.
     
     ### Components
     
     *   Fault-proof-program-compatible MIPS VM
         *   Cannon emulates big-endian 32-bit MIPS instructions that are used by the Go compiler/runtime. The current PoC partially implements this instruction set and can be used to prove the execution of MIPS programs. Using Kimchi’s VM execution engine, we plan to deliver a to-spec implementation of this MIPS ISA.
     *   Nova-folding-style bn128-kzg-plonkish Kimchi
         *   We will swap the Pasta-IPA backend for Kimchi out for a bn128-KZG one so that it will be practical to verify on the EVM without any non-standard precompiles. Switching this backend prevents typical proof-carrying-data-based recursion which is currently built via the “Pickles” layer, so instead we will implement a Nova-style folding scheme by adapting Kimchi’s existing constraint description (aka “expression”) framework, using it to bi-linearize the constraints and compute the required “error” term.
     *   Deep Keccak support
         *   One component of the OP stack system is the pre-image data oracle which is responsible for getting information about the EVM into the MIPS world. The OP stack currently uses the existing ledger which is built on top of Keccak hashes as a baseline. An example workflow: start with hash of block, then get the block and lookup hash of ledger, the first layer of the ledger and request the next layer, etc. With preprocessing we can reduce the loading step to a single layer of lookup from start of ledger → account to reduce the number of hashes in Keccak land.
         *   By unfolding keccak hashing as a dedicated sub-proof, and using the “bit expansion” approach to calculating XORs and ANDs, as well as a generalization of it to calculate sequences of XORs/ANDs, we can efficiently process Keccak hashes inside the proof system
     *   Efficient VM instruction selection optimization
         *   The current PoC naively executes every instruction at every step and masks out the parts of the computation that are unused with a one-hot vector.
         *   Instead, we can generate a dedicated sub-proof for each instruction kind, which only executes the operations necessary for that instruction, and only “pay-for-what-you-use”.
         *   We expect around a 20x speedup after this optimization given that there are 30+ MIPS instructions that we pay for every step at the moment.
     
     ### Out of scope
     
     *   Ethereum L1 Verifier Smart Contract
         *   This proposal does not cover the implementation of an actual verifier on L1, but as discussed above, the technical choices ensure this is feasible.
     
     ### Definitions
     
     *   _Polynomial commitment scheme_
         *   _A polynomial commitment scheme describes a mechanism to commit to a polynomial. This commitment can be shared publicly, and then can be used to verify that evaluations at specific points are valid (an opening of the commitment). These are used at the hearts of most proof systems, including Kimchi._
     *   _Kimchi_
         *   _Kimchi is a Halo2-like PLONKish proving system currently configured with an inner-product-argument style polynomial commitment scheme and defined over the Pasta curves (Pasta-IPA). Kimchi supports verifiable computation using traditional turing-machine-based instruction sets. It is designed to have a swappable backend and this feature will be used by this proposed solution._
     *   _Pasta-IPA vs bn128-KZG_
         *   _The Pasta-IPA configuration enables many nice properties for the proof system (universality, efficient recursion with Pickles (the recursion layer on Mina), etc); however, it is inefficient to verify directly on the EVM without extra precompiles. Due to the existence of certain bn128 Ethereum precompiles, it is more effective to use a backend using the KZG commitment scheme over the bn128 curves._
     *   _Nova-style folding_
         *   _The Nova family of proof systems achieves recursion-like computation via incrementally-verifiable-computation-style (IVC) folding. You can create a chain of partially completed proofs that can be efficiently completed. For proving machine code execution traces in low-degree constraint scenarios like this one, folding is more efficient than recursion, but requires trusted communication between all parties involved in the protocol._
     
     Criteria
     
     *   **Performance**
         *   The following estimates are based off of the prototype after applying the expected 20x speedup of the VM proving optimization:
             *   Running cannon against block 8813569 and 8813570 on Goerli using the configuration in the [Cannon example](https://github.com/ethereum-optimism/optimism/tree/develop/cannon#usage), just changing the l2.head/block-number and keeping all else as equal.
                 *   Running against block 8813569 uses 44,540,000,000 MIPS instruction-steps
                 *   Running against block 8813570 uses 44,420,000,000 MIPS instruction steps
             *   The difference in gas between those blocks is ~51,500 gas and the difference in MIPS instructions taken is 120M. This implies a cost of ~2300 MIPS instructions per 1 gas.
             *   On a modern i9-12900K, 64GB DDR5 machine, it takes 4.75s to run a 2^16 MIPS instruction benchmark using our proof-of-concept, and this translates to 28.5 gas in 4.75 seconds or 6 gas per machine-second. Or after the speedup, 28.5 gas in 0.2375s or 120 gas per machine-second.
             *   Using Hetzner machine [https://www.hetzner.com/dedicated-rootserver/ex101](https://www.hetzner.com/dedicated-rootserver/ex101) as a benchmark, running this machine costs around $100 per month (depending on the euro exchange rate). At 120 gas per machine-second, this is 316M gas per $100 or 3.16M gas per $1 or around $0.0065 per token transfer assuming 21,000 gas per transfer before any of the fixed-overhead costs are applied.
             *   There is also a fixed overhead for a fault-proof-program execution that’s on the order of 20-50B MIPS instructions — further investigation is needed to see to what extent this impacts costs when proving many transactions at once. Even after applying a generous 20x penalty multiplier due to fixed costs we still estimate less than $0.15 per txn.
         *   Note that other planned performance optimizations (outlined in the ‘Future phases’ section) are out-of-scope of the initial grant, but are expected to speed the compute up by at least an order of magnitude.
     *   **Latency**
         *   Before a number of significant optimizations, and for the purposes of the initial work within the scope of this grant only, running a single state transition of around 50B instructions serially with the planned in-scope work on a single Hetzner machine [https://www.hetzner.com/dedicated-rootserver/ex101](https://www.hetzner.com/dedicated-rootserver/ex101) should take about 2 days.
         *   Although out of scope of this grant:
             *   Both proving and folding can be parallelized across machines which should give us at least an order of magnitude speed up if properly used.
             *   This scales multiplicatively with the other order of magnitude of performance optimizations that can be applied later as mentioned elsewhere.
     *   **Complexity**
         *   Kimchi is currently open-sourced [https://github.com/o1-labs/proof-systems](https://github.com/o1-labs/proof-systems) and very well-documented: [https://o1-labs.github.io/proof-systems/](https://o1-labs.github.io/proof-systems/) . Kimchi is currently roughly ~35k lines of code including doc-comments about ~2k lines of parameters and excluding tests. The proposed changes are expected to add 5-10k lines of modifications to generalize kimchi; 3-5k lines of dedicated code (including whitespace, trait boilerplate, doc-comments).
     *   **Robustness**
         *   Kimchi is built into Mina Protocol which has been securing the mainnet chain, including a peak market cap of over $6 Billion, with no security breaches since launch in March 2021. Pasta-IPA Kimchi is a part of the Mina’s Berkeley hardfork incentivized testnet which is actively ongoing. The changes are relatively straightforward and our team has experience delivering reliable ZK proof system software.
     *   **Security**
         *   The same assumptions as any kzg-bn128-based EVM-friendly snark system: there is a required trusted setup, but we can reuse the powers-of-tau danksharding ceremony parameters.
         *   There are 128 bits of security with the bn128 curves.
         *   We also rely on the soundness of the KZG commitment scheme and the hardness the discrete logarithm problem as with any elliptic curve based proving system.
         *   As with any ZK circuit-based solution, the instruction logic will need to be encoded as polynomial constraints which may require a dedicated audit.
     *   **OP Stack Compatibility**
         *   The proposed solution was carefully designed to minimize changes to the existing OP stack system. There are no fundamental changes required beyond excising the existing Cannon system. To be explicit, no precompiles are required.
     
     **Please outline your step-by-step plan to execute this Mission, including expected deadlines to complete each piece of work:**
     
     We have grouped the major elements of work into Milestone phases, and detailed the elements of each phase in the table below, with time estimates attached.
     
     **Grant 1**
     
     Workstream
     
     Expected length of each Phase
     
     Phase 1 / Milestone 1 - Complete and confirm specification with OP Labs: Finalized written specification
     
     4 weeks
     
     Phase 2 / Milestone 2: Demo of the ZKP being used to prove the OP Stack state transition: Low-level optimized Keccak in Kimchi, prover hashing changes, Keccak sys-call interface, Folding, Kzg-bn128 abstractions, VM instruction selection, and the complete VM ISA, instrument for the state transition flow.
     
     10 weeks
     
     Phase 3 / Milestone 3: An implementation of the ZKP working end to end and integrated with a live OP Stack chain , CLI host / pre-image integration, Documentation
     
     2 weeks
     
     **Future Grants / Phases**
     
     Not included in the scope of this work but listed below for context and future consideration are some additional potential phases of work to complete and optimize availability of the solution within OP Stack:
     
     *   GPU optimizations
     *   Additional CLI config / features
     *   Ethereum Verification Smart Contract
     *   Infrastructure for parallelization of proving
     *   RISCV-64
     *   Running the prover backend operationally
     *   Interop with Mina mainnet
     *   Ongoing support and maintenance
     
     **Please define the [critical milestone(s)](https://gov.optimism.io/t/grant-policies/5833) that should be used to determine whether you’ve executed on this proposal:**
     
     *   The milestones are as per the RFP outlined in the workstreams above:
         *   Specification sign-off
         *   Demo of a state change
         *   Demo of tool proving state change on the live chain
     
     **Please list any additional support your team would require to execute this mission (financial, technical, etc.):**
     
     *   Design review and sign off
     *   Communication channel (Telegram/Slack etc.) with OP team for ad-hoc questions.
     *   Further optimizations would require additional grants and specific targets in terms of CPU/Memory/Clock time etc.
     
     **Grants are awarded in OP, locked for one year. Please let us know if access to upfront capital is a barrier to completing your Mission and you would like to be considered for a small upfront cash grant:** _(Note: there is no guarantee that approved Missions will receive up-front cash grants.)_
     
     *   Not an issue for us.
     
     Please check the following to make sure you understand the terms of the Optimism Foundation RFP program:
     
     *    I understand that I will be required to provide additional KYC information to the Optimism Foundation to receive this grant
     *    I understand my locked grant may be clawed back for failure to execute on critical milestones, as outlined in the [Operating Manual](https://github.com/ethereum-optimism/OPerating-manual/blob/main/manual.md#valid-proposal-types)
     *    I confirm that I have read and understand the [grant policies](https://gov.optimism.io/t/token-house-grant-policies/5833)
     *    I understand that I will be expected to following the public grant reporting requirements outlined [here](https://gov.optimism.io/t/suggested-public-reporting-requirements-for-grantees/4176)
     *   *   end of application --
     
     👍React with 👍3Reacted by prz23, Naamah and kumosoukai
     
     ❤️React with ❤️30Reacted by Steve Pack, Joseandro Luiz, Karl Floersch, msf3108, feynyman, s7v7nislands, Florian Kluge, Taem Park, Waylon Jepsen ✨, Ino Murko and 20 more
     
     🚀React with 🚀8Reacted by Barrie Byron, Florian Kluge, Steven Platt, PhD, 0xbundler, Nico, Butterbum.eth, Naamah and kumosoukai
     
     👀React with 👀1Reacted by kumosoukai
     
15.  ### qizhou commented on Jun 28, 2023
     
     [![@qizhou](https://avatars.githubusercontent.com/u/2541286?v=4&size=48)](/qizhou)
     
     [qizhou](/qizhou)
     
     [on Jun 28, 2023](https://github.com/ethereum-optimism/ecosystem-contributions/issues/61#issuecomment-1611598205)
     
     More actions
     
     ## Foundation Mission (RFP) Application
     
     **Please verify that you meet the qualifications for submitting at the above [Tier](https://gov.optimism.io/t/collective-trust-tiers/5877/2)**
     
     *   **Alliance Lead:** Qi Zhou
         
     *   **Contact info:** [qizhou@ethstorage.io](mailto:qizhou@ethstorage.io)
         
     *   **L2 recipient address:** 0x83Ca8766Bac8018a5ff95A7E20F4a21370F147EC
         
     *   **Please list the members of your Alliance and link to any previous work:**
         
         *   Qi Zhou: Dr. Qi Zhou is 

[... truncated ...]