By: Geeq  on Aug 25, 2025

💡 X Space Summary for July 31 2025

Host: Geeq

 Guest: Nicolas RAMSRUD, Co-Founder CEO @Lurklab Privacy is Freedom 

Introduction:

The conversation is a deep dive into zero-knowledge proofs (ZKPs) and their role in improving blockchain scalability, privacy, and user experience. It focuses  on how ZK virtual machines (ZKVMs) work, how they can prove computations without revealing inputs or internal processes, and how this could lead to more private, scalable, and user-friendly blockchain applications.

Core Concepts Explained:

What is a Zero-Knowledge Proof (ZKP)

A ZKP lets one party (the prover) convince another party (the verifier) that a statement is true without revealing any information about why it’s true.

ZK in Blockchains

In blockchain, ZKPs can be used to:

1. Prove that a transaction or computation happened correctly.

2. Do this without revealing private data.

Compress large computations into a tiny proof that’s fast to verify.

ZKVMs and Compilation

What’s a ZKVM?

A ZK virtual machine is like a regular computer that runs programs, but everything it does is encoded as arithmetic circuits or polynomials. You can then generate a proof that the machine ran a program correctly, without showing the inputs or intermediate steps.

Think of it as compiling regular code into a “polynomial form” for a special ZK computer.This is what lets you prove computations privately.

Trusted vs Trustless Setup

Some systems like Groth16 need a trusted setup (a one-time secret generation ceremony). Others like STARKs don’t need a trusted setup, but their proofs are much bigger and need compression.

Architecture and Verifier Keys

Each program has its own verifier key tied to the specific arithmetic circuit. This makes deploying many new programs complex, as validators would need to update for every new circuit.

Their solution? One universal “operating system” (like Lurk OS) that can run any program written in a specific language. So you only update the OS occasionally, not for every app.

How Proofs and State Work

Each user does private computation locally (like changing red to blue). They generate a proof of that computation, which they submit to the blockchain. This proof is verified and updates the global state without revealing the underlying data. The blockchain acts like a “spike of receipts” — each proof is stacked, and collectively, they define the valid state.

Implications for Smart Contracts

Deploying a smart contract changes the program logic.

If you want to ZK-prove something about a new smart contract, you’d need to generate a new arithmetic circuit — unless you’re using a ZKVM. With a ZKVM, you just write the smart contract in a supported language and the system already knows how to prove it, because all the instruction types are predefined.

Why This Matters for Users

The promise of ZK tech:

1. Better UX: No more 15 MetaMask popups — everything abstracted.

2. Better privacy: Nobody sees your data, just the proof.

3. Better integration: Existing systems (like ERPs or banks) can plug into blockchain logic without having to redesign from scratch.

Enterprise Adoption

There’s strong enterprise interest, especially in using ZKPs to automate financial workflows and reduce settlement costs (like with stablecoins replacing traditional payments).

Final Takeaway

ZKPs and ZKVMs are enabling a shift where users interact with blockchains in a more private, trustless, and seamless way. Instead of verifying every detail, users and validators can just verify that a valid proof exists.