Prove every customer balance is backed, on any day your auditor picks.
The kit runs on your servers, read-only against your ledger and the blockchains. Every day it commits all customer balances to a Merkle tree, reads your wallets at a recorded block, checks signed ownership messages and writes a signed snapshot with an auditor pack. Customers check their own balance on a page in your brand. Your keys never leave your custody.
- signed snapshot, kept 400 days
- Daily
- chain families read: EVM, TRON, Bitcoin, Solana, XRP
- 5
- auditor pack languages
- EN + TR
- keys held by the kit
- 0
Six parts, one snapshot.
Merkle sum tree of every balance
Reads customer balances from a CSV export or a read-only SQL query and commits them to a Merkle sum tree. Only the root and the per-asset totals are published.
A check page in your brand
Each customer gets an inclusion proof in the account area and checks it in the browser: signature, path to the root, root against the published snapshot.
Wallet balances at a recorded block
Reads every wallet you declare, native coins and tokens, and records the block height and hash of each reading. Unreadable wallets are listed, never counted.
Signed messages from your wallets
Officers sign one challenge per audit period with the auditor's nonce. The kit verifies EVM, TRON and Bitcoin signatures; multisig and custodian wallets take manual evidence.
One signed document
Liabilities root, reserves, ownership, bank balances and coverage per asset in canonical JSON, signed with your Ed25519 key. Change one number and the signature fails.
Report and annexes
HTML report in English and Turkish with CSV annexes: assets and networks, custody model, addresses and balances, ownership, liabilities, cash, exceptions.
What the kit reads today.
| Chain family | Assets | How the reading is pinned |
|---|---|---|
| EVM (Ethereum, BSC, Polygon, Avalanche C) | Native coin, ERC-20 tokens | One block number for every read, hash checked again after reading |
| TRON | TRX, TRC-20 tokens | Head block recorded at the start of the read |
| Bitcoin | BTC (Esplora) | Tip checked before and after; read again if a block arrived |
| Solana | SOL, SPL tokens | Slot and blockhash recorded per reading |
| XRP Ledger | XRP | One validated ledger for every read |
| Other holdings | Custodian or exchange accounts, bank balances | Entered with the statement reference and date |
| Bitcoin HD wallets | BTC from an xpub, ypub or zpub | Every used receive and change address found by a gap-limit scan |
| Fireblocks | Any asset in one vault or the whole workspace | Read with your read-only API key |
| Binance | Spot and funding accounts | Read with your read-only API key |
Snapshots are taken daily and archived, so a past date is served from the archive rather than by reading old blocks.
Built for the reserve audit in Türkiye.
Platforms in Türkiye have their reserves audited every quarter by an independent information-systems audit firm. The kit keeps the evidence ready for any date the auditor picks.
- Any date in the quarter
- A snapshot every day at 00:05 UTC, kept for 400 days. On the day the auditor names, take a fresh one in one command.
- Pack order
- Assets and networks, custody model, wallet addresses and balances, ownership, customer liabilities, cash balances, exceptions.
- Checks the auditor can repeat
- Signature of the snapshot, any customer's proof, every wallet reading with its block, every ownership signature.
- Two kinds of reserves
- All readable reserves, and reserves whose ownership signature verified. Both are shown per asset.
- Exceptions in plain words
- Negative balances, unreadable wallets, unverified ownership and assets below liabilities are listed, not hidden.
Clear lines.
We are not your auditor
The pack is evidence. The audit opinion comes from the independent audit firm.
No keys, no transactions
The kit reads public chain data and verifies signatures. It never holds a key or moves funds.
Balances stay on your servers
Only the root, the totals and the signed snapshot are published. Proofs are served by you, inside the customer's account.
On BitPolaris or on any other exchange software.
| One-time | Monthly | |
|---|---|---|
| Add-on for BitPolaris customers | €1,700 | €85 |
| Standalone, we host it | €6,300 setup | €490 |
| Standalone, on your servers | €9,800 licence | 20% of the licence per year for updates |
| Audit-day support | — | €980 per quarter |
Pilot: we are onboarding the first platforms now, in time for the first quarter of 2027. Pilot customers help set the order of the next features.
Questions
Does it work with our exchange software?
Yes. Balances come from a CSV export, a read-only SQL query or an internal HTTP endpoint that returns user, asset and balance. For Peatio and OpenDAX ledgers the whole configuration is generated from the exchange's own tables.
Can a customer see other customers' balances?
No names or IDs are ever shown. A proof includes the totals of the neighbouring branches; at the lowest level that is one other customer's balance with nothing attached to identify them. Positions are shuffled every day.
What about multisig and cold wallets?
Single-key EVM, TRON and Bitcoin wallets sign a message. Multisig, smart-contract and custodian wallets are recorded with manual evidence, such as a test transfer, and shown as not verified until the auditor confirms.
What does pilot mean here?
The kit works end to end today. Pilot means we install it with each of the first customers ourselves and adjust the pack to their auditor's requests.
Do you need access to our keys or funds?
No. The kit needs read access to the ledger (or an export), public chain endpoints and the signed messages your officers produce.
We keep funds at Fireblocks or on another exchange. Does it still work?
Yes for Fireblocks and Binance: the kit reads the balances with your read-only API keys. Other custodians and venues go in as statements with a reference and date, and more connectors are coming.
Audit coming up?
Tell us your ledger, your chains and your audit date. We reply with an installation plan.