One page, published at stbu.stobox.io/supply. Everything an exchange, an aggregator or a holder asks about the number of STBU, with the on-chain call that proves each line. Nothing here is a forecast.
As at 16 September 2026. The figures below are final in the sense that the categories are closed: the burn window is shut and no new category of issuance exists. What is still moving is how much of the issuance has actually been minted, and that is read from the chain, not from this page.
1 · The token
| Field | Value |
|---|---|
| Name, symbol | Stobox Utility Token, STBU |
| Network | Base (chain id 8453) |
| Contract | 0xe0c0F44A84CC4a60206360006ebA237a5e8fC2dd |
| Standard, decimals | ERC-20, 18 |
| Deployed, verified | 19 July 2026, source verified on BaseScan |
| Only minter | MigrationClaim 0xec5B3e512de13cb5DdFD84B2DF3167230F2e66a4 |
| Administrator | Safe 0xDD7B82eBD733458220B90c1f98Cc7EBFd1cb4372 |
Token details.
No token at any other address is STBU. The four legacy contracts listed in section 4 are discontinued.
2 · Cap, issuance, minted
| Figure | STBU | How to check it |
|---|---|---|
| Contract cap, immutable | 250,000,000 | MAX_SUPPLY() on the token contract |
| Issuance determined and published | 216,563,456 | Token Terms section 4; resolution RES-INNO-2026-003 |
| Minted so far | read live | totalSupply() on the token contract |
| Headroom below the cap, reachable only after 30 days public notice | 33,436,544 | cap less issuance |
Cap, issuance and minted supply.
The cap is a limit written in the contract. 216,563,456 is not a second cap: it is the issuance the issuer has determined by resolution and publishes, and the issuer keeps the legal right to issue up to the contract cap. What protects you is notice rather than a promise. No STBU is minted above 216,563,456 unless a resolution setting a new figure has been published at stbu.stobox.io at least 30 days before the first such mint, and section 12 of the Token Terms forbids any later version from removing that notice.
3 · What makes up the issuance
| Group | Recipients | STBU | Share of issuance | What it is |
|---|---|---|---|---|
| Holders | – | 181,062,346 | 83.61% | burns credited one for one to 321 wallets (172,793,359), closed Stobox 4 balances restored to 71 holders on proof of a new address (3,002,580), four named holders who lost access to their legacy STBU, verified by hand on 15 September 2026 (699,580), burns confirmed after the close of the window and up to the cut-off transaction 0xe2ca5dcf6b91d0b375e636420e9283ded82e30c134eb2e3c023c006815ea2fb6 on BNB Chain, confirmed at 11:27:36 UTC on 15 September 2026, to 6 wallets (4,566,827) |
| Stobox Terminal Development Allocation and Liquidity | 2 | 28,500,000 | 13.16% | 3,500,000 to the development wallet for building the migration contracts, the portal and the Terminal, held by that wallet and not by the issuer, in one allocation; 20,000,000 in five positions of the STBU/USDC pool on Uniswap v4 on Base and 5,000,000 in reserve outside the pool, both held by the issuer |
| Team | 6 | 6,000,000 | 2.77% | six members of the team, 1,000,000 each, as payment for services; no lock up, three equal tranches on 16 September, 15 November and 31 December 2026 |
| STO Foundation | 1 | 1,000,000 | 0.46% | an industry body of which Stobox is a member, for marketing services and as a grant, in one allocation |
| A test allocation and one duplicate | 2 | 1,110 | 0.00% | disclosed at stbu.stobox.io/transparency: 1,000 minted as a test of the claim path and 110 issued twice by a duplicated record |
| Issuance | 216,563,456 | 100% | shares are of the issuance, never of the 250,000,000 cap |
Issuance by group.
43,770,097 STBU of the issuance, being everything above the migrated burns, is minted without a matching burn. The Token Terms call that an allocation and section 7 governs it.
4 · The legacy token, and why the numbers do not add up to it
| Network | Legacy contract | Legacy supply | Burned in time |
|---|---|---|---|
| Ethereum | 0xa6422e3e219ee6d4c1b18895275fe43556fd50ed | 100,000,000 | 46,342,575 |
| BNB Chain | 0xb0c4080a8fa7afa11a09473f3be14d44af3f8743 | 25,000,000 | 15,500,633 |
| Polygon | 0xcf403036bc139d30080d2cf0f5b48066f98191bb | 25,000,000 | 7,782,806 |
| Arbitrum | 0x1cb9bd2c6e7f4a7de3778547d46c8d4c22abc093 | 127,940,689 | 103,172,725 |
| Total | 277,940,689 | 172,798,739 |
Scroll the table sideways to read the full contract addresses.
Of the burned total, 172,793,359 STBU is credited to 321 wallets; the difference of 5,380 STBU is burns the record does not match to a claimable address.
The legacy supply of 277,940,689 STBU divides into three parts and only three: 172,798,739 burned inside the migration window, 12,472,233 sent to the burn address before the window opened, and 92,669,716 still held in holders' wallets, a third of the legacy supply, not burned before the close. That last part stays where it is, on the network where it is, and it does not become STBU on Base. It is not counted in the issuance, it is not counted in any supply figure for STBU, and the issuer neither supports it nor can act on it. The four legacy contracts are discontinued and should be removed from any STBU listing.
The burn address 0x000000000000000000000000000000000000dEaD holds 185,270,973 legacy STBU. Of that, 172,798,739 was burned inside the migration window and 12,472,233 was sent to the burn address on Ethereum and BNB Chain before the window opened; those earlier transfers are not migration burns and were never eligible. The balance of the burn address is therefore 12,477,614 higher than the 172,793,359 credited to wallets, which is those earlier transfers plus the 5,380 the record does not match to a claimable address. Polygon and Arbitrum reconcile to the wei.
Every figure on this page is the whole-token amount, rounded down from the wei-exact balance on chain, so a row can differ by one STBU from the difference of two other rows. The wei-exact figures for all four networks are published at stbu.stobox.io/transparency.
5 · Circulating supply
Circulating supply is minted supply less the balances below. Read each from the chain rather than from this page.
| Address | What | Circulating |
|---|---|---|
| 0x965D14652aDbe41Ed024bf71A26487Bf3EF9972B | issuer’s account: 5,000,000 reserve outside the pool | no |
| the same account’s Uniswap v4 positions | 20,000,000 supplied as liquidity | yes, by aggregator convention, though it is issuer-owned |
| the development wallet and the team addresses, published when each is known | 3,500,000 and 6,000,000, the team’s in three tranches | no until delivered, then yes |
| credited balances not yet claimed | not minted at all | not part of any supply figure |
Balances and circulating supply.
A credited balance that has not been claimed does not exist as a token: nothing is minted for it until the holder claims. That is why totalSupply() on Base was zero until claims opened and grows with every claim.
6 · What can still change the number, and what cannot
Can: how much of the issuance is actually minted, because claims run until 31 December 2026 and unclaimed balances are never minted. After that day, nothing at all.
Cannot: the cap, which is immutable; the categories, which are closed; the issuance figure without 30 days of public notice first; the legacy supply, which no longer migrates. Neither the issuer nor anyone else can mint STBU outside the MigrationClaim contract, and on the close of distribution its right to mint is withdrawn and never granted again. That transaction is published at stbu.stobox.io/transparency.
Questions on supply: legal@stobox.io.
Stobox Innovations Limited · No. 2098354 · Commerce House, Wickhams Cay 1, P.O. Box 2283, Road Town, Tortola, British Virgin Islands, VG1110 · registered agent ABM Corporate Services Ltd · legal@stobox.io