STBU · before you trade
Only one pool is ours. The others will not warn you.
Within minutes of our pool opening on 16 September 2026, other people created pools on Base carrying the STBU name. We did not create them and we do not operate them. The important part is that they do not fail with an error: a swap there completes normally, and you keep a small fraction of what you paid. This page is how you avoid that in three checks.
Our pool holds $52,588. The others hold $11.04 between them, which is roughly 4,761 times less. A pool can only pay you what it holds, so a hundred dollar trade in one of them is almost entirely your own money moving the price against you.
Nothing about those pools is broken. They carry very high fees and hold almost nothing, and together that means a trade there is mostly loss. A trade is as final as a burn. Read from the chain 2026-09-25 08:52 UTC and rewritten every day.
The link
One link, both addresses already filled in.
Most of what goes wrong starts with searching by ticker instead of opening the pair directly.
This link opens the correct pair with the network and the contract address already filled in. It is the shortest way to be in the right place.
Trade STBU on BaseSTBU · 0xe0c0F44A84CC4a60206360006ebA237a5e8fC2dd
Pool · 0x28bd1d1afcc57d766c5d1c5c38bd8beb376a0c98de719460cdcef60900f7b8b5
Three checks before you confirm
They take ten seconds and they catch every case on this page.
Do them in this order. The third one alone would have prevented every loss we have seen so far.
The network says Base.
Not Ethereum, not BNB Chain, not Polygon, not Arbitrum. The contracts on those four chains were discontinued on 15 September 2026. They still display a price in some interfaces, but that market is closed and nothing you buy there can be migrated.
The contract address is exactly this.
0xe0c0F44A84CC4a60206360006ebA237a5e8fC2dd. Compare the whole string, not the first four characters. Anyone can deploy a token called STBU.The amount you receive looks sensible.
This is the check that catches everything else. At the price read for our pool today, 100 USDC should offer you roughly 42,564 STBU. If a screen offers you a small fraction of that, you are in a pool that is not ours. Stop and use the link above.
The pools that carry our name
Only the first row is ours.
Rebuilt from the chain every day, so this list follows whoever creates the next one. A pool with no trades yet may not appear until it has some, which is another reason to check the address rather than the table.
| Pool id | Pair and fee | Liquidity | Price it quotes |
|---|---|---|---|
0x28bd1d1afcc57d766c5d1c5c38bd8beb376a0c98de719460cdcef60900f7b8b5 | STBU / USDC · ours | $52,588 | $0.00234938 |
0xce10470fc34016a6af4a0213a8e2f20b5681106ff43676be6a072f1426285160 | STBU / ETH 20% | $11.04 | $0.00084792 |
0xc907daa1c714720d1967faf508685d175544faef2e3e194cbaf158cd8819e984 | STBU / USDC 15% | $0. | $0.01004387 |
A pool is identified by its id, not by the ticker printed next to it. The first row is ours. The rest were created by third parties and appear here so you can recognise them, not so you can find them.
Compare the last two columns rather than the names. A pool quoting a price several times away from the first row, on a few dollars of depth, is not a market. The fee is charged on top of that.
This table is rebuilt from the chain every day. If someone creates another pool tomorrow, it appears here without anybody editing this page.
If your trade is rejected
That is usually the pool's depth, not a fault.
Worth understanding rather than retrying, because retrying does not help.
If a larger purchase is rejected, that is usually not a fault and not an attack. Our pool is young, so a trade moves its price, and the bigger the trade the more it moves. When that move is larger than the slippage tolerance, the interface refuses rather than filling you at a worse price. That refusal is the interface protecting you.
The tolerance is set by the interface, not by us. Uniswap sets it to Auto and prints the figure right above the confirm button, and it chooses a wider tolerance for a young pool than for a deep one. Read the number it shows you rather than assuming one.
The depth of the pool is on this page, in the row marked as ours. The larger your order is relative to that number, the more the price moves against you.
As a sense of scale at the depth read today, an order of about 650 USD moves the price roughly half a percent. An order several times that size will usually still go through, because the tolerance the interface picks is wider than that, but you pay the price impact either way. This figure is recomputed here every day, so it follows the pool rather than staying where it was written.
Two ways through if a trade is refused, both normal. Raise the tolerance in the interface's settings, which means accepting the worse price you are shown. Or buy in smaller amounts, which costs less in price impact overall.
The discontinued contracts
Names that look newer, and are not.
The names are written into those contracts and cannot be changed.
Searching for STBU by name may show you Stobox Token v.2 or Stobox Token v.3. Those names are written into the old contracts themselves and cannot be changed by anyone, including us. They look newer than the live token, which is named simply Stobox Token. They are not.
The four discontinued contracts, shown here so they can be recognised:
Ethereum · 0xa6422e3e219ee6d4c1b18895275fe43556fd50ed
BNB Chain · 0xb0c4080a8fa7afa11a09473f3be14d44af3f8743
Polygon · 0xcf403036bc139d30080d2cf0f5b48066f98191bb
Arbitrum · 0x1cb9bd2c6e7f4a7de3778547d46c8d4c22abc093
Buying any of those gets you a token that was switched off on 15 September 2026. It cannot be migrated and it is not the asset this site describes.
When a price site disagrees with this page
Judge by the contract address, not by the name at the top.
Records move between these sites by copying, so one out of date copy can surface in several places at once.
Price sites, portfolio trackers and wallets each keep their own record of a token, and several of them still hold the record of the legacy STBU rather than the one on Base. From the outside that looks like a discontinued contract address, a price or a market capitalisation of zero, an old logo, a description of products that no longer exist, or a note left over from before the migration.
None of that is a statement about the token on Base. It is a record that has not been updated yet, and those records are often copied between sites, so one stale copy can appear in several places at once.
One test settles it, and it does not go stale. Find the contract
address on the page you are reading. If it is
0xe0c0F44A84CC4a60206360006ebA237a5e8fC2dd on Base, you are looking at
the live token. If it is any other address, you are looking at the record of a
contract that was switched off on 15 September 2026, and its price, its supply and
its market capitalisation describe that contract rather than this one.
We have filed corrections with the sites that carry an out of date record, and each reviews on its own schedule. Until a site updates, the address test above is the reliable one, and the figures on /stbu are read from the chain on this site every day.
Who can change anything
Three powers exist in the contract. This is who holds each one.
Rebuilt from the contract’s own log on every build, so a change shows up here without anybody editing this page.
| The power | Who holds it today | What it cannot do |
|---|---|---|
| The powerCreate STBUCLAIM_ROLE | Who holds it todaythe claim contract0xec5B3e512de13cb5DdFD84B2DF3167230F2e66a4 | What it cannot do It cannot choose who receives the tokens. Every mint answers a voucher signed for one wallet and one amount, and no mint can take the total past 250,000,000 STBU. |
| The powerStop every transferPAUSER_ROLE | Who holds it todayone key, held by Stobox0x0e8aB96989eDd4616959bB56757eE9cBD3ca4DBb | What it cannot do It cannot start them again, cannot create STBU, and cannot move anyone’s balance. A pause stops all transfers including ours, and only the admin can lift it. |
| The powerGrant or withdraw the two above, and lift a pauseDEFAULT_ADMIN_ROLE | Who holds it todaythe admin Safe0xDD7B82eBD733458220B90c1f98Cc7EBFd1cb4372 | What it cannot do It cannot create STBU, cannot pause, and cannot move a balance. It can hand the power to create STBU to another address, which is the one thing worth watching here, and that grant is a public transaction on this contract. |
There is no fourth power. The published source has 29 functions and among them no owner, no blacklist, no freeze, and nothing that moves a balance you did not approve yourself. The address is not a proxy, so the code sitting there cannot be swapped for different code. The static analysis behind that paragraph is at /stbu/security.
Every role transaction this contract has ever seen – five of them – sits in one block, 48830559, on 19 July 2026. In it the deploying key took the admin power, passed it to the Safe, and gave up its own, in that order. Nothing has touched the roles since. If anything ever does it lands in the same log, and this table is built from that log rather than from a list we keep.
Transfers are running: paused() answers false as this page is built.
One thing on this page is a commitment rather than a rule the contract enforces. Claims close on 31 December 2026, and the contract holds no closing date of its own: the close is Stobox stopping the signing of vouchers and then withdrawing the power to create STBU from the claim contract. That withdrawal is a transaction on this contract, so it is public the moment it happens, and until it happens the power exists. Better you read it here than find it out later.
You can settle every line of this yourself in about a minute, and you should not take our word for any of it. Open the contract on BaseScan, choose Read Contract, and call hasRole with the role and the address. The three roles are the only ones the contract has:
CLAIM_ROLE · 0xf7db13299c8a9e501861f04c20f69a2444829a36a363cfad4b58864709c75560
PAUSER_ROLE · 0x65d7a28e3265b37a6474929f336521b332c1681b933f6cb9f3376673440d862a
DEFAULT_ADMIN_ROLE · 0x0000000000000000000000000000000000000000000000000000000000000000
The rules that do not change
Short, and worth knowing before anything else.
None of this is specific to STBU. All of it is how people lose tokens.
Stobox will never message you first, and will never ask for your seed phrase or your private key. Anyone who does is not us, whatever name they use.
The only addresses we publish are on this site and on stbu.stobox.io. If you were sent an address anywhere else, check it against those two places before you send anything.
Burning is permanent and irreversible. So is a trade in the wrong pool. Neither of them can be undone by us or by anyone.
You can verify every claim on this page yourself: the contract source is published on BaseScan and independently in Sourcify, and a static analysis of it is at /stbu/security. The token page with live figures is at /stbu.
Straight answers
What people ask after they have lost something.
Which STBU contract and pool did Stobox deploy?
The contract is 0xe0c0F44A84CC4a60206360006ebA237a5e8fC2dd on Base, chain id 8453, which as a CAIP-19 asset id is eip155:8453/erc20:0xe0c0F44A84CC4a60206360006ebA237a5e8fC2dd. The pool is the Uniswap v4 pool on Base quoting STBU against USDC, pool id 0x28bd1d1afcc57d766c5d1c5c38bd8beb376a0c98de719460cdcef60900f7b8b5. Those two strings are the whole answer. Any other contract or pool carrying the STBU name was not deployed by Stobox Innovations Ltd.
How do I know I am in the right STBU pool?
Three checks, in this order. The network says Base, not Ethereum, BNB Chain, Polygon or Arbitrum. The contract address matches the whole string above, not just its first four characters. And the amount you are offered looks sensible: at the price on this page, 100 USDC should offer tens of thousands of STBU, so an offer of one or two thousand means the pool is not ours. The third check alone would have prevented every loss seen so far.
I received far less STBU than I expected. What happened?
Most likely the swap went through a pool that is not ours. Those pools do not fail with an error: a swap in them completes normally, and what comes back is a small fraction of what was paid, because they carry very high fees and hold almost nothing. A pool can only pay you what it holds. The depths of every pool carrying this name are in the table on this page, read from the chain, so the comparison needs no simulation.
Why was my STBU trade rejected?
Usually the pool’s depth rather than a fault. The pool is young, so a trade moves its price, and the bigger the trade the more it moves. When that move is larger than the slippage tolerance, the interface refuses rather than filling you at a worse price, which is it protecting you rather than something going wrong. The tolerance is set by the interface, not by Stobox: Uniswap sets it to Auto and prints the figure above the confirm button, and it picks a wider one for a young pool than for a deep one. Read that number rather than assuming one. Two normal ways through: raise the tolerance in the settings and accept the price shown, or buy in smaller amounts, which costs less in price impact overall.
Is Stobox Token v.2 or v.3 a newer version of STBU?
No, and the naming is the trap. Those names are written into the four discontinued contracts themselves and cannot be changed by anyone, Stobox included. The live token is named simply Stobox Token. Buying v.2 or v.3 gets you a token that was switched off on 15 September 2026: it cannot be migrated and it is not the asset this site describes.
Who controls the STBU contract?
Three powers exist in it and no others. The power to create STBU sits with the claim contract 0xec5B3e512de13cb5DdFD84B2DF3167230F2e66a4, which can only answer a signed voucher for one wallet and one amount. The power to stop transfers sits with one key held by Stobox, which cannot start them again. The power to grant or withdraw either of those, and to lift a pause, sits with a Safe that needs two signatures of three. All three are listed with their addresses on this page and can be checked with hasRole on BaseScan.
Can Stobox freeze my STBU or take it back?
Take it back, no. The contract has no owner, no blacklist and no function that moves someone else’s balance without an allowance you approved yourself, and it is not a proxy, so the code cannot be replaced with code that does. Freeze, in one sense yes: one key can pause the contract, which stops every transfer at once including ours, and only the admin Safe can lift that. A pause is visible on chain and paused() answers it at any moment.
Can more STBU be created?
Yes, until the claim window closes, and only in one way. The claim contract holds the only power to create STBU and it answers signed vouchers for burned legacy tokens, one wallet and one amount at a time, with the total bounded by a cap of 250,000,000 written into the contract. Claims close on 31 December 2026. The contract itself holds no closing date, so the close is Stobox stopping the signing of vouchers and then withdrawing that power from the claim contract, which is a public transaction on Base when it happens.
Can Stobox reverse a trade made in the wrong pool?
No. Nobody can, Stobox included. A trade is as final as a burn, and both are permanent and irreversible. That is why the three checks on this page come before you confirm rather than after.