Transparency
Proof of Reserves
Every Monday we snapshot total customer liabilities and the reserves we control for BTC, ETH and TRX. The user-balance side is committed to a Merkle root — any account holder can verify their balance is included in the published root.
How it works
Cryptographic verification, no trust required
- 1. Snapshot. Every Monday at 00:05 UTC we freeze every customer's BTC, ETH and TRX balance.
- 2. Commit. Each balance is hashed with a per-user random nonce; hashes are combined into a Merkle tree. Only the root is published — your UID and balance never leave the system.
- 3. Reserves. We total the platform hot and cold wallets plus every registered external reserve wallet. Coverage = reserves ÷ liabilities.
- 4. Verify. Sign in and open Verify my balance — your browser recomputes the hash chain and confirms inclusion in the published root.
Coverage is informational only. Liabilities are denominated in each native asset; we don't net across assets. The published root is computed on-server today; on-chain anchoring (publishing the root to an Ethereum transaction) is on our roadmap.
Reserves
Registered reserve wallets
Every wallet and custodial account counted toward reserves. Addresses are shown as a SHA-256 commitment so we don't expose raw treasury addresses publicly — the hash is stable per wallet and changes only when the underlying address changes.
| Asset▲ | Label | Kind | Address hash | Balance | Updated |
|---|
History
Past snapshots
| Published | Asset | Liabilities | Reserves | Coverage | Root |
|---|