INTERSECTION / ZK × zkSYNC

ZK × zkSync.

Paid cryptography work supporting zkSync's ZK rollup infrastructure. Scope bounded by NDA.

§1 — What we ship on zkSync.

What we ship on zkSync.

Paid cryptography engagement under NDA, supporting zkSync's ZK rollup infrastructure. Specifics of scope, deliverables, and timeline are NDA-bounded. The engagement is listed here because the practice does grant-funded public work (Wormhole light clients), open-source contribution (Penumbra), contracted protocol engineering (MultiGov's Solana implementation), and NDA-bounded paid work for a major rollup team. Different engagement shapes, same cryptography bench.

We don't publish project specifics on engagements under NDA. The intersection page exists because zkSync is in the chain coverage list, and an honest site has to acknowledge the work without exposing it.

§2 — What ZK × zkSync engagements look like.

What ZK × zkSync engagements look like.

Engagements shaped like the zkSync one are rollup-cryptography work: prover-side optimizations, in-circuit / out-of-circuit decisions for performance, verifier-side engineering, and the supporting cryptography for the rollup's broader roadmap. Engagement runs as outstaff under enterprise terms — similar to M0 in structure though different in domain.

— ENGAGEMENT

If your rollup cryptography has to stay under NDA, talk to a founder.

If you're building rollup infrastructure or production ZK cryptography that has to run under enterprise terms, the engagement starts with a 30-minute call.

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