Lurk Lab retweeted
The revised Lurk paper has been published in the Journal of Functional Programming: jfp.episciences.org/en/artic…
We have done so much since then… looking forward to making it public soon.
Lurk Lab retweeted
Here's a snapshot of what we're working on at @LurkLab. This also serves as a snapshot of the kind things coding agents can plausibly accomplish these days.
Lurk Lab retweeted
we are quietly shipping, anon
sneak peek at LurkOS, our provable operating system sending 100k transactions between actors
yes, this is all intra-actor and without proofs, but this is just the start.
LurkScript now works well enough to implement the Lurk standard library so far! Our modular design allows the lurk CLI REPL and prover to use the LurkScript CLI frontend to seamlessly add LurkScript support to Lurk.
github.com/lurk-lab/lurk/pul…
Lurk Lab retweeted
Replying to @NicolasRamsrud @0xLita
Wow, I haven't kept up with Lurk. That's amazing. Okay @LurkLab is going on my study list 🤝
Lurk Lab retweeted
Lurk does something similar with similar results.
All data and code is commitment based, including proof I/O (which is then opened and committed to at each step of computation), so with content-addressed data storage you can generate proofs of computation over arbitrarily sized datasets stored in arbitrary locations. Even private data.
Although we use Poseidon to get const sized commitments, this makes me wonder if there is some PCS method to use as a commitment scheme for proofs over large datasets that would perform better than Poseidon.
The Accidental Computer with @angeris on prover acceleration via DA encodings
In short, proofs-of-encoding (such as ZODA) perform much of the work of a code-based PCS, making it cheap to “embed” verifiable computations over data posted to a DA layer
Lurk Lab retweeted
A little view behind the curtain, anon.
You can now write provable JavaScript with Lurk.
This shows why Lurk is so powerful. It took just 5 weeks to make it possible to compile JS into a JS representation of Lurk that can either be interpreted in place as JS or passed through Lurk for proving.
Onwards to on-boarding millions of devs to ZK.
Provable JavaScript? Check.
Users can now write programs in JavaScript, compile to LurkScript, evaluate in place or pass through Lurk to generate a proof.
Getting ready for that Web2 scale ZK.









