The proof is public. The witness is not.

Focus areas

Where we build.

Not a locked product roadmap—three directions our team works across so partners can see how we think.

• 01

  zk-TLS

  Most valuable data still lives behind ordinary HTTPS—banks, exchanges, providers, and web apps. zk-TLS lets a user prove a fact from a real TLS session without handing over the full response, cookies, or credentials.

  That means a smart contract or counterparty can verify statements like a balance threshold, an account status, or a signed API result, while the underlying session stays private. We treat it as the bridge between the web and on-chain verification.

• 02

  ZK credentials & KYC

  Protocols often need assurance—“over 18,” “KYC-passed,” “not on a restricted list”—without becoming custodians of passports, selfies, or provider databases. Zero-knowledge credentials make that possible through selective disclosure.

  A user proves only the attribute required for access or settlement. The verifier gets a cryptographic yes, not a document vault. We design for EVM integration: clear trust assumptions, portable proofs, and interfaces protocols can call.

• 03

  ZK shielding

  Public ledgers expose amounts, counterparties, and transfer graphs by default. ZK shielding keeps balances and transfers private inside a commitment-based system, while withdrawals and settlements still land on EVM when needed.

  Our focus is usable private settlement—not anonymity as a slogan. That includes fee and relayer paths, sound nullifier design, and optional compliance disclosure when a use case requires viewing keys or selective proofs of legitimacy.