Docs / Token
Treasury and Revenue
Two cold wallets with two jobs. Where the treasury came from, what the revenue wallet holds now that the project's revenue goes to stakers, what both pay for, and how to watch them.
The project keeps two wallets, both accounts of one hardware wallet, each with one job:
| Wallet | What it holds | What goes in |
|---|---|---|
| Treasury | the launch capital: the SEED bought at launch that the airdrop did not use | nothing after launch, except SEED back that could not be delivered when a season expires, stakers' rewards not claimed within their year, and what it claims from its own stake |
| Revenue | what the project retains for its costs | each week, the costs taken out of the revenue before it is shared with stakers; nothing else |
Neither wallet is the seller's operating wallet. Each of them signed to accept its role, in two steps, propose then accept, so that a wrong address could be corrected before anything moved. Both addresses are on Verify it yourself.
Where the treasury came from
The treasury started with the VVV the project earned by selling inference: settled USDC, swept into VVV, sweep after sweep, since September. In the launch transaction all of that VVV bought SEED from the pool at the launch price. The airdrop was carved out of that SEED first; what remained is the treasury's balance.
So the treasury holds SEED it bought, not SEED it minted for itself, and the VVV it paid is in the pool, where anyone can sell into it.
Where the project's revenue goes
| Source | How | Where it ends |
|---|---|---|
| The project's share of sales | Of the 15 % kept after participants' 85 %, 5 points buy SEED back for buyers. The other 10 points accumulate in VVV and, each time the accumulated amount passes $30, go out in three legs: 34 % stays VVV, 33 % buys SEED in our pool, 33 % buys DIEM on the open market (the VVV/DIEM pool on Aerodrome). They are held by the project's operating wallet until the week closes | the week's budget for SEED stakers, after costs |
| The pool's 1 % fee | accrues to the locked position; collect() sends it to the beneficiary, the project's operating wallet, in SEED and VVV |
the week's budget for SEED stakers, after costs |
The $30 trigger and the 34 / 33 / 33 split are policy, published here. They are fixed each time a round opens, so a change applies to every round opened after it, including the VVV that was accumulating before the change; a round already open keeps its own numbers. The share of each source that goes to stakers is published on Staking, with the week any change takes effect. A change gets a line in the changelog before it takes effect. The DIEM leg is a purchase, not staking: the budget holds DIEM as an asset, the same way it holds VVV and SEED.
Nothing else. There is no mint, no team unlock, no reserve of SEED that was never bought.
What they pay for
Running costs. The server, the domain, the fees of listing the token on explorers and trackers. These are taken out of each week's revenue before it is shared with stakers, at the amounts published on Staking, and land in the revenue wallet. The project does not pay salaries; it is run by AI agents and one person who checks on them.
What the two wallets do and do not do
- The treasury may stake, like anyone. Its stake, its points and what it claims are public on the staking contract and the distributor, under its address. The revenue wallet does not stake.
- They do not vote, if voting ever exists.
- They do not promise never to sell. If the project needs to pay a cost in dollars, it may sell SEED, VVV or DIEM into the market like anyone else. When it does, it is a public transaction from one of the two addresses.
How to watch them
- Both wallets' balances on Basescan, from the addresses on the verify page.
- Every
collect()is a transaction on the lock contract, paying the beneficiary. - Every sweep of USDC into VVV is a swap from the seller's wallet. In each round, the SEED and DIEM legs are swaps into the seller's wallet, visible one by one; the VVV leg does not move, it stays in that wallet and is listed in the week's published file. After each week closes, one transfer per token from the seller's wallet to the revenue wallet is the week's retained costs; the rest goes to the stakers' distributor.
- Every week's list, costs and roots are published with the staking page, and the treasury's own claims are
Claimedevents under its address.
If the rules on this page change, this page changes first and the changelog says when.