STBU migration is in progress: claim your STBU on Base
Why STBU moved to one contract on Base, how the exploit that pushed the legacy supply past plan was closed, what the 216,563,456 issuance is made of, and how every kind of holder claims before 31 December 2026.
- 31 December 2026, 23:59 UTC
- Claims close. The date does not move.
- 15 December 2026
- Last day for Stobox 4 holders without keys to send a request.
- stbu.stobox.io
- See what your wallet can claim before you sign anything.
STBU now lives on one network, under one contract, with one public record of every token that exists. The burn window closed on 15 September 2026. What is open now is the part that matters to you: claiming the STBU you are entitled to on Base.
This article tells the whole story in one place, and the questions we expect from you are answered at the end.
Where STBU came from
Stobox has built tokenization infrastructure since 2018. STBU is the utility token of that ecosystem. Over the years it came to live on four blockchains: Ethereum, BNB Chain, Polygon and Arbitrum. Each had its own token contract, 277,940,689 STBU in total. In this article we call that old token legacy STBU.
Four contracts meant four versions of the truth. Supply was counted differently depending on where you looked, price aggregators showed different figures for the same asset, and moving STBU between networks meant bridges, each one more contract to trust.
A second problem sat inside our own product. Stobox 4, our earlier platform, held tokens for many users in custodial wallets. The users saw a balance, but the keys were ours. That made the platform simple to use and made self-custody impossible. Stobox 4 closed on 18 June 2026.
The third problem was the worst one. STBU was planned with a total supply of 250,000,000. An exploit created legacy tokens above that plan, and the legacy supply reached 277,940,689 STBU: 27,940,689 more than there should ever have been. For holders that meant dilution nobody agreed to. For Stobox it was a disaster, and we say so plainly.
By mid-2026 the conclusion was plain. STBU needed one network, one contract, a supply anyone can check, and tokens held by the people who own them.
The exploit, and how the migration closes it
We could not delete tokens from contracts on four networks. What we could do was decide which tokens move forward.
First, we contained it. The wallets that received the exploited tokens were identified and blocked on the centralised exchanges where they arrived, so those tokens could not be sold or withdrawn there.
Then, we migrated. A burn-and-mint migration gives a fresh start by design: only tokens that were burned by their holders inside the window, plus a small number of closed and disclosed categories, exist on Base. Tokens that were not burned, including the exploited ones, stay on the old contracts, and those contracts are discontinued.
The result in one subtraction.
| STBU | |
|---|---|
| Legacy supply on four networks | 277,940,689 |
| Issuance on Base | 216,563,456 |
| Difference | 61,377,233 |
277,940,689
216,563,456 · 61,377,233 smaller
- Burned and credited
- Stobox 4, lost access, late burns
- Development and liquidity
- Team and STO Foundation
- Burned before the window
- Not burned, including the exploited tokens
The STBU issuance on Base is 61,377,233 STBU smaller than the legacy supply. That difference is what was left behind, and it includes the tokens created by the exploit. None of it becomes STBU on Base, and none of it can be used in the Stobox ecosystem again.
Why we migrated, and why Base
We chose a burn-and-mint migration to Base. In plain words: you destroy (burn) your old tokens, and the same amount of new tokens is created (minted) for you on Base, one for one.
- Ethereumlegacy · 100.00M
- BNB Chainlegacy · 25.00M
- Polygonlegacy · 25.00M
- Arbitrumlegacy · 127.94M
One network. Every STBU now exists on Base, under the contract 0xe0c0F44A84CC4a60206360006ebA237a5e8fC2dd. No token at any other address is STBU.
A supply you can read. The token contract has a hard cap of 250,000,000 written as a constant, no proxy and no upgrade path. How many STBU exist at any moment is totalSupply() on that contract, not a number we publish.
No bridge. Holders burned the legacy token on the network where they held it, and the same wallet claims the new token on Base. Nothing depends on a bridge.
Self-custody. A claim goes to a wallet you control. For Stobox 4 holders who never had the keys, the migration is the moment they get them.
Why Base. Base is where Stobox is building. Our uRWA factory, the infrastructure for issuing tokenized real-world assets, is being built on Base, and so is the Stobox Terminal for tokenized stocks. STBU belongs on the same network as the products it is used in. Base also has low fees, so a claim costs a holder cents rather than dollars, and it is widely supported by wallets.
How the migration worked
The migration ran in two phases.
Phase 1: burn. The token and claim contracts were deployed on Base and verified on 19 July 2026, and the portal at stbu.stobox.io opened. From then until 15 September 2026 at 00:00 UTC, holders sent legacy STBU to the burn address 0x000000000000000000000000000000000000dEaD on Ethereum, BNB Chain, Polygon or Arbitrum. Our indexer, the system that reads the blockchain, recorded each burn and credited it one for one to the wallet that burned.
Phase 2: claim. Each credited wallet claims its STBU on Base. The claim contract mints the credited amount to that wallet, and only to it. Claims opened on 16 September 2026 at 11:12 UTC. Claims close on 31 December 2026 at 23:59 UTC.
The result of the burn phase. 172,793,359 STBU was burned in time and credited to 321 wallets. 92,669,716 legacy STBU, about a third of the legacy supply, was not burned before the close. That part is discontinued: it does not migrate, and it does not become STBU on Base.
Some holders could not burn in time for reasons that were not theirs. Those cases are handled as closed categories, described below, and each is disclosed.
- Stobox 4 closes
- Contracts deployed on Base, portal opens, burn window starts
- Burn window closes
- Cut-off for the six late burns
- Claims open
- Team tranches
- Last day for Stobox 4 requests
- Claims close
- Minting right withdrawn
The issuance
The issuance is the total amount of STBU that can exist on Base once everyone has claimed. The contract cap is 250,000,000 STBU. The issuance Stobox Innovations has determined is 216,563,456 STBU; raising it would need a resolution published 30 days before any mint relies on it, and minting is switched off for good immediately after claims close on 31 December 2026.
The difference between the cap and the issuance, 33,436,544 STBU, is not an allocation to anyone. It is headroom in the contract that is not issued.
| Group | Wallets | STBU | Share |
|---|---|---|---|
| Holders | 404 | 181,063,456 | 83.61% |
| Stobox Terminal Development Allocation & Liquidity | 2 | 28,500,000 | 13.16% |
| Team | 6 | 6,000,000 | 2.77% |
| STO Foundation | 1 | 1,000,000 | 0.46% |
| Issuance | 413 | 216,563,456 | 100% |
Shares are of the issuance, never of the 250,000,000 cap.
Holders, 181,063,456 across 404 wallets. This is almost everything. The main parts:
- 172,793,359 burned in time and credited one for one to 321 wallets;
- 3,002,580 for 71 wallets whose balances sat in closed Stobox 4 accounts they never had the keys to;
- 699,580 for 4 wallets of holders who lost access to their legacy STBU, verified by hand on 15 September 2026, a closed category;
- 4,566,827 for 6 wallets whose burns the chain confirmed after the close, up to one cut-off transaction, a closed category.
Holders · 181,063,456 STBU · 404 wallets
- Burned and credited172,793,359 STBU · 321 wallets · 95.4%
- Stobox 4 without keys3,002,580 STBU · 71 wallets · 1.7%
- Lost access, verified by hand699,580 STBU · 4 wallets · 0.4%
- Late burns to the cut-off4,566,827 STBU · 6 wallets · 2.5%
Stobox Terminal Development Allocation & Liquidity, 28,500,000. 3,500,000, one development wallet, pays for building what this token runs on: the migration contracts, the claim portal and the Stobox Terminal, including the technical team and liquidity inside that product. 20,000,000 goes into the STBU liquidity pool that is being set up now. 5,000,000 is a reserve that is not sold; it is kept for future pools. The liquidity and the reserve are held in one Stobox Innovations Safe.
Team, 6,000,000. Six members of the team receive 1,000,000 each as payment for their work.
STO Foundation, 1,000,000. An industry body of which Stobox is a member, for marketing services and as a grant.
How allocations are delivered. Only the team is paid in tranches: three equal parts on 16 September, 15 November and 31 December 2026. The development allocation and the STO Foundation are each paid in one allocation. After that, minting stops.
What will be minted. The final supply is whatever is minted by the close. It will be below 216,563,456, because anything unclaimed on 31 December 2026 is never minted and goes to no one.
How to claim, by kind of holder
Start at stbu.stobox.io in every case. The portal shows what your wallet is entitled to before you sign anything.
You burned legacy STBU in time. Connect the same wallet you burned from, sign in, and claim. The claim is one transaction on Base, and you pay the network fee (gas) in ETH on Base from that wallet. The STBU arrives in that wallet.
You held STBU in a closed Stobox 4 account. You never had the keys, so you could not burn. Sign in at stbu.stobox.io with the email address you used on Stobox 4. The portal shows your Stobox 4 record and balance. Connect a new self-custody wallet, sign, and request your balance to it. We review the request, and once it is approved you claim to that wallet like everyone else. Send the request by 15 December 2026. A later request is still reviewed, but we cannot promise it is approved and claimed before claims close. If you no longer have access to that email address, write to support@stobox.io with "Stobox 4" in the subject.
You are one of the four holders verified by hand, or one of the six late burners. Those allocations are already recorded. Sign in with the wallet named for you and claim.
You burned in time, but no balance shows. Write to support@stobox.io with the burn transaction hash. A burn the chain confirmed inside the window is credited whether or not our indexer saw it in time, and we answer within 5 business days.
Your wallet shows "under review". We are reviewing these wallets and will come back to each holder. You do not need to send anything, pay anything or burn anything.
You did not burn in time. Your legacy STBU is discontinued. It stays in your wallet and stays yours, but it does not migrate, and there is no buy-back, exchange or compensation. The details are at stbu.stobox.io/legacy.
Your wallet is a Safe or another contract wallet. A contract wallet can claim once the portal supports its signature type, which is announced at stbu.stobox.io. Until then your credit is safe and is not lost.
Gas. You need a small amount of ETH on Base in the claiming wallet. You can bridge ETH to Base, or withdraw ETH from an exchange choosing the Base network. ETH on Ethereum or Arbitrum does not work for a Base transaction.
What happens when you press Claim
A claim has three steps, and you can follow each of them.
- 1. Sign a messagefree, moves nothing
- 2. Claim ticketyour address, your amount, expires
- 3. One transaction on Baseyou pay the gas in ETH
- 4. STBU minted to your walletevery check passes, or nothing is minted
1. You sign in. You sign a message with your wallet. A signature is not a transaction: it costs nothing, moves nothing and gives nobody access to your funds. It only proves that you control the address.
2. The portal issues a claim ticket. The ticket is a signed statement that says one thing: this address may receive this amount of STBU. The amount comes from our records of your burn or your allocation, never from anything sent in the request, and the ticket is only valid for a short time and only for your address.
3. You send one transaction on Base. Your wallet submits the ticket to MigrationClaim. The contract checks that the ticket was signed by the registered ticket signer, that it is for your address, and that the amount has not already been claimed. Then it mints the STBU to your wallet. If any check fails, nothing is minted.
The claim then appears in the public claims registry. If your wallet does not show STBU, add the token with the address 0xe0c0F44A84CC4a60206360006ebA237a5e8fC2dd.
How much safer this is, in plain words
The new setup was built so that what happened to the legacy token cannot happen quietly again. Here is what changed, without the jargon.
| Legacy STBU | STBU on Base | |
|---|---|---|
| Networks | Four, with four contracts | One: Base |
| Supply | 277.94M, above plan after an exploit | Hard cap 250M in code, issuance 216.56M |
| Who can create tokens | Four contracts to watch | One contract, only with a signed ticket |
| Keys | Custodial wallets on Stobox 4 | Your own wallet |
| Checks | Different numbers in different places | Recount every 5 minutes, public registry |
| End of minting | Open-ended | Withdrawn right after 31 Dec 2026 |
A hard ceiling written into the token. The token contract can never hold more than 250,000,000 STBU. That number is written into the code as a constant, and the contract cannot be upgraded or replaced. Think of a jar with a fixed size: whatever happens, it cannot overflow.
Only one door can create tokens. New STBU can only come out of one contract, MigrationClaim. No person and no ordinary wallet can mint. Think of a building with a single entrance and no windows.
The door opens only with a signed ticket. MigrationClaim mints only when it is shown a claim ticket signed by the registered ticket signer, made out to one specific wallet, for one specific amount, and valid for a short time. Think of a cheque that names you, states the amount, and expires.
The signing key cannot be copied. The key that signs tickets lives in hardware-backed key management. It can sign, but it cannot be exported or read out, not even by us. Think of a stamp locked inside a machine: you can press the button, you cannot take the stamp home.
The amount comes from our records, not from the request. Nobody can ask for more than they are owed.
Administration is not one ordinary wallet. The contracts are administered by a Safe multisig: a shared account designed to be controlled by several keys rather than one. Every allocation also needs one person to prepare it and a different account to approve it.
Someone is always counting. An automatic checker is built to recalculate every wallet's entitlement every five minutes, and a watchdog to pause claims within 30 seconds if the numbers do not add up. Separately, an independent monitor checks every mint on Base against the wallet's recorded entitlement every 15 minutes. Think of a till built to be recounted every few minutes and locked the moment it is short.
Everything is visible. Every claim is a public transaction on Base. A token that should not exist would show on chain.
- Hard cap in codethe jar cannot overflow
- One minting contracta single door
- Signed, expiring ticketsa cheque with your name
- A key that cannot be copieda stamp locked in a machine
- Amounts from our recordsnobody asks for more
- Safe multisig administrationnot one ordinary wallet
- Recount every 5 minutesautomatic pause in 30 seconds
- Public record on Baseanyone can check
- An end dateminting withdrawn after 31 Dec 2026
There is an end date. Right after claims close on 31 December 2026, the right to mint is withdrawn in a published transaction. After that, no new STBU can be created at all.
Stay safe
Nobody can claim for you, speed up a claim, or reopen the migration. Stobox never asks for a payment, a seed phrase or a private key, never asks you to send tokens anywhere, and never messages you first. We write only from addresses ending in @stobox.io. The only portal is stbu.stobox.io.
The new infrastructure
These are the addresses that matter. Check them on BaseScan rather than trusting a screenshot.
| What | Network | Address |
|---|---|---|
| STBU token | Base | 0xe0c0F44A84CC4a60206360006ebA237a5e8fC2dd |
| MigrationClaim, the only contract that can mint STBU | Base | 0xec5B3e512de13cb5DdFD84B2DF3167230F2e66a4 |
| Administrator of both contracts, Safe multisig | Base | 0xDD7B82eBD733458220B90c1f98Cc7EBFd1cb4372 |
| Stobox Innovations, liquidity and reserve, Safe multisig | Base | 0x965D14652aDbe41Ed024bf71A26487Bf3EF9972B |
| Claim ticket signer, registered on MigrationClaim | Base | 0x54eDD7F4d9027665d7E52eD622478Ab395C4D99E |
| Burn address used by the migration | all legacy networks | 0x000000000000000000000000000000000000dEaD |
| Legacy STBU, discontinued | Ethereum | 0xa6422e3e219ee6d4c1b18895275fe43556fd50ed |
| Legacy STBU, discontinued | BNB Chain | 0xb0c4080a8fa7afa11a09473f3be14d44af3f8743 |
| Legacy STBU, discontinued | Polygon | 0xcf403036bc139d30080d2cf0f5b48066f98191bb |
| Legacy STBU, discontinued | Arbitrum | 0x1cb9bd2c6e7f4a7de3778547d46c8d4c22abc093 |
The contracts were deployed at block 48830559 on Base, and their source is verified on BaseScan. To check the supply yourself, call totalSupply() and MAX_SUPPLY() on the token contract. Every claim appears in the claims registry at stbu.stobox.io/transparency with its transaction hash.
What comes next
The migration is the first of three chapters.
- Chapter 1 · nowClaimsUntil 31 December 2026
- Chapter 2DEX tradingAnnounced when live
- Chapter 3Stobox TerminalTokenized stocks and real-world assets on Base
Chapter 1: claims. This is now. Every eligible holder claims on Base until 31 December 2026. The claims registry shows how much has been claimed, not how much was burned, and it grows with every claim.
Chapter 2: DEX trading. STBU will trade on a decentralised exchange on Base, starting with the pool funded from the liquidity allocation. We will announce it when it is live, with the pool address and how to check it, in its own article.
Chapter 3: the Stobox Terminal. The Terminal is the product STBU is built for: one place to trade STBU, tokenized equities and other real-world assets. What STBU gives access to inside the Terminal will be published with the Terminal itself, together with its terms.
The vision behind all three is the one Stobox has worked toward since 2018: real-world assets and the tokens around them should be as simple to hold and as easy to verify as any other digital asset, with every number checkable on chain rather than taken on trust.
Questions and answers
Short answers. The binding text is the STBU Token Terms at stbu.stobox.io/token-terms.
Supply and minting
1Who can mint STBU?
No person or wallet mints STBU directly. The only contract that can mint is MigrationClaim, and it mints only against a verified claim ticket issued for an eligible wallet, to that same wallet. To see what your wallet is eligible for, go to stbu.stobox.io.
2Who controls the contracts?
Both contracts are administered by a Safe multisig at 0xDD7B82eBD733458220B90c1f98Cc7EBFd1cb4372. The administrator can pause, manage the claim ticket signer and close minting. The token contract has no function that moves STBU out of your wallet, freezes your address or changes your balance.
3Can my tokens be frozen?
Not individually. There is no per-address freeze, blacklist or clawback in the token. There is one emergency pause that stops every wallet at once, for a defect or a compromised key, and any pause is announced at stbu.stobox.io with its reason.
4The cap is 250,000,000, the issuance is 216,563,456. Can that change?
The contract cap is 250,000,000 STBU. The issuance Stobox Innovations has determined is 216,563,456 STBU; raising it would need a resolution published 30 days before any mint relies on it, and minting is switched off for good immediately after claims close on 31 December 2026.
5What stops you from issuing more before 31 December?
Every allocation needs one person to prepare it and a different account to approve it, every mint is public on Base within minutes, and any mint above the issuance needs 30 days of published notice first. Right after claims close, the minting right is withdrawn in a published transaction.
Allocations
6Why does the team get 6,000,000 STBU when holders paid for theirs?
Holders paid for STBU in earlier versions of the token. The team allocation is payment for work: six people, 1,000,000 each, 2.77% of the issuance, with no buy-back and no price guarantee.
7What is the 3,500,000 development allocation for?
Building what STBU runs on: the migration contracts, the claim portal and the Stobox Terminal, including the technical team and liquidity inside that product. It is 1.62% of the issuance and is paid in one allocation.
8What is the 25,000,000 for liquidity?
20,000,000 goes into the STBU liquidity pool that is being set up now. 5,000,000 is a reserve that is not sold; it is kept for future pools. Both are held by Stobox Innovations at 0x965D14652aDbe41Ed024bf71A26487Bf3EF9972B. Trading details come with the DEX chapter.
9Can the team sell right away?
There is no lockup. The team receives its STBU in three equal tranches on 16 September, 15 November and 31 December 2026; the development allocation and the STO Foundation are paid in one allocation each. After that, minting stops.
10How does Stobox earn from STBU?
Nothing is paid to Stobox for a claim, ever. The commercial terms of the liquidity pool are not public. What STBU gives access to in the Stobox Terminal will be published together with the Terminal.
Claims and deadlines
11The burn window closed at 00:00 UTC on 15 September. Why were later burns credited?
Six wallets burned on 15 September, after the close, and Stobox credited them one for one as a correction, shown on their own line. The cut-off is one transaction, 0xe2ca5dcf6b91d0b375e636420e9283ded82e30c134eb2e3c023c006815ea2fb6 on BNB Chain at 11:27:36 UTC. Nothing burned after it is credited, and the category is closed.
12Who decides what counts as lost access?
For Stobox 4 it is a chain reading, not a judgement: the custodial wallet has not moved since the platform closed on 18 June 2026. That covers 71 holders. Four more holders who lost access to their legacy STBU were verified by hand on 15 September 2026, and that category is closed.
13How do I know the Stobox 4 wallets are real people?
Every Stobox 4 wallet is a legacy address you can check on chain, and its balance has not moved since the platform closed. Names and emails are never published.
14Why did Stobox hold other people's keys?
Stobox 4 was a custodial platform. It closed on 18 June 2026, and the migration moves those balances into wallets their owners control.
15My wallet says "under review". What does that mean?
We are reviewing these wallets and will come back to each holder. You do not need to send anything, pay anything or burn anything.
16What if the indexer missed my burn?
If the chain confirmed your burn inside the window, it is credited. Write to support@stobox.io with the transaction hash, and we answer within 5 business days.
17An earlier draft said claims stay open for twelve months. Which is it?
That draft was never published. The published deadline is 31 December 2026, 23:59 UTC, and it is final.
18What happens if I miss 31 December?
Your unclaimed balance is never minted. It does not go to Stobox, to a treasury or to anyone else. There is no extension and no late claim.
19The deadline is not written in the contract. What stops you from moving it?
The published Token Terms: the date does not move, earlier or later, for anyone. Right after the close, the minting right is withdrawn in a public transaction, and after that nothing can be minted at all.
20What happens to legacy STBU that I did not burn?
It is discontinued. It stays in your wallet and stays yours, but it does not migrate, and there is no buy-back, exchange or compensation. Stobox does not support it anywhere. The one exception is a balance in a closed Stobox 4 account: request it by 15 December 2026.
Cost, access and trading
21Who pays the gas?
You do. A claim is one transaction on Base, paid in a small amount of ETH on Base from the claiming wallet. Nothing is paid to Stobox, and nobody will ever ask you for a payment to unlock a claim.
22Where can I trade STBU?
DEX trading on Base is the next chapter, and we will announce it when it is live. We have no centralised exchange plans at this time. Any market in the legacy token is not ours.
23My wallet is a Safe. Can it claim?
A contract wallet can claim once the portal supports its signature type, which is announced at stbu.stobox.io. Until then the credit stays on your address and is not lost.
Security and trust
24Were the contracts audited?
There is no independent third-party audit. The contracts were reviewed internally, including by AI agentic analysis software, and checked against the chain: verified source matching the deployed code, a hard cap, no upgrade path, no owner or admin mint, roles matching the published ones, and the claim path tested on a copy of the network.
25What protects the claim system from being hacked?
A capped token, one minting contract, signed tickets from a key that cannot be exported, a multisig administrator, a recount designed to run every five minutes with an automatic pause, and a public record of every claim. Each layer is explained in plain words in the article.
26What if your portal goes down before 31 December?
A claim needs a ticket from our system, so while the portal is down, claiming stops. Outages are published at stbu.stobox.io. The deadline does not move, so claim early rather than in the last week.
27Your numbers disagree with each other. Which one is right?
The live figure, read from the chain and timestamped. Published figures carry the date they were fixed. Where the two differ, the difference is explained at stbu.stobox.io/transparency.
28Why trust a transparency page you write yourselves?
You do not have to. Every claim is a mint on Base with a transaction hash you can open on BaseScan, and the total minted is totalSupply() on the token contract.
Documents and links
- stbu.stobox.ioClaim portal
- STBU token on BaseScanContract, supply, holders
- MigrationClaim on BaseScanThe only minting contract
- STBU on stobox.ioWhat the token is for
- One STBU, One ChainThe July announcement of the migration
- STBU Token Terms, supply statement, legacy noticePublished at stbu.stobox.io
- support@stobox.ioQuestions
