A NETWORK

Proof of Reserves

Proof of Reserves and Transparency

Every figure below is read from a public chain in your browser while you watch. Nothing is self-reported, cached by A Network, or signed by an operator. Addresses are the ones published in the whitepaper; click any of them to verify independently.

—

CHECKS PASSING

—

VAULT wANET

TREASURIES

BRIDGE VAULT RECONCILIATION

INTERFACE FEE REVENUE LEDGER

INFLOWS TO THE EVM RESERVE TREASURY, RECONSTRUCTED FROM BNB CHAIN TRANSFER EVENTS loading…

SUPPLY INVARIANT

PUBLISHED DOCUMENT INTEGRITY

METHOD AND LIMITS

How to read this page. Balances come from eth_call / eth_getBalance on BNB Chain and Ethereum, getBalance / getTokenAccountsByOwner on Solana, the Blockstream Esplora API for Bitcoin, and the public A Network Layer 1 API. Revenue is reconstructed from ERC-20 Transfer events whose recipient is the treasury; the sender of each transfer is shown so you can distinguish interface fees from other deposits. USD values use the live DexScreener and CoinGecko prices at the time you load the page, not historical prices.

What this page proves and what it does not. It proves what the published addresses hold and what entered them, at the moment of your request. It does not prove who controls the keys, and it is not an audit opinion or a financial attestation. Native-coin (BNB, ETH) inflows cannot be enumerated from an RPC node without an indexer, so only the current native balances are shown. Operating expenses paid out of the treasury are visible as outflows on the explorers linked above.

Layer 1 export liabilities. The Layer 1 export ledger (/bridge/burns) is behind the operator switch described in whitepaper Version 4.6. While it is switched off the page reconciles from the BNB Chain side only: vault balance plus total released equals the wANET escrowed, and the number of release events on BNB Chain is the number of exports ever honoured. When the switch is on, the page additionally compares pending Layer 1 burns with releases.