River reserve watch
An independent check of the Bitcoin held at River's published reserve address, with all three parts of the September 2026 Proof of Reserves verified.
Tracked addresses
Reserve addresses published on river.com. Moves between them count as internal, not as outflows.
| Label | Address | Confirmed BTC | Pending BTC | Transactions |
|---|
Independent verification
All three parts of River's September 1, 2026 Proof of Reserves, checked independently (snapshot block 965,052).
| Check | Result | How |
|---|---|---|
| Assets on-chain | Reconciled | Reserve address balance matches attested assets of 33,737.53513283 BTC to the satoshi, after the movements since the snapshot. |
| Liabilities add up | Verified | Rebuilt River's Merkle sum tree: 2,097,151 parent nodes checked, 0 sum and 0 hash mismatches. Total of 33,498.71382005 BTC matches published liabilities. |
| River controls the address | Verified | Proof transaction sent 0.04034917 BTC (plus a 1,078 sat fee), matching the last seven digits of block 965,052's largest coinbase output of 3.14034917 BTC. The block was mined about 10.5 hours before the proof. |
Liabilities verified locally on Sep 30, 2026 with a script built from River's open-source proof-of-reserves code. This confirms the liabilities file is internally consistent and matches the published total. Only individual clients can confirm their own balances are included.
Inside the liabilities tree
What the September 1, 2026 liabilities file looks like. River splits and shuffles balances for privacy, so these are pieces of balances, not accounts.
| Lines in file | 4,194,304 |
| Nodes in the tree | 4,194,303 |
| Leaves (bottom row) | 2,097,152 (221) |
| Zero-value filler leaves | 0 |
| Largest leaf | 0.04999997 BTC |
| Average leaf | 0.01597343 BTC |
| Median leaf | 0.01235709 BTC |
| Smallest leaf | 0.00000001 BTC |
Every leaf is under 0.05 BTC, so a 10 BTC balance appears as at least 200 separate pieces. That hides how large any one balance is, and the number of leaves says nothing about the number of clients. The tree reaches a power of two by splitting balances further rather than adding empty leaves.
Proof of Reserves over time
River's monthly attestations from river.com/reserves. Assets are Bitcoin in cold storage; liabilities are what clients own.
| Attestation | Assets BTC | Liabilities BTC | Surplus BTC | Coverage |
|---|
Net movement at the reserve address since the latest attestation: …
Recent movements
The latest transactions touching any tracked address, with the net change to the combined balance.
| When | Type | Net change BTC | Block | Transaction |
|---|---|---|---|---|
| Loading movements | ||||
Possible internal move: a round amount of 10 BTC or more to or from an address not on the tracked list. Treasury transfers usually look like this, so verify against river.com/reserves before treating it as an outflow. Likely ownership proof: a small spend within a week after an attestation. River proves it controls the reserve by sending a set amount each month.