Using the app
The app's screens, what each figure means, and what its unavailable states mean.
The app is still being validated and public contributions are not open. This page covers how to read its figures, and which of them mean less than they appear to.
Before anything else: the environment notice
The app loads its own selected deployment. It never asks you to paste a contract address, a manifest or an RPC endpoint. Connecting a wallet moves nothing and signs nothing; transaction access additionally requires the deployment and release checks to pass.
| Notice | What it means |
|---|---|
| Local preview, test funds | Figures come from an actual local rehearsal with test assets and simulated chain time. Not a live position. |
| Public contributions are not open | Verified deployment or release requirements are missing. Not a pool balance of zero. |
| Connected to Robinhood Chain | A configured public deployment passed the current release checks. A contribution still needs an accepting round and your wallet approval. |
| Loading / indexing | Evidence is being obtained or verified. A partial history is never shown as a complete record. |
| Stale / not available | Current evidence cannot support that value. An old assessment is not substituted for a current one. |
In a configured local preview, View sample member shows the rehearsal account without a wallet. Its buttons cannot spend from that account.
How a page is built
Every route is a heading, a row of at most four tiles, one or two rows of cards, then a More detail run of folds.
- A tile is a label with an info mark, one value with its unit set small, and one context line.
- A card is a title, one figure or functional graphic, a few label–value rows, and at most one action.
- A fold holds the detailed panels.
Definitions live behind the info marks. Freshness is stated once per page. Colour carries state only — plum for members, copper for distributions, ink for the pool — so a figure's colour is never decoration.
The five screens
| Screen | What to look for |
|---|---|
| Dashboard | Pool assets, wallet and bank balances, holdings, realised distributions, Reserve conditions, estimates and recent activity |
| Position | Your units, assessed stake value, distributions, ETH commitments and refunds, queued units, funded withdrawals and your own activity |
| Reserve | Public Standard Reserve policy, flows, supply, auction inventory and timing, and the largest banks by branches |
| Activity | Receipt-verified pool operations and contributor transactions, filterable and paginated |
| Strategy | Round and settlement state, fee and distribution rules, allocation priorities, executed operations and configured addresses |
Reserve observations describe the Reserve as a whole. They are deliberately separate from pool accounting and are not a rate of return.
The operating bank panel
The dashboard carries a panel for charter #729, marked founder-owned and operated.
The balance shown is included in pool operations but is not cash available for distribution or withdrawal — under the Reserve's rules a balance becomes $STANDARD only when branches are retired. The founder's entitlement is shown as the benchmark described in Custody and the founder, and the purchase of the charter is deferred with no liability in version 1.
If the charter is ever observed not to be held by the designated wallet, the panel is suppressed rather than reassigned.
The chart, and what it is not
The chart switches between cumulative profit recognised for distribution and cumulative declarations. Deposits are excluded.
Costs and losses can arise after profit was recognised, so the first line is not lifetime net profit and loss — it does not decrease when a later loss lands. Expand the receipt-accounting fold for recovered capital, costs still to recover and realised loss carry. An empty chart means there are no reconciled results to plot; it is never filled with invented performance.
Coverage, and what it does not tell you
Three different things are called coverage:
- Liquid withdrawal coverage compares available $STANDARD with currently assessed queued value.
- Recognised liabilities against assessed assets includes funded claims, fees and reported liabilities. It does not treat queued units as secured debt.
- Unfunded ownership in withdrawal is the proportion of units currently queued.
None of them gives a repayment date, and none says anything about the quality of an appraisal.
Estimates
Estimates are modelled from the last licence auction's price, the Reserve's emission rate and the retirement policy, run day by day, with the cost of swapping ETH counted as part of what members put in. Their one assumption about the future is how far the Reserve grows.
Read them as a model at one block, not a forecast. The figures move with every auction — a different day's auction price can change a modelled annual return by a wide margin, and a cut in issuance, a higher exit fee or the Reserve raising its limits all lower it. In ETH they additionally depend on $STANDARD's price when you are paid.
Changing a scenario assumption changes no policy and sends no transaction. Zero assumed costs is an assumption, not evidence that operating the pool is free. Where evidence cannot support an estimate, the app shows not available rather than a confident zero.
Activity totals
Contributions, refunds and collections are distinguished from internal funding allocations. Contributing wallets is a historical count including people who cancelled or left — not a current holder count. Local test transaction hashes do not resolve on the public explorer, and your wallet's own submission list is separate from the verified pool event history.
Reviewing an action
Every member action is presented for explicit review before it is sent, with the exact call and its consequences. A submission whose response is lost leaves a pending marker and blocks a duplicate send rather than silently retrying. An unresolved or reverted transaction needs reconciliation; it is never treated as permission to try again.
Your personal wallet holdings appear under Position and never increase pool totals.
What the app shows that policy v1 would change
The app currently displays the deployed distribution model — targets, funded claims and collections. Operating policy v1 pays out everything a retirement brings in, in proportion to units, without redeeming them. That is a contract change which has not been reviewed, so the app describes the code rather than the published policy. Accounting marks each place the two differ.
Public contributions are not open.