The Standard DeviationDocs
All pagesCustody and the founder

Custody and the founder

Charter 729 in the founder's wallet, the charter reserve, what the keeper, the founder and the multisig can do, and the founder's interest in full.

The pool holds its charters in two places. This page states who holds what, what the automated service, the founder and the multisig can and cannot do, and the founder's interest in full, as a related-party statement.

If you read one page before contributing, read this one.

Two custodies

Charter 729 stays in the founder's wallet. The founder bought it in the founding sale, and charters cannot currently be transferred, so it cannot move to a contract. Its first branch is the founder's; the pool funded the rest.

Every charter the pool buys is held by the pool's charter reserve, a contract. The Reserve mints a charter to whoever buys it, so the charter reserve buys it directly at the charter auction and keeps it. The charter reserve takes purchase instructions only from the pool, approves no charter transfer, and has no function to send its charters anywhere. Every branch of a charter it holds is the pool's.

Where everything sits

AssetHeld by
ETH deposited and not yet spentThe pool contract, refundable to the member who sent it
ETH a purchase is spendingThe founder's wallet (for charter 729) or the charter reserve (for a new charter, or a charter it holds), only inside the transaction that spends it; whatever that transaction does not spend returns before it ends
Charter 729, its branches and the balance they earnInside the Reserve, under charter 729, held by the founder's wallet
Bought charters, their branches and the balance they earnInside the Reserve, held by the charter reserve
$STANDARD for withdrawals, instalments and feesThe pool contract
The $STANDARD remainder of a swapThe custody that made the swap, reported by its pooledStandard()

Before it hands either custody ETH or $STANDARD, the pool checks the custody's code against the code it was built for: the founder's wallet must be running the published delegate, and the charter reserve must be the published contract. If either has changed, the pool refuses.

What the automated service can and cannot do

The automated service — the keeper — acts only through the governor contract, which acts on the pool; each custody accepts a governed call only from the pool. A transaction the keeper sends to a custody directly is refused.

The governor accepts twelve actions from it: file a valuation report, start the pool, buy licences, buy a charter, admit deposits, settle the weekly round with its instalment, rotate branches on charter 729 or on a charter the reserve holds, claim vested fees to the fee recipient, return idle ETH, and open or settle an announced admission window. It chooses when, and, within the contracts' limits, how many branches to rotate and how large an instalment is. The limits themselves are on chain (Operating policy).

It cannot withdraw funds, make arbitrary calls, change the policy, pause the pool, or appoint its own replacement.

What the founder can do

The founder's wallet administers the governor. It sets the policy, including the reserves and other liabilities the governor's reports count against the pool's value; it can file reports and act for the governor directly; it replaces or removes the keeper; it can close the intake to new deposits; it pauses and unpauses the pool; and it can hand the pool to a new governor. It also sets both custodies' licence limits, and can switch charter purchases off at the charter reserve.

The founder's own key is not bound by the delegate's rules: it can act on the wallet, and on charter 729, directly. Contributing therefore means trusting the founder as custodian of charter 729. No contract prevents it, and this documentation does not claim otherwise. The charter reserve has no such key: nobody can move its charters.

Changing a limit is something we undertake to give seven days' public notice of. That is a commitment, not a contract rule: setPolicy carries no delay. Separately, a report that puts the unit price more than 10% below its recent high stops the pool converting deposits for 24 hours.

The multisig

A multisig that needs two of its three keys can replace the pool's accounting contract at any time, without a waiting period, and receives the pool's fees. The founder holds all three keys, two of them on hardware wallets. The multisig is also the guardian: it can pause the pool, stop the keeper and switch charter purchases off, but it cannot unpause the pool or change the policy. Upgrades that are not urgent are announced in the app a day ahead. Security and audits and Contracts and addresses say more.

The founder's interest

Stated in full, as a related-party statement.

ItemTerms
The founder's interestCharter 729's original branch and its earnings. They are the founder's, not pool assets.
The pool's interest in charter 729The branches the pool paid for, and their earnings.
Sale of the founder's interestThe founder intends to sell it to the pool later. No time, price or terms are set, and nothing is owed for it today.
Fee10% of realised profit, net of realised losses, paid to the multisig. Fees accrued in a 30-day epoch become claimable only once the following epoch has ended, so between 30 and 60 days after accrual, and are clawed back by later losses while unclaimed.
Operating costsThe keeper's transaction costs are borne by the operator, not charged to members.

How the split on charter 729 works

The Reserve has no branch-level owner, so the founder's wallet keeps the split itself. What the charter held when the pool was bound to the wallet is the founder's. After that, every branch earns the same share of the daily issue, so between two readings the founder's share grows by the founder's branch's part of the growth, and the rest is the pool's. When branches retire, the founder's slice of what they release stays in the wallet and only the pool's slice is sent on. A fall the wallet's code cannot explain, which only an action outside that code could cause, is shared in proportion.

This is a ledger convention kept by the wallet's code, not an upstream fact: the Reserve cannot enforce it, and it cannot isolate the pool's branches from actions taken with the founder's key.

The founder's wallet holds charter 729, is operated by the founder's own key, administers the governor, sets the valuation policy and can file valuation reports. The founder also holds the multisig's keys and receives the fees. Treat any eventual sale of the founder's interest to the pool as a related-party transaction: it needs a stated method, disclosed evidence and a named scope before it happens.

What the code review covered

The pool's contracts have been reviewed by the operator and by reviewers the operator engaged, with tests that reproduce each finding against the real contracts, and the findings were fixed. There has been no audit by an independent security firm, and this project has not reviewed the Reserve's own contracts. Security and audits says what was reviewed and what was not.

The limits above are enforced on chain; the founder's key over charter 729 is not.