The Standard DeviationDocs
All pagesOverview

Overview

Technical documentation for The Standard Deviation. How the pool runs, what enforces it, and who holds what.

This is the technical documentation for The Standard Deviation: what the contracts enforce, what the operating policy says, and who controls what.

The argument for the design — why pooling beats running a bank alone, and what the pool is modelled to earn — is the thesis . The thesis is canonical. Where this documentation disagrees with it on intent, the thesis is right and this is out of date; where it disagrees on what is built, these pages are describing the code and say so explicitly.

Where things actually stand

The contracts are deployed and running. Every address is on Contracts and addresses, with the commands to check each claim on this site against the chain yourself.

Three things are worth knowing before you read anything else:

  • No security firm has audited the code. It has been through several adversarial reviews by more than one reviewer, each with executable proof-of-concepts against the real contracts, and they found and fixed real bugs. That is not a paid audit. Security and audits says what was reviewed, by whom, and what was not.
  • The pool's charters are held in two places. Charter 729 stays in the founder's wallet, and you are trusting the founder as its custodian. Charters the pool buys at the Reserve's charter auction are held by the pool's charter reserve, a contract with no function to transfer them or approve their transfer. Custody and the founder states both in full.
  • The operating policy is live, and its limits are in the contracts: what the pool may pay for a charter or a licence, and the highest retirement fee at which it may rotate branches. An automated service chooses when to act within those limits. The policy can change with seven days' public notice. Operating policy sets it out, and Accounting describes what the code does with the money.

The pages

PageWhat it covers
The Reserve's rulesIssuance, retirement, licences, charters, exit fees and dormancy — the upstream mechanics every policy below is a response to
Operating policyWhat the pool buys and when, how it rotates branches to pay out, the constants, and the seven-day notice rule
Custody and the founderCharter 729 and the founder's wallet, the charter reserve, the governor's limits, and the founder's interest
Contracts and addressesEvery deployed address, who controls what, and how to check all of it from the chain
Security and auditsWhat protects contributed money, what the keys can and cannot do, and what review the code has and has not had
AccountingUnits, the pool's value, the fee rule, withdrawal rounds, weekly instalments and rounding
Using the appThe screens, the figures and the unavailable states
Terms and constantsGlossary, fixed values, and the words that mislead

The shape of it, in one paragraph

Contributors send ETH to the pool, which takes it whenever it has something to buy: branches for a charter it holds, or a new charter. There is no limit. A member's ETH stays theirs, and refundable, until a purchase spends it, the earliest first; the purchase converts what it spends to units at the pool's value just before it, so the price is set when the purchase happens, never at the deposit. The pool fills one charter at a time. It buys a new charter at the Reserve's charter auction only once its ETH covers every empty branch slot and the charter too, and never for more than 5% over the auction's last completed sale; it buys branches at the licence auction, swapping ETH to $STANDARD. Branches earn a share of the Reserve's daily issue as a balance inside the Reserve — not as tokens. The only way to turn that balance into $STANDARD is to retire branches, which destroys them, so the pool rotates: it retires a few branches of a charter and buys as many back in the same transaction, from that charter's own balance, releasing earnings without shrinking. What a rotation releases is paid in $STANDARD: withdrawals first, in the weekly round, then the rest to members in weekly instalments, in proportion to their units. Leaving is a request paid over those weekly rounds, at the same value per unit a purchase uses.

What this is not

There is no promised return, no minimum payout, no withdrawal completion date and no guarantee that operating the pool earns more than it costs. Pool units are not $STANDEV and carry no entitlement to it. The thesis publishes modelled returns under explicitly stated assumptions; a model is not a forecast, and the figures move with every auction.

Where evidence cannot support a number, the app says so rather than showing a confident zero, and a figure being read again keeps its last reading, marked as updating.