Skip to content

Commit 0927dc4

Browse files
authored
update plasmafold (#323)
1 parent 14e4175 commit 0927dc4

1 file changed

Lines changed: 41 additions & 13 deletions

File tree

data/projects/plasma_fold.ts

Lines changed: 41 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -11,26 +11,55 @@ export const plasmaFold: ProjectInterface = {
1111
en: {
1212
tldr: "Integrating folding schemes into plasma-based L2 solutions for efficient and scalable Ethereum transactions.",
1313
description: `
14-
### Leveraging Folding Schemes for Efficient L2 Solutions
14+
## Plasma Fold
1515
16-
Our project builds on the external [intmax](https://www.intmax.io/) design by integrating folding schemes into their plasma-based L2 approach. While intmax uses client-side validation with minimal on-chain data and validity proofs to achieve high throughput, its reliance on resource-intensive proving can strain low-end devices. Folding schemes—with low recursive overhead and minimal memory usage—offer a powerful solution to streamline this process.
16+
**Reimagining Plasma with Folding Schemes**
1717
18-
### Overview & Key Contributions
18+
Plasma Fold is an experimental Layer 2 (L2) design that combines the original Plasma architecture with modern zero-knowledge folding schemes to dramatically scale Ethereum transaction throughput. By leveraging recent advances in Incremental Verifiable Computation (IVC) and folding-based proof systems, Plasma Fold achieves high-speed client-side proving while keeping on-chain data to a minimum.
1919
20-
By combining plasma's efficient data availability with folding schemes, our approach significantly reduces the resource demands on client devices. This integration:
20+
Unlike traditional rollups that post extensive transaction data to L1, Plasma Fold operates using a *minimal data availability* model inspired by Intmax, where only essential metadata—like tree roots and signer indices—are recorded onchain. Validity is ensured through user-generated proofs, making this model far more efficient for resource-constrained environments.
2121
22-
- **Optimizes Client-Side Proving:** Folding schemes accelerate proof generation while cutting down memory requirements, making the system more accessible.
23-
- **Maintains a Low On-Chain Footprint:** Leveraging plasma's lightweight data posting for deposits, withdrawals, and checkpoints ensures fast, secure transaction processing.
24-
- **Boosts Throughput:** The synergy between folding schemes and plasma validity proofs could dramatically enhance transaction-per-second rates.
22+
## Why Plasma Fold?
2523
26-
### Objectives & Impact
24+
Most L2s today struggle to scale without relying on increasingly expensive data availability solutions (e.g., blobs). Plasma Fold offers a low-cost, high-throughput alternative. Inspired by Vitalik Buterin’s vision of a Plasma-EVM hybrid, Plasma Fold explores the use of folding schemes to support lightweight client-side proving—ideal for mobile or browser-based clients. In theory, this architecture could enable transaction rates in the range of 90k–260k TPS, matching or exceeding centralized systems like VISA.
2725
28-
Our goal is to design and benchmark a client-friendly zk/plasma scaling solution for Ethereum. By reducing the computational load, we aim to make scalable L2 solutions practical for a wide range of devices.
26+
## Key Innovations
2927
30-
### Additional Resources
28+
- **Client-Side Proving with Folding Schemes:** Users generate recursive ZK proofs on their devices to attest to their own balances and transactions, minimizing trust and computation on the L1.
29+
- **UTXO-Based Design with IVC:** Transactions are modeled as UTXO trees, allowing users to maintain and prove their own balances incrementally across time.
30+
- **Minimal Onchain Footprint:** Only block roots, nullifier indices, and signer bitmaps are posted on L1—greatly reducing gas costs and data needs.
31+
- **Instant Exits & Offline-Friendliness:** Users can exit the system at any time using a locally stored proof. They do not need to stay online between blocks unless actively transacting.
32+
- **Composable and Future-Proof:** Designed to eventually support multiple assets, order books, and potentially even programmable features.
3133
32-
- [intmax: Plasma-based L2 scaling](https://www.intmax.io/)
33-
- [Deep dive into intmax](https://www.pierredm.xyz/posts/intmax)
34+
## Status
35+
36+
- **Stage:** Research and Prototyping
37+
- **Current Focus:** Implementing and benchmarking core circuits
38+
- **Target Output:** A technical paper and reference implementation
39+
- **Team Lead:** Pierre Daix-Moreux
40+
- **Collaborators:** Chengru
41+
42+
## Timeline & Milestones
43+
44+
- **Q2 2025:** Initial circuit design and benchmarks against Plonky2
45+
- **Q2–Q3 2025:** Drafting formal paper; collaborative review with Intmax
46+
- **Q3 2025:** Reference implementation using Sonobe’s Nova-based tooling
47+
- **Beyond:** Explore multi-asset support, privacy enhancements, and programmability
48+
49+
## Learn More
50+
51+
- [Technical Write-Up on Intmax2](https://www.pierredm.xyz/posts/intmax)
52+
- [GitHub – Sonobe](https://github.com/privacy-scaling-explorations/sonobe)
53+
54+
## Get Involved
55+
56+
Plasma Fold is part of the Privacy & Scaling Explorations initiative. If you’re interested in collaborating, contributing research, or running your own Plasma Fold client, we’d love to hear from you.
57+
58+
On X: [@xyz_pierre](https://twitter.com/xyz_pierre)
59+
60+
Email: Pierre Daix-Moreux [pierre@pse.dev](mailto:pierre@pse.dev), Chengru Zhang [winderica@pse.dev](mailto:winderica@pse.dev)
61+
62+
Join the conversation on [PSE Discord](https://discord.com/invite/sF5CT5rzrR)
3463
`,
3564
},
3665
},
@@ -45,6 +74,5 @@ Our goal is to design and benchmark a client-friendly zk/plasma scaling solution
4574
],
4675
themes: ["scalability", "L2 solutions", "zk proofs"],
4776
types: ["research", "development"],
48-
builtWith: ["plasma", "zk proofs", "folding schemes"],
4977
},
5078
}

0 commit comments

Comments
 (0)