Proof of Reserves

Per-coin user liability snapshots with a Merkle root, published for transparency.

Important boundary

CoinDock.online v1 publishes user-liability snapshots only. We do not claim a full proof-of-reserves attestation, on-chain reserve verification, or third-party audit completion. Wallet adapters in v1 are simulated or testnet (see /risk and /compliance).

Latest liability snapshots

Coin Taken at (UTC) User entries Total user liability Merkle root (sha256)
BTC 2026-09-09T01:01:35+00:00 0 0.000000000000000000 0000000000000000000000000000000000000000000000000000000000000000
ETH 2026-09-09T01:01:35+00:00 0 0.000000000000000000 0000000000000000000000000000000000000000000000000000000000000000
MLRT 2026-09-09T01:01:35+00:00 0 0.000000000000000000 0000000000000000000000000000000000000000000000000000000000000000
USDT 2026-09-09T01:01:35+00:00 0 0.000000000000000000 0000000000000000000000000000000000000000000000000000000000000000
USDT-TRC20 2026-09-09T01:01:35+00:00 0 0.000000000000000000 0000000000000000000000000000000000000000000000000000000000000000

How it works

  1. The scheduler runs SnapshotLiabilitiesJob periodically. It iterates every coin, sums each user's available, locked, pending_deposit, and pending_withdrawal balances.
  2. Each per-user row is canonicalised and hashed with SHA-256. A binary Merkle tree is built over the leaves; the root is stored on the snapshot.
  3. Users may request a Merkle inclusion proof for their own row via GET /api/v1/account/balances with the ?include=por_proof flag (gated by the user's own session — never returns other users' data).
  4. No on-chain attestation is currently performed. Snapshots are append-only and retained per the audit policy.