Contracts and addresses
Every address the pool deploys, controls or depends on, what each one can do, and how to verify all of it yourself.
Every address this project deploys, controls or depends on, with what each one is allowed to do. Nothing here is a contribution instruction; read Security and audits before you act on any of it.
Addresses are written in their EIP-55 checksummed form. If an address you were given elsewhere differs from the one here by more than capitalisation, it is not ours.
The pool is on Robinhood Chain, chain ID 4663, the same chain as Standard Reserve. It is not on Ethereum mainnet and is not deployed on any other chain. An address carrying the same bytes on a different chain is a different contract.
The pool's contracts
These are ours. Each one's runtime code was compared byte for byte against the reviewed build before it was put to use, excluding the slots the compiler fills with constructor values.
| Contract | Address | What it is |
|---|---|---|
| Pool | 0x81C77388a9a6F4E140c4b54BCd12b586C728D2F4 | The contract members interact with. Holds deposits, units, payouts and withdrawal rounds. This is the only address a member ever sends ETH to, and the only one of the pool's parts anything calls. |
| Pool code, part one | 0x618716dE3c5596117E0cd99fB8aBF7C75Ff5FDAa | What members do: depositing, refunding, claiming, requesting and collecting a withdrawal. Holds no funds and no state; inert at its own address. |
| Pool code, part two | 0x9D82fC043a5C3A164A08d1B06f9501434b477774 | What the governor does to the ledger: starting the pool, valuation, fees, payouts, admission and the weekly withdrawal round. Also inert. |
| Pool code, part three | 0x84594bc5698c4a2216602E1cAf6b55bC40ef2961 | What the governor does with the charters the custodies hold: spending ETH on licences, opening and retiring branches. Also inert. |
| Pool code, part four | 0x19b8dc44BeF446b8d9a4d0BEB50D742A39Af1917 | Buying charters at the Reserve's charter auction, and licences for them, through the charter reserve. Also inert. |
| Deposit queue | 0x50660d878245946f186DD445d1b39F95964c1171 | Keeps members' deposits in the order they arrived, so that a purchase spends the earliest first. Holds no assets, and only the pool may write to it. |
| Charter reserve | 0xA5abB07752e5ff77EF52C853824B05f299B805c2 | Holds every charter the pool buys. Takes instructions only from the pool, keeps no ETH between calls, and has no function to move a charter out. |
| Governor | 0x904092df2E0Be671B26202598bDD82B2f497C148 | Owns the pool and is the only account the pool takes governed instructions from. Its code cannot be replaced and its wiring was fixed at construction; its policy is set by the founder, within limits fixed in its code. |
| Governor's lens | 0x2a606AE616f98ddd376d122403003221bfCa963e | The views the governor decides by: what the pool can spend, which charter to fill next, whether a charter can be bought and what the charters are worth. Holds nothing and can do nothing. |
| Charter sale history | 0x3E0D87194a9E15c10414413Cb5Eb2457D285d948 | The last five completed charter sales, which the pool's value uses. A new sale is recorded from the charter auction itself; earlier sales come from a record the founder supplies. |
| Adapter | 0x8834fEc2f9439744a96a5E258b0D72424F7a76cD | Proved the custody binding when the pool started. |
The pool's code is in four parts because one contract cannot hold it. Only the pool is ever called; it hands on what it does not itself declare, each part to the next, and each part refuses to be built on any configuration but the pool's. The pool address is a proxy, so the code behind it can be upgraded: see Who can change the code below and the security page.
| Deployment fact | Value |
|---|---|
| Pool creation transaction | 0x3ee37802117f08f02ab9b80b1288f1ee3f500406815565213ee8568693625b00 |
| Pool creation block | 68,783,875 |
| Deployer of the pool, its four code parts, the charter reserve, the governor, the adapter and the delegate code | 0xd85209C6aF614c859797B38febE5118A9173Fb6B |
| Created by other contracts | The deposit queue, by part four; the lens and the sale history, by the governor; the proxy administrator, by the pool |
| Contract source revision | 3b2ae8bbee5a219a5fb956a486012a3839d3dfd5 |
| Compiler | Solidity 0.8.30, optimiser 200 runs, IR codegen (via_ir), Prague |
0xd85209C6… is an ordinary account that paid gas. It holds no role in the deployed system and no power over anything it created. Each contract's creator can be checked from the chain: a contract's address is fixed by the account that created it and that account's nonce.
Who controls what
| Role | Address | What it can do |
|---|---|---|
| Governance multisig | 0x578E27D42C850d8b6ebe66D666f02c9aa045310E | A 2-of-3 Safe. Administers the proxy, so it can replace the pool's code. As guardian of the governor and of the charter reserve it can pause the pool, revoke the keeper and switch charter purchases off. Receives the fee. Short of replacing the pool's code, it cannot unpause, set policy or move member funds. |
| Founder wallet | 0x86B0F0dFb53AD14315D05956AE27cc608FEf381f | The custody of charter 729, and the governor's administrator. Sets policy and the keeper, pauses and unpauses, closes or opens the intake, can call any governed function on the pool by hand, and can hand the pool to a new governor. As the charter reserve's administrator it sets its licence limits and can switch charter purchases on or off. Supplies the charter sale history's earlier sales. Holds charter 729 and the $STANDARD remainder of its swaps, alongside the founder's own money. Pool ETH reaches it only inside a transaction that returns what it did not spend before that transaction ends, and only while it runs the delegate code below. |
| Founder delegate code | 0x2B66156a130BCac987E851b912B94f8aabC8EEfe | The code the founder wallet runs under EIP-7702. It accepts governed calls from the pool and nothing else, bounds what each purchase may spend, and is what buys through the Reserve's licence auction for charter 729. |
| Keeper | 0x3216354cfe55773Cc0B845F3A26921455a9E042E | An automated operator key. It calls the governor and nothing else, and the governor accepts twelve actions from it: reports, starting the pool, buying licences, buying a charter, admitting deposits, settling the weekly round with its instalment, rotating branches on charter 729 or on a reserve charter, claiming vested fees, returning idle ETH, and opening and settling an announced admission window. It chooses when; the contracts bound the rest. Revocable by the founder or the Safe. |
| Proxy administrator | 0x7eC43Cf1B5bf628c64ADA5BF5fF137d0759F443e | Holds the upgrade right for the pool. Owned by the Safe; it does nothing on its own. |
The Safe has three keys and a threshold of two: any two of them acting together can exercise the powers above. All three are the founder's: the founder wallet and two hardware wallets. The Safe is the founder's own key security, so that no single key can replace the pool's code; it is not a check on the founder.
The founder therefore holds the Safe's keys and is the custodian of charter 729 and the governor's administrator. That is a concentration of control, it is deliberate, and it is stated in full in Custody and the founder.
Who can change the code
Four separate powers:
- The pool's code can be replaced by the Safe, 2-of-3, through the proxy administrator. This is the only way the pool's fixed economic constants, such as the fee, can ever change. Upgrades that are not urgent are announced in the app a day ahead.
- The governor's code cannot be replaced at all. Replacing the governor means the founder handing the pool's ownership to a new contract.
- The charter reserve's code cannot be replaced, and the pool is bound to it once. No upgrade of the pool can give the charter reserve a way to move a charter out.
- The founder wallet's delegate code can be replaced by the founder's key alone. That is a custody migration, not a routine change: the pool checks the wallet's code before handing it anything, so it neither buys nor opens branches on charter 729 through a replacement until the Safe upgrades the pool's code to name it.
The contracts do not announce an upgrade themselves. Read the pool's implementation slot yourself if you want to know what code it is running; the command is below.
The Reserve's contracts
These are not ours. Standard Reserve is an upstream protocol this project depends on and does not control, has not written and has not reviewed. They are listed so you can see exactly what the pool touches.
| Contract | Address |
|---|---|
| $STANDARD token | 0x88ad8DdF1E3898412146a534538d418c6F8A9062 |
| Charter NFT | 0x69101f92427376FA80476A997d024cf9dC3EaE39 |
| Central bank | 0x5977B25419f9c0dDcB2F89fE204955622f4F57ea |
| Registry | 0x855C294dD019E9e0d84C058cFF7404f5F2dDCa4b |
| Tax hook | 0xF1eE073811B14359D850825E48d200483200eDcd |
| Licence auction | 0x7CD3c6ec047B1A21ea65AF64D7c850e6f6049015 |
| Charter auction | 0x1E369e5977e1d90D9A1Ec52aC72a124346E622E4 |
| Founding sale | 0xF54B589EADC2aaE98b96DaD58d89BCBF27503e46 |
| Expansion vault | 0x6f457765035958725367a1D4C1f6064b047DAdB3 |
| Contraction vault | 0x796e80E8ABcedc30c700A9587F7933d3342B8946 |
| Liquidity manager | 0x50e4C444f71dF2Db8593c6c8ba4d493De618E147 |
| Fee splitter | 0xaa12DEda4aC19233A315777b17ff6ff5029D01b2 |
| Executor | 0x01C0335B8389564096a2B76c5BaA89980bf71fBb |
The Reserve names its auctions in its registry and can replace them. The charter reserve reads the registry at every purchase and uses whichever auctions it names, provided they belong to the Reserve's own bank. Charter 729 is different: the founder wallet is bound to one licence auction, the binding is checked on every purchase, and if the Reserve replaces that auction, charter 729 stops buying until the founder rebinds it.
Charter 729 is held in the founder's wallet; the charters the pool buys are held by the charter reserve. The Reserve does not currently allow charters to be transferred.
Verifying this yourself
Every claim above is a public read. None of these commands sends a transaction or needs a key. Set $RPC to any Robinhood Chain endpoint you trust, ideally your own node.
Which contract owns the pool, and what code the pool runs:
cast call 0x81C77388a9a6F4E140c4b54BCd12b586C728D2F4 "owner()(address)" \
--rpc-url $RPC
cast storage 0x81C77388a9a6F4E140c4b54BCd12b586C728D2F4 \
0x360894a13ba1a3210667c828492db98dca3e2076cc3735a920a3ca505d382bbc \
--rpc-url $RPC
The first returns the governor. The second is the ERC-1967 implementation slot; its last 20 bytes are the address of part one, which should equal the one listed above. The other parts, and the deposit queue, follow from the pool:
cast call 0x81C77388a9a6F4E140c4b54BCd12b586C728D2F4 "extension()(address)" \
--rpc-url $RPC
cast call 0x81C77388a9a6F4E140c4b54BCd12b586C728D2F4 "holdings()(address)" \
--rpc-url $RPC
cast call 0x81C77388a9a6F4E140c4b54BCd12b586C728D2F4 "charters()(address)" \
--rpc-url $RPC
cast call 0x81C77388a9a6F4E140c4b54BCd12b586C728D2F4 "admissionQueue()(address)" \
--rpc-url $RPC
What the governor is bound to: the keeper, the guardian, the charter reserve, its lens and its sale history:
cast call 0x904092df2E0Be671B26202598bDD82B2f497C148 "operator()(address)" \
--rpc-url $RPC
cast call 0x904092df2E0Be671B26202598bDD82B2f497C148 "guardian()(address)" \
--rpc-url $RPC
cast call 0x904092df2E0Be671B26202598bDD82B2f497C148 "reserve()(address)" \
--rpc-url $RPC
cast call 0x904092df2E0Be671B26202598bDD82B2f497C148 "lens()(address)" \
--rpc-url $RPC
cast call 0x904092df2E0Be671B26202598bDD82B2f497C148 "saleHistory()(address)" \
--rpc-url $RPC
Who administers the proxy, and who holds the Safe:
cast call 0x7eC43Cf1B5bf628c64ADA5BF5fF137d0759F443e "owner()(address)" \
--rpc-url $RPC
cast call 0x578E27D42C850d8b6ebe66D666f02c9aa045310E "getOwners()(address[])" \
--rpc-url $RPC
cast call 0x578E27D42C850d8b6ebe66D666f02c9aa045310E "getThreshold()(uint256)" \
--rpc-url $RPC
The first should return the Safe; the others its three keys and its threshold of two.
What code the founder wallet runs:
cast code 0x86B0F0dFb53AD14315D05956AE27cc608FEf381f --rpc-url $RPC
It should return 0xef0100 followed by the delegate code's address: that is how EIP-7702 records a delegation.
Which charters the charter reserve holds, and who administers it:
cast call 0xA5abB07752e5ff77EF52C853824B05f299B805c2 "charters()(uint256[])" \
--rpc-url $RPC
cast call 0xA5abB07752e5ff77EF52C853824B05f299B805c2 "pool()(address)" \
--rpc-url $RPC
cast call 0xA5abB07752e5ff77EF52C853824B05f299B805c2 "admin()(address)" \
--rpc-url $RPC
cast call 0xA5abB07752e5ff77EF52C853824B05f299B805c2 "guardian()(address)" \
--rpc-url $RPC
Whether the pool has started, and whether it is paused:
cast call 0x81C77388a9a6F4E140c4b54BCd12b586C728D2F4 "activated()(bool)" \
--rpc-url $RPC
cast call 0x81C77388a9a6F4E140c4b54BCd12b586C728D2F4 "paused()(bool)" \
--rpc-url $RPC
What the pool owns inside each custody between purchases, as distinct from the founder's own money:
cast call 0x86B0F0dFb53AD14315D05956AE27cc608FEf381f "pooledNative()(uint256)" \
--rpc-url $RPC
cast call 0x86B0F0dFb53AD14315D05956AE27cc608FEf381f "pooledStandard()(uint256)" \
--rpc-url $RPC
cast call 0xA5abB07752e5ff77EF52C853824B05f299B805c2 "pooledStandard()(uint256)" \
--rpc-url $RPC
pooledNative() should read zero outside a purchase: members' ETH rests in the pool, and a custody holds it only for the length of the transaction that spends it. pooledStandard() is the remainder a swap leaves behind. The founder wallet's own balances are never the pool's.
What this page does not tell you
- It is not a price, a size or a schedule. Figures that move — what the pool holds, what a unit is worth — are shown live in the app and deliberately not written here.
- It does not prove the code is correct. Matching bytecode proves the deployment is the reviewed build. Whether the reviewed build is right is the subject of Security and audits.
- It does not authenticate the Reserve. The upstream addresses are read from the Reserve's own registry and bank, and the founding sale from its published directory. This project has not reviewed that code and does not vouch for it.
- It is not a complete transaction history. Deployment and configuration transactions beyond the pool's creation are retained in the project's internal release record, not published here.