Docs / Token
Verify it yourself
Every address we use, with a link, and what to check at each one. Do not take our word for any of it.
Everything these docs claim about the token is readable on Base. This page is the list of where to look. Addresses are given in full here, once; verify them before you interact with anything, and never send tokens to a contract address directly.
Addresses on Base (chain id 8453)
| What | Check |
|---|---|
SEED token0x89a0A44100628B1011EE69783cE867f26c32d07A |
Source verified, OpenZeppelin ERC-20 unchanged. Total supply 1e27 wei. No owner(), no mint, no pause |
VVV token (Venice)0xacfE6019Ed1A7Dc6f7B508C02d1b04ec88cC21bf |
Venice's token; the other side of the pool |
Our seller0xd19ffae0e85b5230422019926b2f37ec0f1f41f3 |
The wallet that receives settlements, runs the sweeps and signed the launch. Also our peer id on AntSeed |
| Pool SEED/VVV, 1 % 0xCe957a148291Fa8F524afB7C0A74917504C5B472 |
Uniswap v3 pool; slot0() gives the price; liquidity() the position's L |
| Lock 0x7A200eBb4a41e9a400EfC0bAD200920E1fD6106e |
Owns position #6611005. Read the source: no function decreases liquidity, transfers the NFT, or upgrades. collect() is public and pays the beneficiary |
Treasury (cold wallet)0x2a03B00a5286d7f02baA567639c265A9966Ff633 |
Holds the launch capital in SEED after the handover and is the treasury of the distributors; SEED balance and every outgoing transaction |
Revenue (cold wallet)0x5224b6A4f01eD3d80927b78249d1EfeD830AAb53 |
Receives only what the project retains for costs each week, from the seller's wallet, in VVV, SEED or DIEM; every incoming transfer |
Airdrop distributor0x67849CDD0a10D993E6b0EEf0FC3dC12d5b22b17d |
Season 0: root frozen, funded with 100,000,000 SEED (10 % of supply, the contract's cap) in the launch transaction, no claim deadline; Claimed events are the delivery receipts |
Staking contract0x4e548ef8f0041FdaD227d68EeCf360Ab5f1547B6 |
No owner. stake, unstake, points readable per account; totalStake is everything staked, the treasury's stake included; stakeOf(address) is one staker's part |
Stakers' distributor0x6df20eA55d56e6b83874D9cB4D030aB391846F73 |
One season per token per week; root frozen, claim deadline one year after the freeze; Claimed and Expired events |
Participants' distributor0xBadb95787654E99B0500F4d14695cEfa37d8f09a |
The SEED bought in the pool for participants from their share of sales; root frozen per season, Claimed events |
Buyers' distributor0xc721f6a78A73817B041Ff245288B470539C7d2A3 |
The SEED bought in the pool and given back to buyers in proportion to what they paid; root frozen per season, Claimed events |
| AntSeed deposits contract on antseed.com/docs |
Where buyers' USDC sits and where channels settle |
Addresses marked "published when live" are filled in here when that contract exists. The launch record, with the block and the transaction hash, is on The launch.
Reading a holder list
A holder scan of SEED sorts contracts and wallets by balance. The largest ones are these. The same list, with every project address and its role, is machine readable at /.well-known/seed-wallets.json. None of them is a team allocation, because there is none: the whole supply went into the pool, and every SEED outside it was bought from it or paid out of it as the pool's 1 % fee.
| Holder | What its balance is |
|---|---|
| Pool SEED/VVV | The SEED nobody has bought yet. It leaves only in a swap that puts VVV in |
| Staking contract | Every stake added up, from every staker. The treasury stakes its SEED here, so this contract shows as one of the largest holders and its first deposits come from the treasury; stakeOf(address) gives each staker's part, the treasury's included |
| Distributors | The stakers', participants' and buyers' distributors hold SEED until each account claims its part. The project funds them, so a scan that traces funding ties every wallet that claims from them to the project: a staker who claims a week's rewards shows up as linked, though nothing was allocated to it |
| Airdrop distributor | The airdrop, 100,000,000 SEED (10 % of supply), until it is pushed to the wallets on the snapshot. It is not the project's to keep |
| Treasury | The part of its SEED it has not staked |
| Our seller | The pool's fees collected in SEED and each round's SEED leg, held for that week's stakers until the week closes |
What the project holds is the treasury, 183,692,551 SEED (18.37 % of supply), and the airdrop until it is delivered, 100,000,000 SEED (10 %): 28.37 % together. Both were bought from the pool in the launch transaction with the project's VVV, at the launch price. To check it, open the launch transaction: one Swap, then a Transfer of 100,000,000 SEED to the distributor and one of 183,692,551 SEED to our wallet, followed by a single transfer from our wallet to the treasury.
The treasury is not locked: it can sell like any holder. A sale by the treasury would be a SEED transfer from its address to anything other than the staking contract. Its whole SEED history is one list: SEED transfers of the treasury. In: the launch capital from our wallet, then its own staking rewards. Out: stake() into the staking contract.
Our seller's SEED history is the same kind of list, SEED transfers of the seller: out, the whole supply into the launch contract (the pool's locked liquidity, not a sale), the launch capital to the treasury and each week's pool fees to the stakers' distributor. Its sweeps of sales into VVV are on VVV transfers of the seller.
Checking our sales on the chain
The live feed is our own record of each request as the seller serves it. The chain is the check on it: every sale is paid through an AntSeed payment channel, and each payment settles on Base.
| What | Where |
|---|---|
AntSeed channels contract0xBA66d3b4fbCf472F6F11D6F9F96aaCE96516F09d |
Its ChannelSettled events (topic0 0x0b287f37d8bd14ef37f2966734ab387c243cc1a1663616a25a4cc259877736b1) with our seller, 0xd19ffae0e85b5230422019926b2f37ec0f1f41f3, as the third indexed topic are our sales being paid. The second data word is the amount settled, in USDC with 6 decimals |
| Per day | Add those amounts up per UTC day and you have what we settled that day. The settled line on Use is drawn from the same events, and antseedstats.com indexes them too |
A channel settles after its requests are served, so a day on the live feed and the same day on the chain are close but not equal: payment for the last requests of a day can land the next day.
What to check, claim by claim
| We say | Where to see it |
|---|---|
| All one billion SEED went into the pool | The launch transaction: Transfer of 1e27 from our wallet to the launch contract, then the position's IncreaseLiquidity event for the full amount |
| Liquidity is locked permanently | The lock's source on Basescan: no decreaseLiquidity, no transferFrom of the NFT, no selfdestruct, no proxy |
| The first buy was ours, at launch | The Swap event in the launch transaction, from the launch contract |
| The airdrop total | The distributor's season 0: rootTotal equals funded equals the Transfer into it in the launch transaction |
| We push the airdrop; nobody claims | Claimed events on the distributor, all from our poster address, one per wallet on the list |
| The treasury holds the launch capital and what its own stake earns | Transactions into the treasury address: one SEED transfer from the seller's wallet after the handover; then only Claimed events from the distributors to its address, and what a season sends it when it expires |
| The revenue wallet grows only by what the project retains for costs | Transfers into the revenue address from the seller's wallet, at most a few per week, matching the costs line of that week's published file |
| Sales become VVV | Swaps USDC to VVV from the seller's wallet on Base; one per sweep |
| What we sold settles on-chain | Channel settlements to our seller's address, on Basescan (also on antseedstats.com) |
The site reads the chain too
The SEED page reads the pool's price, the VVV in it and the share of supply bought from Base through a public RPC in your browser, each time you open it. Nothing passes through our servers. If the page and the chain disagree, the chain is right; tell us.
Compiler warnings on Basescan
The SEED token page on Basescan lists seven known bugs of Solidity 0.8.28, the compiler version the token was built with. Basescan shows that list for every contract built with that version; it is not a finding about this contract. The verified metadata gives the settings (optimizer on, 200 runs, viaIR off), so you can check each one against the official conditions in the Solidity repository (docs/bugs.json):
| Bug | When it can apply | SEED |
|---|---|---|
TransientStorageClearingHelperCollision, MisorderedNamedParametersInRequireWithCustomErrors, SpillSlotCollisionAcrossMutualRecursion, UnsoundSpillInMutualRecursion |
Only with the IR pipeline (viaIR: true) |
Compiled without it |
MemoryByteArrayElementDeleteClearsWholeWord |
delete on an element of a bytes array in memory |
No delete anywhere in the source |
LostStorageArrayWriteOnSlotOverflow |
A storage array that runs past the end of storage, which needs a custom storage layout | No storage arrays, standard layout |
YulOptimizerKnowledgeBaseStaleBookkeeping (rated low) |
Inline assembly, or helper functions the optimizer generates | No inline assembly. What remains are the compiler's helpers that encode name, symbol and error data; on Base they return the expected values and errors |
The last warning is present in every published version of the compiler today, so a rebuild would show it as well. The token is the OpenZeppelin ERC-20 (5.2.0) unchanged, with a single mint in the constructor.
Source code
The token, lock, launch, distributor and staking contracts are verified on Basescan and Sourcify once deployed, so the source you read there is the bytecode that runs. The seller's public identity, including this domain, is also announced on the AntSeed network under our peer id and at /.well-known/antseed.json.