Proof of reservesProof of liabilities · availableProof of reserves · in pilot

Keep your ledger. Add proof of reserves.

We prove that your reserves are at least what you owe customers — without revealing anyone's balance. Auditors and regulators verify the result themselves, without receiving the ledger.

Across all productsWe prove the facts without exposing the data

Proof of reserves resultExample

Snapshot time
2026-10-23 09:00 KST
Reserves ≥ customer deposits
Met
Individual balances
Not disclosed
Proof ID
PR-20261023-0900
Audit pack
Audit response pack

The proof is based on the balance data provided. Actual holdings are confirmed alongside it with wallet-ownership signatures and bank or custodian balance confirmations.

Track record

  • Bank of Korea CBDC pilot (2022)
  • Samsung SDS Stablecoin platform backend (2025)
  • Gyeonggi Province Stablecoin adoption study (2026)
Company & technology →

Why crypto and prepaid operators need it

Crypto exchanges

When you must explain 5-minute balance reconciliation and monthly audit results to outsiders

Crypto custodians

When you must show customers and auditors that assets held match the books

Prepaid operators

When you must show users and regulators that 100% of stored value is segregated

How it differs from a monthly audit

A monthly audit checks once a month, leaving the time in between unverified. Regular proofs leave a proof file at whatever interval you choose — even every 5 minutes.

Monthly auditHard to verify between auditsRegular proofEvery proof leaves a proof file and audit pack01 month2 months3 months
CriteriaMonthly auditInternal reconciliation · 5 minRegular proof (ZKRYPTO)
FrequencyMonthlyWithin 5 minutesYou decide
Who checksAccounting firmInternal teamAuditors, regulators, users
External re-checkReport onlyDifficultYesAudit response pack
Ledger shared externallyGiven to auditorsNoNo
Actual reserves confirmedYesBank balance confirmationWallet balances onlyWallet-ownership signaturesBank deposits via confirmation letters

Regular proofs don't replace monthly audits or internal reconciliation. They add an externally verifiable proof on top of both.

How it works

  1. 01

    Set a snapshot time

    Collect balances at that moment

    Customer and reserve balances at the snapshot time are collected inside your systems. Raw data never leaves.

  2. 02

    Generate the proof

    Computed without revealing balances (zero-knowledge)

    Proves every customer balance is in the total and that reserves cover it — without revealing any individual balance.

  3. 03

    Anyone can re-check

    Auditors and users verify

    Auditors re-check the result with the audit pack you submit. Users can confirm on a check page that their balance was included.

    User check page · coming soon

Inside your systems (raw data never leaves)Customer ledger & raw balancesSnapshot totalsBalance total and reservesGenerate proof(zero-knowledge)Proof file & totalsNo individual balancesAuditors & regulatorsRe-check with audit packUsersCheck own balance is included
  1. Customer ledger & raw balancesInside your systems
  2. Snapshot totalsBalance total and reserves
  3. Proof generationZero-knowledge proof
  4. Proof file & totalsNo individual balances
  5. Auditors, regulators, usersRe-verify
The customer ledger never leaves your organization — only the proof file and totals are shared.
On-chain record · per-account commitments (Cm) and totalCm1Cm2Cm3Cm4Cm5Cm6Cm7Cm8A Cm alone reveals no balanceCm1 + … + Cm8 = TotalMatched by zero-knowledge proof (PoL)Compare valuesUserComputes Cm from own balance + check valueAuditors & regulatorsVerify the match with the proof file

What you receive with every proof

Along with each result, you get an audit pack that lets auditors and regulators re-verify without receiving the ledger.

  1. Run proofAt each snapshot time
  2. Audit pack6 items · per proof, compiled monthly
  3. Auditors & regulatorsRe-verify without the ledger
  • File list with tamper-check hashes
  • Proof result summary
  • Snapshot time and totals
  • A publicly verifiable proof file and verification key
  • Exceptions found and actions taken
  • A 1–2 page report for management and disclosure

With the shared ledger (ZKRYPTON), proof results are recorded together with other participants, so no single organization can alter them. (Optional · in pilot)

Deployment options

Dedicated install

Installed on your servers or a dedicated environment. Raw data never leaves.

Monthly subscription (hosted by ZKRYPTO)

Timing TBD

Regular proofs run in an environment operated by ZKRYPTO.

Getting started

Timeline
4–8 weeks for full rollout (with balance data in our standard format)
What we need from you
Snapshot balance data via CSV file or API
Pricing
Pilot (8 weeks) → pilot fee credited against the first year when you signCredit terms and amounts are provided during consultation once we understand your data volume and proof frequency.

Frequently asked questions

Can it meet the 5-minute reconciliation requirement?

Yes. You set the interval, and 5 minutes is possible. If you already reconcile internally, we add proofs on top of those results.

Do we have to change our ledger or systems?

No. All we need is a connection that exports balance data at the snapshot time.

Has the technology been externally audited?

An external security audit of the proof code (ZK circuits) is being prepared. Once complete, we'll publish the auditor and report.

Does it prove the reserves actually exist?

The proof checks that the balance data provided is consistent. Actual holdings are confirmed with wallet-ownership signatures for crypto and bank or custodian confirmations for deposits.

Does it replace an accounting firm's audit?

No. It supports audits and disclosures, and can be provided together with an accounting partner.

Can it be combined with other products?

Yes. The security token, stablecoin, policy fund and fractional products share the same reconciliation proof, so the data and proof history you connect now carry over. The fractional product is coming soon.

Start with a pilot

We agree on success criteria before the pilot, and set full pricing together based on the results.

Add a trust layer to your existing services.

Stablecoins & digital assets, public trust infrastructure, research collaboration — live demos available at demo.zkrypto.com.