Lambda VM is an open-source zkVM for RISC-V being built in collaboration with @class_lambda and @3miLabs.
to learn more about it, read the article on its principles: https://t.co/QA7AHEoa2w
every rollup needs a way to prove its transactions executed correctly.
without a zk engine, you're asking people to trust an operator instead.
Lambda VM takes a program, runs it, and produces a mathematical proof that Ethereum can verify.
with it, security stops being an assumption and becomes a guarantee.
interoperability protocol is a part of the stack that lets enterprises and governments launch products on @ethereum
to learn more, read https://t.co/p25lIji9w5
i've seen things you people wouldn't believe...
a wallet, a rollup, a bridge, a prover: several vendors, one app that still doesn't ship.
months of integration for a product that launches to nobody.
wallets guarded by seed phrases nobody can remember.
all those integrations, lost in time, like the multiple vendors you no longer need.
Epochs are what we run today. Prove-and-retire is still an experiment, and it's doing a lot better than we expected.
Both designs are in the post below. Lambda VM is built with @class_lambda and @3miLabs.
Post: https://t.co/4pgVwsXnkY
The problem every zkVM has to solve: big programs don't fit!
To prove an execution, a STARK prover needs the whole thing in memory at once. For an Ethereum block that's an unreasonable amount of RAM.
Every zkVM team hit this wall, and each one got over it differently.
Here are the two ways we tried in Lambda VM 🧵
Epochs work, but each one drags along its own fixed tables and FRI, so proof size and verification time grow with the epoch count.
Prove-and-retire pays in compute instead.
Re-running a program is cheap next to proving it; holding everything at once was the real problem.