TechnologyZero-knowledge proofs

    Zero-knowledge proofs: prove the fact, keep the data

    Short answer

    A zero-knowledge proof lets a user or a system prove that a statement is true (a score is above a threshold, a person holds a valid credential, a batch of transfers is correct) without revealing the data behind it. We design the circuits, the proving flow on the client or a relayer, and the smart contracts that verify the proofs, and we built and maintained the zkSync SDKs in five languages.

    At a glance
    Proof systemsGroth16 · Halo2 · recursive proofs
    VerificationEthereum smart contracts
    Layer 2zkSync SDKs: Go, Python, Rust, Android, iOS
    Used forSybil resistance · private auth · scaling

    How a project runs

    Zero-knowledge proofs: from question to running system

    Your pathEach step ends in a written result
    1. 01Statementwhat is proved · what stays private
    2. 02Circuit designproof system · trusted setup
    3. 03Proverclient or relayer · proving time
    4. 04Verifiersmart contract · gas per check
    5. 05Integrationpartner API · SDK

    What we build

    Threshold proofsA user proves "my score is at or above the threshold for this level" without revealing the score or any input, verified in a smart contract. Feasibility assessment and a proof-of-concept prototype for an anonymous proof-of-humanity protocol with six trust levels.
    Private authenticationZero-knowledge authentication and data checks for a private messenger with seed-phrase identity, end-to-end encryption and encrypted metadata.
    ZK rollup integrationsThe full set of zkSync SDK libraries for integrators, built and maintained by our team in Go, Python, Rust, Android and iOS, later with EIP-712 signatures and deterministic deployments.
    Off-chain to on-chain flowsCommitments from an off-chain engine (for example an ML risk score), proofs generated on the client or by a relayer, and on-chain verifiers that partner contracts can call.
    Proof system choiceGroth16 where cheap verification on Ethereum matters most, with a planned path to Halo2 and recursive proofs where a trusted setup or proof aggregation is the constraint.
    Privacy without KYCDesigns that replace passports and biometrics with device attestation, behaviour signals and proofs, so a protocol never stores who the user is.

    Stack

    Technologies we use

    Proof systems
    Groth16, Halo2, recursive proofs
    Chains
    Ethereum mainnet as the trust anchor, zkSync, low-cost chains such as TON or Base for everyday status
    Contracts
    Verifier contracts, staking and slashing, soulbound-style status records
    Clients
    Proof generation on mobile clients or through a relayer; SDKs in Go, Python, Rust, Android and iOS
    Around the proofs
    Device attestation (Secure Enclave, DeviceCheck, Play Integrity, Keystore), risk graphs, end-to-end encryption

    Proof

    Delivered work

    All work
    Case · ZK identity · Global

    Proof of humanity with zero-knowledge proofs

    Problem
    Bots drained airdrops and DAO votes; KYC was not an option.
    Built
    A feasibility assessment, then a proof-of-concept prototype.
    Scale
    Six trust levels, L0 to L5
    Zero-knowledge proofsProof of conceptGroth16Halo2
    Working prototype; protocol split into MVP and ZK phases.
    Case · Layer 2 · Global

    zkSync SDKs in five languages

    Problem
    Every integrator needed an SDK in the language it uses.
    Built
    Go, Python, Rust, Android and iOS SDKs, built and maintained.
    zkSyncEthereum layer 2SDKGo
    zkSync docs credit Vareger as the SDK author.
    Case · Messaging · Global

    Private messenger with zero-knowledge sign-in

    Problem
    No one, not even the operator, may see who talks to whom.
    Built
    Discovery: seed-phrase identity, E2E encryption, ZK sign-in.
    Zero-knowledge proofsEnd-to-end encryptionSignal ProtocolMetadata encryption
    Version 1.0 scope, architecture and team plan, ready to build.
    Case · Identity · Global

    Decentralized identity and verifiable credentials

    Problem
    No standard way to issue, resolve and revoke identities.
    Built
    DID create, resolve and revoke, plus credential issuance.
    DIDVerifiable credentialsUniversal ResolverSmart contracts
    Developers issue and verify credentials through our layer.

    FAQ

    Questions buyers ask

    Q01When is a zero-knowledge proof worth it?

    When a third party must trust a fact but must not see the data behind it: a trust level without the score, eligibility without identity, a correct batch without replaying it. If the data can be shown, a signature or a plain on-chain record is simpler and cheaper.

    Q02Groth16 or Halo2?

    Groth16 gives small proofs and cheap verification on Ethereum, but needs a trusted setup per circuit. Halo2 avoids that setup and supports recursion, at the cost of larger proofs. Many projects start on Groth16 and plan the move once circuits settle.

    Q03Can proofs be generated on a phone?

    Yes, for small circuits. For larger ones the proof is generated by a relayer, and the design must make sure the relayer learns nothing it should not.

    Q04Do you work with existing ZK networks?

    Yes. Our team built and maintained the zkSync SDKs in five languages and advised zkSync integrators on their integrations.

    Next step

    Working on zero-knowledge proofs?

    A 30 minute call with Mykhailo. You leave with a clear view of scope, risks and next step.

    Mykhailo Tiutin

    CTO, Vareger

    Mykhailo Tiutin, CTO, Vareger