Challenges
Most Useful Web3 Tool
We would like to be noticed for building out project on Cartesi, which is in turn running on Polygon Mumbai. We have built an on-chain ZK Prover inside the Cartesi VM (a Layer 2 optimistic rollup). Usages: - L2 to L1 ZK transfers. - Dual Rollup: ZK + Optimistic - Universal ZK Bridge
Best project using Filecoin Virtual Machine (FVM)
We have built an on-chain ZK Prover inside the Cartesi VM (a Layer 2 optimistic rollup). This proves feasibility for development of an Universal ZK Bridge, which would be safer by the existing (consensus based and/or Time Locked Hash based) bridges. Hopefully Cartesi would be deployed on FVM (permissionlessly) to allow this.
Launch Cross-chain apps & features with Swing’s API, SDK
We would like to be noticed for related work: We have built an on-chain ZK Prover inside the Cartesi VM (a Layer 2 optimistic rollup RISC-V machine). Usages: - L2 to L1 ZK transfers. - Dual Rollup: ZK + Optimistic - Universal ZK Bridge
Build on RISC Zero or Integrate RISC Zero into your project
We would like to be noticed for related work: We have built an on-chain ZK Prover inside the Cartesi VM (a Layer 2 optimistic rollup RISC-V machine). Usages: - L2 to L1 ZK transfers. - Dual Rollup: ZK + Optimistic - Universal ZK Bridge
Developer Tooling
We would like to be noticed for out achievement of deploying an on-chain ZK Prover (not just Verifier).
Applied ZK, with a side of Scroll
We would like to be noticed, as eventually we would use the EVM state transition proof from Scroll in our project (if allowed). This would achieve our goal of Dual Rollup (ZK + Optimistic in one). We achieved deploying an on-chain ZK Prover inside the Cartesi VM (a merkelized RISC-V machine).
Use a GMP Protocol to Remotely Call a Contract
We would like to be noticed for related work: We have built an on-chain ZK Prover inside the Cartesi VM (a Layer 2 optimistic rollup RISC-V machine). Related: Feasibility proof for development of an Universal ZK Bridge, which would be safer by the existing (consensus based and/or Time Locked Hash based) bridges.
#BUIDLathon 2023 Infrastructure + Scalability
We have built an on-chain ZK Prover inside the Cartesi VM (a Layer 2 optimistic rollup). Usages: - L2 to L1 ZK transfers. - Dual Rollup: ZK + Optimistic - Universal ZK Bridge
Building DApps using Cartesi Rollups
We have built an on-chain ZK Prover inside the Cartesi VM (a Layer 2 optimistic rollup). Usages: - L2 to L1 ZK transfers. - Dual Rollup: ZK + Optimistic - Universal ZK Bridge
Transparent Bridge
We have built an on-chain ZK Prover inside the Cartesi VM (a Layer 2 optimistic rollup). This proves feasibility for development of an Universal ZK Bridge, which would be safer by the existing (consensus based and/or Time Locked Hash based) bridges.
Create a Developer Tool for the AttestationStation
We have built an on-chain ZK Prover inside the Cartesi VM (a Layer 3 optimistic rollup, on top of Optimism). Usages: - L3 to L2 ZK transfers. - L3 Dual Rollup: ZK + Optimistic - Universal ZK Bridge
Project details
We are providing a proof-of-concept mechanism of Dual Rollup: ZK Rollup and Optimistic Rollup in one. Cartesi already provides Optimistic Rollup functionality. In addition, we run ZK Rollup functionality, which can be "claimed" at any time by anyone. If the Optimistic Rollup rolls back as a result of a fraud proof, next time it proceeds is going to be from the new Ethereum -Layer 1 (L1) state, which fits well.
To achieve this we run zero-knowledge proofs (actually Validity Proofs) where both the Prover and the Verifier can run on a public blockchain.
Running the verifier on Ethereum Virtual Machine (EVM) is relatively inexpensive and feasible for many applications. However, running the prover requires more computational resources, and as such is running in a Cartesi virtual machine.
We deploy Aztec PLONK Validity Proofs written in Noir, into Cartesi virtual machine executable provers and EVM verifiers.
The limitation (as a result of feasibility) is that the Layer 2 ZK Rollup is running an EVM. Since this is a proof of concept, instead of proofs of state transitions of the EVM, we are deploying a dummy Noir program, just to show that this is feasible. In reality, the claim would have to include the new EVM state (or difference from the previous) along with the proof that the new state resulted from execution of the sequence of EVM instructions on L2.