Skip to content
Blockworks

The Future of Security is Zero Knowledge | PMLS 2025 | Day 2 | Blockchain Design

Marc-Thomas Arjoon, Uma Roy, Dan Elitzer, Dr. Benjamin Beckmann

0:000:00

Key takeaways

  • Tooling Tipping Point: Succinct’s SP1 ZK-VM and Midnight’s Compact language move ZK from cryptography PhD territory to ordinary developer workflows, opening the flood-gates for new applications over the next 12-18 months.
  • Verifiable Exchanges Go Live: A new crop of ZK-verified central limit-order books—projects like Hibachi—aims to match Hyperliquid’s product-market fit while adding provable matching, private positions and unfront-runnable liquidation logic.
  • Web-2 Data On-Chain: ZK-TLS, ZK-email and similar “web proofs” will let builders target billions of mainstream internet users for airdrops, credit, identity and rewards, expanding the addressable market far beyond today’s on-chain power users.
  • AI as Force Multiplier: Large Language Models already write circuits, fill security checklists and identify 70-80 percent of smart-contract bugs for top audit firms, compressing development time but raising new supply-chain risk.
  • Privacy Renaissance: Speakers agree the next wave of differentiation is user-centric privacy, not just roll-up scaling. Selective disclosure, viewing keys and shielded resources are becoming baseline expectations for consumer-facing products.
  • Compliance by Construction: Privacy and regulation are not mutually exclusive; application-level viewing keys allow auditors to see what is required without hard-coding back-doors into the protocol layer.
  • Product > Proofs: Venture capital appetite hinges on clear go-to-market plans. A mathematically elegant circuit is irrelevant if teams cannot capture user attention in a stagnant onboarding environment.

On Zero-Knowledge Security Fundamentals

Marc-Thomas Arjoon steers the panel into definitions. Uma Roy separates three layers of assurance: cryptographic soundness, bug-free implementation and pragmatic redundancy, such as multiple provers or TEEs. Dan Elitzer adds that off-chain compute plus on-chain proofs lets contracts run richer safety checks than Ethereum’s gas budget allows. Dr. Benjamin Beckmann frames ZK as minimum-information disclosure for end users: say “I am over 18” without revealing any other data. All agree formal verification is progressing but specialist auditor capacity is scarce, so layered mitigation remains essential.

On Tooling and Developer Experience

A year ago, building anything beyond a simple circuit required “multiple cryptography PhDs.” SP1 now compiles ordinary Rust or C into provable circuits, while Midnight’s Compact offers TypeScript-like ergonomics. Both projects ship with automated determinism tests so developers cannot silently introduce nondeterministic traps. Cheaper, faster proofs via a decentralized prover marketplace are next on Succinct’s roadmap, promising near real-time Ethereum state verification.

On Emerging Application Frontiers

Exchanges lead commercial traction. Hyperliquid’s rapid user growth proves demand; ZK-verified competitors intend to add privacy and market-integrity guarantees. Private liquidation thresholds and hidden order sizes aim to prevent position hunting incidents that recently rattled traders. Outside crypto-native finance, ZK-TLS and ZK-email unlock provable internet histories—think Spotify-powered credit scores or YouTube-based influencer payouts—without exposing raw personal data. Google’s age-verification wallet demo underscores that meaningful ZK adoption may originate off-chain first.

On AI as Development Co-Pilot and Security Accelerator

A self-described Hyperliquid “whale” with no coding background vibe-coded an SP1 application over a weekend using an LLM, then passed an audit. Security firms for major Layer-1s now automate up to 80 percent of vulnerability discovery with similar tools. Midnight trains AI agents to scaffold Compact projects inside IDEs and to manage private state interactions on behalf of users, envisioning intent-based trading where bots hold asymmetric information without leaking it on-chain. The flip side: model-generated circuits add another dependency layer that must itself be verified.

On Privacy, Compliance and Regulatory Design

Dr. Benjamin Beckmann stresses that compliance hooks belong at the application layer. Midnight issues per-user viewing keys so accountants or regulators can audit specific flows while the base protocol remains sealed. This mirrors how stablecoins or neo-banks will need to reconcile KYC mandates with consumer expectations. The panel rejects protocol-level back doors; selective key sharing gives users agency and preserves legal clarity about who disclosed what.

On Commercialization Challenges and Hype Calibration

Investors shut pitch decks when founders equate “ZK” with automatic distribution. Products must still beat incumbents on UX, cost and narrative. Scaling use cases are now commonplace; privacy-enhancing ones are under-explored. Overhyped: generic “on-chain neo-banks” that ignore wallet-level data leakage. Underhyped: practical privacy primitives and mainstream web-proof integrations.

Key actionable insights

  • Monitor SP1’s decentralized prover network launch and initial proof price trends as a bellwether for ZK compute commoditization.
  • Track early ZK-TLS deployments that tie web-2 credentials to on-chain identity, a likely catalyst for the next major user-acquisition wave.
  • Follow verifiable exchange roll-outs to gauge whether privacy and auditability translate into liquidity migration from existing venues.