Mint & redemption approval
Minting and redemption only run after multiple approvals, and every approval is recorded.
We supply issuance control, key management and reconciliation proofs as one package. If reserves are found to be short, the next mint is put on hold. While the bill is still under discussion, you can trial issuance operations and disclosure in a pilot.
Across all productsWe prove the facts without exposing the data
Track record
The four things you'll need to explain to regulators, recorded in one system.
Minting and redemption only run after multiple approvals, and every approval is recorded.
Keys are split into shares (MPC), so a single leaked share can't mint on its own.
Mint hold on shortfall · in pilot
Regularly proves reserves cover circulating supply. If they don't, the next mint is held.
A disclosure summary and audit pack are produced every cycle.
If reserves fall below circulating supply, the next mint is held.
If reserves are short, the next mint is held
Each option an issuer can choose covers a different scope.
| Criteria | Wallet / custody platform | In-house issuance system | External data feed (oracle) | ZKRYPTO |
|---|---|---|---|---|
| Mint & redemption approval | Focused on custody and trading | Depends on design | N/A | Multi-approval and records included |
| Key management | Platform's approach | HSM or MPC purchased separately | N/A | MPC includedzkWallet |
| Reserve-based mint control | Provides reconciliation dataSome integrate with oracles | Built separately | Rejects mints on shortfall | Holds mints on shortfallIn pilot |
| Proof method | Data reconciliation | Built separately | Oracle feedSource data relies on the provider | Zero-knowledge proofCovers supply and holder totals; account data stays private |
| Where it runs | Varies | On-premises | Connected to an external oracle network | On-premises |
Oracles (services that bring external data on-chain) can also gate minting on reserves. ZKRYPTO proves circulating supply and holder totals inside your organization, without sending account data out. Based on public information as of October 2026.
Issuance control and reserve disclosure on top of the core (key management and reconciliation proofs). Keep using the blockchain you already have.
Specific to this product
Disclosure summary page and reports
Included
Token mint, burn and admin console
Included
Split keys, signed per approval policy (MPC, zkWallet)
Included
Proves reserves cover circulating supply (zero-knowledge, zkPoRL)
Add-on · available in pilot
When you need a blockchain run jointly with participants (ZKRYPTON)
Optional add-on
Hides B2B payment amounts and counterparties (zkTransfer)
The reserve check result is passed to the issuance system, and reserves are re-checked just before each mint. If they're short, the mint is held. Available in the pilot.
Trial deposit-token and stablecoin operations on internal systems first
Fintech and IT companies joining bank-led issuance consortia
No. The pilot starts with trial runs of issuance operations and disclosure. Success criteria and full terms are agreed upfront, and adjusted to the final requirements once the rules are set.
Yes. Issuance control, key management and reconciliation proofs connect to whichever chain you use.
Yes. The pilot trials issuance operations and disclosure together. The separate proof-of-reserves product is for exchanges, custodians and prepaid operators that don't issue tokens.
An external security audit of the proof and issuance code is being prepared. Results will be published when complete and added to the evaluation pack.
Run the issuance and disclosure flow internally in a pilot first.