Proof of reserves for exchanges and custodians: Trust,
done simply.

Q: How do we get started?

Email hello@peaknode.ar with your company, your role, and the chains you custody on. We will set up your organization and walk your team through the first proof.

Continuous cryptographic proof that every customer balance is backed on-chain. Checkable by anyone.

Watching Ethereum · block –

Request access How verification works

Sample exchange Sample proof

1.009×

Solvent

Reserves: USD 200.5M
Customer balances: USD 198.7M
As of: –

Illustrative figures

A million balances. One answer.

What the answer is made of

Three proofs, one verdict.

Each proof of reserves joins signed wallet ownership, a commitment to every customer balance, and on-chain holdings priced at one moment. The verdict is solvent, insolvent or incomplete, decided by exact comparisons, never by a rounded ratio.

How a proof is checked

Many sources, one price: The median of independent sources. Stale quotes and outliers are set aside, each with its reason kept.
Never $0: An asset without a reliable price blocks the verdict instead of counting as zero
Per asset or pooled: Choose whether each asset must be covered on its own
Rounded down: Holdings are kept to 8 decimals and never overstated

You stop asking for trust. You show it.

Are you solvent?
Our latest proof:
verify.peaknode.ar/…

The proof page

A link anyone can open. No one can alter.

Publishing gives the proof a permanent page at verify.peaknode.ar. Anyone sees the verdict, every asset, wallet coverage and where each price came from, without an account.

Check a proof offline

Ed25519: Every published bundle is signed. Keys are listed publicly, retired ones included
128-bit link: Each proof gets an unguessable code and never changes once published
evidence.zip: The signed files, checkable offline with openssl and jq
One script tag: Embed a live solvency badge on your own site

Your customers check for themselves.

Included
2.41 ETH
root 0x7f3a…c91e
Sample

Inclusion proofs

Each customer sees their balance counted. Nobody sees anyone else's.

Balances are committed to a Merkle sum tree for each asset. A customer's zero-knowledge proof shows their own balance is in the tree and range-checks every neighbouring sum, without showing those sums.

Verify an inclusion proof

PLONK · BN254: Built with gnark, checked against a pinned verifying key
No setup of our own: Public Aztec Ignition parameters from 176 participants
1,048,576: Balances per asset in each tree
Offline too: Check with the Go SDK, without relying on our servers

You know, every time it runs.

1.00×
Sample

Continuous evidence

Proof as often as you like, not once a quarter.

Set a schedule in your own timezone and every run ends in a signed verdict. Each one is anchored to a block anyone can look up.

Check block anchors

5 min: Shortest interval between scheduled runs
Block-anchored: Every scan records block number, hash and time
60 s: Prices refresh every minute by default
Finalized · 6: Ethereum is read at its finalized block, Bitcoin at 6 confirmations

And you get your quarters back.

Getting started

Connect once. Then it runs.

Prove your wallets with a signature, upload customer balances as a file and choose a schedule. Peaknode never holds keys and never moves funds.

Read the API quickstart

Bitcoin · Ethereum: Live today, with USDT, USDC, DAI, WBTC, WETH and LINK
5 signature schemes: BIP-322, BIP-340, Bitcoin signed messages, SIWE (EIP-191) and Ed25519, plus Gnosis Safe multisig
CSV · NDJSON · Parquet: Liability uploads are atomic and idempotent
PDF · CSV: Reports to share with your team or auditors

Start with your first proof.

Tell us your company and the chains you custody on. How each proof is built and checked is in the docs.

Request access Read the docs

Questions

How is this different from an audit firm?

An audit firm samples records and signs an opinion at a point in time, often once or twice a year. Peaknode produces cryptographic proofs anyone can check: signatures show control of each wallet, a Merkle commitment fixes customer liabilities, and balances are read directly from the chain. Peaknode does not issue an audit or assurance opinion, and it can sit alongside one.

What can our customers verify themselves?

Each customer can check that their balance is included in the committed liabilities. They verify a zero-knowledge proof against the published commitment, using their identifier and a private code you give them.

What does an inclusion proof reveal?

A customer’s proof shows their own balance for one asset, along with that asset’s committed root and total. Neighbouring hashes and subtotals stay inside the zero-knowledge proof, and no other customer’s identifier appears in it. Each asset’s total is part of the published commitment.

Which chains are supported today?

Bitcoin and Ethereum are live. New chains and tokens are added through configuration, without a new release.

Does Peaknode ever hold our keys or funds?

No. Wallets prove ownership by signing a challenge with their own keys. Peaknode never receives private keys and never moves funds; it only reads balances from the chain.

How do we get started?

Email [email protected] with your company, your role, and the chains you custody on. We will set up your organization and walk your team through the first proof.

Proof of reserves for exchanges and custodians: Trust,done simply.