Treasury controls, on chain
Read from the treasury's own config account. Who may move funds, and what an outflow has to pass through first.
Reading the treasury config
Waiting on the chain.
Treasury YUID vault
The 150,000,000 YUID treasury allocation, read from the token account. Separate from the SOL vaults above — a different asset in a different account.
No mint to read the vault for
The vault address derives from the mint, and the supply ledger has not reported one yet.
Treasury SOL vaults
Connect a wallet to read the lamport balances from Solana.
Activation destinations, last reported
The three SOL vaults activation pays into, as the treasury's events last reported them. Balances update when a vault pays out, not when it receives — see the panel above for a direct read.
No pool balances yet
No outflow event has reported a balance. The vaults still receive every activation; nothing has moved out of them to report.
Ecosystem programmes
Every programme, what it was authorized, and what actually moved. The §9 audit trail.
No programmes exist
Creating one is a protocol-authority action, and funding it is a second.
Treasury
Protocol revenue accrues to the treasury, which funds development, liquidity, operations and ecosystem programmes. Every balance above is read from its account; the panel below says what a treasury page conventionally shows that this one cannot.
What this page does not show
Two different reasons, and they do not have the same fix
Fee revenue reaching the treasury is visible today per participant, in base units, on the Economic Graph page. What is missing is the aggregation over time, not the underlying record.