The SmartCodedBot studio token on Base. This page describes what is deployed, not what is intended. Every number here can be checked against the contracts.
A plain ERC20 on Base with a fixed supply of 100,000,000,000, minted once in the constructor. It is the studio token: the thing the studio's products point at, and the asset holders of the previous token are carried into.
The contract exposes nine functions, all of them standard: name, symbol, decimals, totalSupply, balanceOf, transfer, transferFrom, approve and allowance. There is nothing else in it.
| Share | Purpose | Tokens |
|---|---|---|
| 74% | Liquidity, single sided range | 74,000,000,000 |
| 16% | Claim for recorded holders | 16,000,000,000 |
| 4% | Development | 4,000,000,000 |
| 2% | Partnerships | 2,000,000,000 |
| 2% | Community | 2,000,000,000 |
| 2% | Listings and market making | 2,000,000,000 |
The claim pool holds 16,000,000,000 against 15,540,540,378 of recorded entitlement, so 459,459,622 is surplus. That surplus, and anything left unclaimed, goes to a sweep address fixed at deployment once the window closes.
Every eligible wallet and its amount were committed to a Merkle root before the contract was deployed. The root is immutable, so no allocation can be added, changed or removed after the fact.
To claim, a wallet proves its leaf and hands over the same amount of the old token. The contract then sends the same amount of VISOR back. The exchange is one for one and capped at the recorded amount, so a valid proof cannot take more than it was issued.
Partial claims are allowed and accumulate. The window closes on 20 September 2026 at 14:42 UTC, after which claiming reverts and sweeping opens.
8,000,000,000, being the development, partnerships and community shares, sits in a vesting contract. It releases nothing for 90 days, then streams linearly over the following 270, finishing twelve months from deployment.
The schedule is set once at deployment. It cannot be paused, revoked or moved, by the studio or anyone else. Release is callable by anyone, but the tokens can only ever be sent to the beneficiary fixed at deployment.
The remaining 2,000,000,000, for listings and market making, is liquid today and held in its own wallet so it can be watched separately.
What the studio can do: spend the liquid listings share, and receive the vested shares on the schedule above. Both are visible on chain.
$SMART was deployed through a launchpad, and its owner is that launchpad's own Safe. That Safe holds the inflation switch and the pool lock, so the studio could not renounce ownership, change the fees or lock liquidity. Roughly 84% of its supply sits in a pool that cannot be switched off, which is why it still trades and always will.
Rebuilding produced a token with no owner and a fixed supply. Nothing is taken from holders of the old one: the exchange is voluntary, initiated by the holder, at a rate that cannot be altered.
| Token | 0xB095E46785b8e90aa29Ed7a3548F68F61dec0dEd |
| Claim | 0x3960D82C74e2A63aB07649CaAF6A7Aa277b4A422 |
| Vesting | 0x271d74D6b76760e3460Da77FEFE68DBfbc96336c |
| Liquid treasury | 0x619Cf552863231CDc66c07A3e65396e5E37C0deD |
| Old token | 0xB623b95571087447f6B45a966f8720b1F196DbA3 |
All three new contracts are verified as an exact match between the published source and the bytecode on chain, creation and runtime. The full Merkle tree is published at smartcodedbot.com/snapshot/api/tree, so you can rebuild your own proof and check the root rather than trusting any page.