Docs
Features

WALLET

The account the other panels act on, and how its balance is found.

WALLET is the account the other five panels act on. It is what you check, rather than what you open the product to reach.

What is held

A single figure cannot say that money is real and sitting in the wrong place, so the pools are read and shown separately.

Ironwood
provable
Read, held and provable. This is the pool the circuit speaks about and the only one a proof can be built from.
Orchard
read
Read and held, never proved. A holder with funds here has done nothing wrong and has one step left, so the row says migrate rather than warning them.
Transparent
public
Public, traceable, and outside the circuit. It is shown because a completed scan that hid it once reported zero over money the same seed controlled. One signed step shields it.

Finding a balance

No server holds your balance, so the browser finds it. It asks the relay for compact blocks and tries to decrypt every action with your viewing keys.

Two pools are requested
Only Ironwood can be proved, and a holder who shielded into Orchard would otherwise be shown a confident zero. Sapling is not requested at all.
Every wallet starts at activation
A wallet derived from a Solana account is not new, so scanning from the tip would report a confident zero over money that is really there. A slow correct answer beats a fast wrong one.
Every resume rolls back 100 blocks
Proof of work settles in probability, so a resume exactly where it stopped would hold a note from a reorganised block forever. Rolling back too far costs seconds. Not far enough costs a wrong balance permanently.
A full restore in the browser
~93 s
Both pools, two viewing keys, and hundreds of thousands of trial decryptions. Every sync after it is seconds. The Measurements page has the breakdown.