Staking Transparency

Proven cryptographically, checkable by an outsider without trusting us:

• Every staking event sits in an append-only chain that cannot be reordered, edited or deleted without breaking a published signature — including every admin capital deposit and withdrawal.
• The history you were shown last week is the same history everyone else sees today (consistency proofs between signed tree heads — this page pins the last head your browser verified and checks it on your next visit).
• Proof of Liabilities: your balance was counted in the published total owed to stakers, and that total is the honest sum of all counted balances — the sums are bound inside the tree's hashes, so an understated total cannot survive verification.
• Every published epoch (returns, fees, price, mints, burns) replays deterministically from the log alone.

Not proven: that the coins exist. Crypto custody is delegated to a payment processor — this platform holds no address keys and cannot sign from any address. What the asset side publishes is Attested Reserves: a balance statement signed by a named party (the wallet service's own key, or an auditor whose statement was recorded). That proves the party asserts the balance — testimony you can verify came from them, not proof the funds are on-chain. Currencies without an attestation are shown as exactly that: unattested — never hidden, and never presented as solvent or insolvent either way.

One more honest limit: tree heads are not yet anchored to an external timestamping service, so a signed head proves non-rewriting only relative to a head you already hold — which is why this page pins heads in your browser between visits, and why the export is downloadable for independent, offline replay.

This page's checks run in your browser, but the code still came from us. The stronger path is the open staking-verify CLI, a public, standalone project with its own build instructions and release binaries: feed it the raw export, the signed heads and the key registry, and it re-derives everything from scratch — chain hashes, signatures, Merkle roots, consistency, your liability proof (-pol proof.json), the attestation arithmetic — and replays every balance from the log alone.

The downloads on this page (and the buttons on each pool above) serve the byte-exact material the CLI consumes: the canonical NDJSON export, the signed tree heads, and the key registry. Nothing about the format is browser-specific — a few hundred lines in any language reproduce every check from the published spec.