INTERSECTION / ZK × ETHEREUM

ZK × Ethereum.

Light-client receiving side for cross-chain ZK transfers, MultiGov contribution, identity cryptography, and privacy-protocol partner engineering.

§1 — What we ship on Ethereum.

What we ship on Ethereum.

The cryptography practice's Ethereum surface covers four kinds of work. Cross-chain ZK — the Ethereum side of the Wormhole NEAR↔Ethereum light client (Foundation grant), plus MultiGov engineering — Zpoken built the governance system's Solana implementation. Identity cryptography — engineering work with Privado / PolygonID on ZK-based credential proofs. Privacy protocol engineering — Panther (Base deployment) and Hinkal (cryptography review and support on core contracts). Cross-chain primitives for Zpoken's internal protocol Evidentia, which uses Ethereum as one of its three deployment chains with LayerZero omnichain messaging.

§2 — Representative work.

Representative work.

01 / WORMHOLE MULTIGOV

Governance infrastructure contribution.

MultiGov is Wormhole's multichain governance system — proposals, voting, and execution coordinated hub-and-spoke across the chains Wormhole spans; the EVM contracts carry its Ethereum surface. Zpoken built MultiGov's Solana implementation — the spoke-voting, staking, and vesting programs — and engineered on the EVM side alongside ScopeLift, as contract engineering for the Wormhole Foundation.

→ /ecosystem/wormhole
02 / PRIVADO · POLYGONID

ZK identity credential proofs.

Identity protocol with ZK-based credential proofs. Engagement scope covers circuit work and the Ethereum-side integration where credentials are verified on-chain. Builds on the same in-circuit / out-of-circuit decision framework as our other ZK work.

→ /work
03 / PANTHER · HINKAL

Privacy protocol partner engineering.

Two privacy protocols, each composing a different set of privacy primitives (commitments, range proofs, set-membership proofs, encryption) on Ethereum. Panther — Base deployment; Hinkal — cryptography review and support on core contracts.

→ /work

§3 — What ZK on Ethereum actually requires.

What ZK on Ethereum actually requires.

Ethereum is where most ZK demos work and most production ZK shipments hit constraints. The chain's gas profile, finality semantics, and developer ecosystem set the cost budget for every cryptographic design choice.

01.

On-chain verification cost is the gating constraint.

Ethereum's gas profile makes verifier cost the primary design constraint for most ZK use cases. A Groth16 verifier costs ~250K gas; a PLONK verifier 2–5× that depending on circuit; a STARK verifier substantially more. The proof system that's right in a paper isn't necessarily the proof system that's economic in production on Ethereum. Choosing the right one is downstream of the use case's economic budget for verification.

02.

Composition under MEV.

Privacy protocols on Ethereum face MEV-style attacks that don't exist on chains with different mempool semantics. A privacy primitive that holds up in isolation can leak when adversarial mempool observation is in scope. Composition analysis on Ethereum has to include MEV-related leakage paths, not just protocol-internal composition.

03.

Identity primitives at scale.

Identity protocols (Privado is the example we know best) face a scale problem on Ethereum that isn't in the cryptography literature: the on-chain cost of credential verification has to be low enough that the protocol scales to non-trivial usage. The engineering call is which proofs verify on-chain vs. which carry off-chain witnesses with on-chain commitments.

— CAPABILITYApplied cryptography & ZK→
— ECOSYSTEMWormhole→
— INTERSECTIONZK × NEAR→
— ENGAGEMENT

If your protocol needs ZK on Ethereum, talk to a founder.

If you're building Ethereum-anchored ZK or privacy infrastructure that has to hold up under adversarial review, the engagement starts with a 30-minute call.

That call is with a founder. Shapes, discovery, and terms → /engagement

Book a call→ Open the form