CTO-1.9
Treasury on a multisig
"The community treasury sits in a multisig wallet, and its address is published."
Where does a takeover team's money go? With Open Books the team shows it. Its verified lead connects the team's wallets, and codeflex.si publishes every payment in and out as read from the Solana chain, with the team's label on each one and a sealed statement every month. It is a public ledger of what the connected wallets did: not an audit, not a guarantee and not advice.
Live / Read from the chain
Each token has a ledger page, a statement page per month and a badge that names the last sealed month.
Every count is real and started at zero on November 19, 2026.
Loading the books.
How it works
Free message signatures only, never a transaction. The chain is the only source.
Step 1
Sign in with your SI Passport. The page checks that you are the verified lead of the token on the CTO Registry.
Step 2
Each wallet is connected with a free message signed by that wallet itself, naming the token and its role: treasury, marketing, liquidity or team.
Step 3
From that moment every SOL and token transfer of the wallet is read from the chain and listed. You add a label and a short note; you cannot hide a row.
Step 4
When a month ends and every wallet is read past its end, the statement is sealed at a fixed address. The badge names that month.
What CTO-1 asks for
The CTO-1 Standard asks a takeover team to publish its treasury and its official wallets. Open Books is the free way to do it, and to keep doing it.
CTO-1.9
"The community treasury sits in a multisig wallet, and its address is published."
CTO-1.11
"A public page lists the official wallets, locks and burns."
A multisig vault is a program address and cannot sign a message, so it cannot be connected here yet. Connect the wallets that can sign, and publish the vault's address in your CTO-1 application. Open Books does not replace the CTO-1 review.
For verified leads
Paste the token contract. Connecting the first wallet opens the books. Up to 8 wallets per token.
The rule card
The ledger says exactly what it covers and what it does not.
Always
Never
SCOUT lists new transactions of up to 4 wallets and reads up to 30 transactions in full every 5 minutes, from the public Solana RPC. A busy wallet can take a few runs to catch up, and the page says how many are waiting.
The badge
A team puts the Open Books badge on its own site. The badge is an image served from codeflex.si, so it always says what is true today.
Fresh
The badge reads Open Books and names the month of the last sealed statement. New books show when their first statement is due.
Stale
If a month ends and no statement is sealed for it, the badge turns to stale wording by itself. Nobody has to take it down.
The badge code is on each token's ledger page. The token's Registry page and its Takeover Site link to the ledger too.
Questions
If the team keeps Open Books, its ledger on codeflex.si/open-books/ shows every payment in and out of the wallets it connected, read from the Solana chain, with the team's label on each and a sealed statement for every month.
No. It is a public ledger of what the connected wallets did, as read from the chain. Nobody checks what a payment was for, and a wallet the team did not connect is not covered. It is not an audit, not a guarantee and not advice.
The verified lead signs in with the SI Passport, and the wallet itself signs a free message that names the token and the wallet's role. The signature proves the wallet agreed to be shown. It is never a transaction.
No. Every transaction of a connected wallet shows, labeled or not. Removing a wallet does not remove its rows: the wallet stays in the history with the day it was removed.
For each connected wallet, the opening and closing balance of SOL and the token, the totals in and out by label, and the count of unlabeled transactions. The statement has a fixed address and a SHA-256 fingerprint signed with the codeflex.si signing key.
At the moment the wallet was connected. The first statement covers the month of the connection from that moment on, and nothing earlier is claimed.
A multisig vault is a program address with no key of its own, so it cannot sign a message. Open Books connects only wallets that sign for themselves. Publish the vault address in your CTO-1 application.
Nothing. Reading uses the public Solana RPC and Jupiter's free price, and every signature is a free message.
Follow the work as it ships. The team posts what was built, what it cost and what comes next.