In 4,030 parsed signals the exchange's own string for the contract almost never appears in the message. The gap looks cosmetic until the name carries a multiplier, and then the quantity box means something a thousand times larger than you think.
Why does a signal say SHIB/USDT when the exchange says SHIB1000USDT?
Because the channel is naming a coin and the exchange is naming a contract, and only one of those two things can be traded. A perpetual has a ticker assigned by the venue that lists it, the venues do not agree with each other, and some of those tickers carry a multiplier that changes what every price and every quantity on the screen means.
Most of the time the gap is harmless. You read #BTC/USDT, you type BTCUSDT, you get the contract you expected. The gap turns expensive on a small handful of names where the multiplier is baked into the string. On those, the coin's price and the contract's price differ by a factor of a thousand, and so does the number in the order ticket.
This article is about the string itself. What a perpetual is at all is covered in Spot, futures and perpetuals: what you actually trade, and which coins get called is measured in Bitcoin is 0.8% of the signals. Here the subject is what sits between the hash and the entry price.
How do channels actually write the pair?
As a slash pair with a hash in front of it, almost every time. Across the 4,030 signals our parser has read, dated 9 November 2021 to 18 August 2026, from the 22 accounts in our 47-provider index that publish anything readable, the forms break down like this. They overlap, because one message can carry several.
| Form in the message | Signals | Share |
|---|---|---|
slash pair, BTC/USDT |
3,568 | 88.5% |
hash prefix, #BTC/USDT |
3,382 | 83.9% |
dollar prefix, $BTC |
231 | 5.7% |
concatenated, BTCUSDT |
202 | 5.0% |
TradingView perp suffix, BTCUSDT.P |
98 | 2.4% |
| the word "spot" | 71 | 1.8% |
| the word "futures" | 30 | 0.7% |
| the word "perp" or "perpetual" | 0 | 0.0% |
Not a single message in the corpus uses the word for the instrument every one of these calls is about, and only 30 mention futures at all. The string is doing all the work of telling you which market this is, and only 5.0% write it without punctuation at all.
Which leaves a translation to perform on nearly everything else. The symbol we store appears in the raw message as a literal substring in 204 messages, 5.1% of the corpus, and in 3,825 of them, 94.9%, once every punctuation mark has been stripped out first. The whole gap is punctuation, and our parser strips it before it looks anything up; a subscriber reading on a phone does not.
What does the 1000 in the name do to the price?
It multiplies it, and the exchange says so in the listing notice. Binance's announcement for the contract states the arithmetic in two sentences:
"The notional value of the 1000SHIBUSDT contract is 1,000 SHIB each." "The underlying index price of 1000SHIBUSDT is 1000 times that of the SHIB/USDT spot index." - Binance Futures Will Launch USDT-Margined 1000SHIB Perpetual Contracts
Read live on 18 August 2026, the same token sits at three different numbers depending on which string you looked up.
| String | Where | Last price |
|---|---|---|
SHIBUSDT |
Binance spot | 0.00000443 |
1000SHIBUSDT |
Binance USDT perpetual | 0.004429 |
SHIB1000USDT |
Bybit USDT perpetual | 0.004429 |
Three tickers, one asset, and two price scales 1,000 apart to the rounding of the spot tick. A channel publishing an entry of 0.00000450 and a stop of 0.00000420 has quoted the first row. Typed into either of the other two, those digits sit a thousandfold below the market, which means a buy order that can never fill and a sell order that is already through the book.
One kind of quantity in the message crosses the boundary untouched, and that is ratios. The distance from entry to stop reads the same on both scales: a stop 6.7% below entry is 6.7% below entry at either price. Everything you can do with that ratio still works, including the sizing arithmetic in Position sizing when the trade idea is not yours. Every absolute price in the post has to be multiplied before it means anything.
What does the multiplier do to the size you type?
This is where the money is. Order quantity on these instruments is counted in contracts, and one contract is a thousand tokens, so the number you would type on spot is a thousand times too large on the perpetual.
The venues state their own units. Bybit's API describes lotSizeFilter.qtyStep as "the step to increase/reduce order quantity" and returns quantities in the instrument's base coin; for SHIB1000USDT that base coin is literally SHIB1000, with a minimum order of 10 and a step of 10. So the smallest position Bybit will accept on the contract is ten thousand SHIB, and every size above it moves in ten-thousand-SHIB jumps. Binance's 1000SHIBUSDT reports a step size and a minimum quantity of 1, against a base asset of 1000SHIB.
Work an example through at today's prices. A follower wants roughly $200 of exposure. On spot at 0.00000443 that is about 45,146,700 SHIB, and 45,146,700 is what goes in the quantity box. On the perpetual at 0.004429 the same $200 is about 45,157 contracts. Type the spot quantity into the futures ticket and you have asked for a position of nearly $200,000.
That mistake normally announces itself as a refused order, because an account funded for a $200 trade cannot post margin against $200,000 of notional. Refusal is the good outcome. On an account large enough to carry it, the order fills, and the follower is now running a thousand times the position they sized, with the liquidation distance that goes with it. What that distance looks like at the leverage these channels post is in Liquidation explained.
Is there a rule for where the number goes?
There is one contract's worth of it, and no rule. SHIB1000USDT is a single string on a single venue, and nothing generalises from it.
Reading Bybit's full list of live USDT perpetuals on 18 August 2026, 716 of them are trading, and 17 carry a multiplier in the name. Sixteen put the number first, in the shape 1000PEPEUSDT, 10000SATSUSDT, 1000000MOGUSDT. Exactly one puts it last, and it is the SHIB contract, which launched in October 2021 and has kept its original string ever since. Binance's list has 13 multiplier contracts and all 13 lead with the number.
So a reader who learns the rule from 1000PEPEUSDT and applies it to SHIB gets nothing back from Bybit's search box, and a reader who learns it from SHIB1000USDT and applies it anywhere else gets nothing back either. Both readers concluded, reasonably, that there was a rule.
Our corpus holds both orderings for the same idea. A Spanish-language channel in the archive writes 1000SHIB; the string stored in our database from a different account is SHIB1000USDT. Neither channel is wrong about the trade. They are naming two contracts, on two venues, with the same multiplier on the same token, and the arithmetic in the post travels between them while the string does not.
Is the multiplier itself the same everywhere?
No, and this is the failure the price scale will not warn you about. Two contracts on the same token can carry different multipliers, and both of those strings turn up in our signals.
1000SATSUSDT and 10000SATSUSDT each appear once in the corpus. Binance lists the first as a USDT perpetual and does not list the second. Bybit lists the second, with a base coin of 10000SATS, a tick size of 0.00000001, a minimum order of 100 and a quantity step of 100, and does not list the first. Checked live on 18 August 2026, Binance's 1000SATSUSDT traded at 0.00001020 and Bybit's 10000SATSUSDT at 0.00010202, which is the factor of ten showing up in the price, to the rounding, as the names promise.
A follower who reads the extra zero as a typo and trades whichever contract their venue offers has taken a position ten times the intended size, at prices that look plausible on both charts. Nothing on either screen flags it. The two charts have the same shape, the same percentage moves, and different axes.
Twelve distinct multiplier strings appear in our parsed signals, across 25 signals from 10 different accounts:
1000XECUSDT 7 1000PEPEUSDT 5 1000CHEEMSUSDT 3 1000BONKUSDT 2
1000CATUSDT 1 1000RATSUSDT 1 1000000BOBUSDT 1 10000SATSUSDT 1
SHIB1000USDT 1 1000SATSUSDT 1 1MBABYDOGEUSDT 1 1000NEIROCTOUSDT 1
Twenty-five signals out of 4,030 is a small corner of the feed. In the wider archive of raw messages the form shows up 59 times across 15 of the 42 channels, including #1000000MOG/USDT and #1000TURBO/USDT. A reader can go a long time without meeting one, and the first meeting is the expensive one.
What happens if the channel's string does find something?
You get a real market with a real chart, and it may be the wrong one. The trap is not a missing ticker; it is a ticker that resolves.
SHIBUSDT is a live pair on Binance spot as of 18 August 2026, with a tick size of 0.00000001. It is not a Bybit USDT perpetual at all, and neither is PEPEUSDT, BONKUSDT, FLOKIUSDT or XECUSDT. On those tokens Bybit offers the multiplier contract and nothing else. So the subscriber who searches Bybit for the channel's string finds nothing and has to guess, while the subscriber who searches Binance finds the spot pair and can buy it immediately.
The spot pair is a coherent instrument. It also has no leverage, no short side, and no relationship to a call written for a perpetual at 20x, which makes the resulting trade a different trade with the same name on it. Whether the message even tells you which market it meant is doubtful: one channel in the archive labels its own calls #Spot/Futures and states leverage in the same post, and 24 archive messages mention spot and futures together.
Buy/LONG #AVAX/USDT 40-44 ... Spot/Futures 5-10x- altzsignalz
Spot has no leverage, so the label settles nothing.
What about .P, and the asset at the end of the string?
BTCUSDT.P is a TradingView symbol. TradingView's own page for it names the instrument "Bitcoin / TetherUS PERPETUAL CONTRACT" and attributes it to Binance, so the suffix is that platform's way of separating the perpetual from the spot pair on its charts. It is not a string any exchange search box will accept. Ninety-eight signals in our corpus, 2.4%, carry it, which is the shape a symbol takes when it is copied off a TradingView chart.
The tail of the string is not a promise about the venue either. One archive message lists six venues for a single call and writes a different quote asset for one of them:
Binance Futures, Bitget Futures, ByBit USDT, HyperLiquid Futures(NOT/USDC), KuCoin Futures, OKX Futures/#NOT/USDT Take-Profit target 2- Okxfreecryptosignal
That parenthesis is accurate. Hyperliquid's contract specifications describe its perpetuals as "USDC margining, USDT denominated linear contracts", meaning the oracle price is quoted in USDT while the collateral you post is USDC. A follower routing the same call to that venue needs a different asset in the account before the position is possible, and the message says so in five characters inside a bracket.
What this does not prove
Nothing here says a channel that writes #SHIB/USDT has done anything wrong. That is how the token is named, it is how a reader searches for it, and no channel controls how Bybit or Binance chose to string their contracts together. Publishing a coin name where a contract name would be more precise is a convention, not misconduct.
Our corpus figures describe our own index as of 18 August 2026: 4,030 parsed signals from 22 publishing accounts out of 47 indexed, 498 distinct symbols, and an archive of 42 channel dumps holding 25,932 messages with text. That set was assembled from channels large enough to index and formatted consistently enough to read, so it is a selection and not a sample of the signal market. The counts move as channels publish.
The exchange listings, prices, tick sizes and quantity steps above are a snapshot of one day. Venues add and remove contracts, and they change tick and lot parameters on live instruments, so any specific figure here should be re-read from the endpoint before it is relied on.
We have not measured how often a follower actually mistypes any of this. We hold published messages and replayed prices, and no order-level data of any kind, so the cost of the error is arithmetic we can demonstrate and frequency we cannot. Nothing here is financial advice.
The practical read
Put the venue's last price beside the entry price in the message before you do anything else. A gap of a thousand, or of ten thousand, is the multiplier announcing itself, and ordinary movement between publication and reading does not open a gap that size. Whatever the ratio turns out to be, it applies to every absolute price in the post: the entry, the stop and each target.
That test is worth preferring to the obvious one. Reading the venue's string and asking whether it carries a number the message did not fails precisely where the risk is highest, because 59 messages in our archive already write the multiplier themselves, in forms like #1000TURBO/USDT and #1000000MOG/USDT. A reader applying the string rule mechanically to one of those would multiply a price that was already multiplied. Comparing the two prices handles both cases without your having to know which one you are in.
Then confirm the quantity box. On a multiplier contract, the units are contracts, and the size you want is your intended dollar notional divided by the contract's own price, never by the price of the coin. The order ticket on these names also carries a minimum and a step, which is one of several reasons the size you get is not the size you calculated. The others are in Which order type turns a published entry into a position.
Last, treat the percentage as the only portable number in the post. Entry to stop and entry to target survive any multiplier, any venue and any price scale. The digits do not.
Current ratings for the channels we can score are at Signal Providers, and the rules our replay applies are on the Methodology page.
Sources
- Message forms and corpus counts. Our production index and channel archive as of 18 August 2026: 4,030 parsed signals dated 2021-11-09 to 2026-08-18 from 22 publishing accounts of 47 indexed, 498 distinct symbols; the form table; 204 literal-substring matches against 3,825 after punctuation is stripped; 12 multiplier strings over 25 signals from 10 accounts. Archive figures from
data/channel_dumps/, 42 files, 25,932 messages with text: 59 multiplier-form messages across 15 channels, 24 messages mentioning spot and futures together, and the quoted lines fromaltzsignalzandOkxfreecryptosignal. - What the 1000 in the name means. Binance Futures Will Launch USDT-Margined 1000SHIB Perpetual Contracts with Up to 25X Leverage, opened and quoted directly for the notional value and the index relationship.
- Bybit instrument metadata.
api.bybit.com/v5/market/instruments-info?category=linear&symbol=SHIB1000USDT, fetched 18 August 2026: base coinSHIB1000, price scale 6, tick size 0.000001, minimum order quantity 10, quantity step 10, minimum notional 5. The same endpoint over the full linear category returned 824 instruments, 716 of them USDT perpetuals trading, 17 with a multiplier in the name, and10000SATSUSDTwith base coin10000SATS, tick 0.00000001, minimum order 100, step 100. Field definitions from Bybit V5 API: Get Instruments Info. - Binance futures metadata.
fapi.binance.com/fapi/v1/exchangeInfo, fetched 18 August 2026:1000SHIBUSDTtrading with base asset1000SHIB, tick 0.000001, step size and minimum quantity 1;1000SATSUSDTtrading; noSHIB1000USDTand noSHIBUSDTperpetual; 13 multiplier contracts, all leading with the number. Filter definitions from Binance USDS-Margined Futures: Exchange Information. - Prices quoted. Binance spot
SHIBUSDT0.00000443 and futures1000SHIBUSDT0.004429; BybitSHIB1000USDT0.004429; Binance1000SATSUSDT0.00001020 against Bybit10000SATSUSDT0.00010202. All read 18 August 2026 from the public ticker endpoints of the two venues above. Binance spot pair status and tick size fromapi.binance.com/api/v3/exchangeInfo. - The .P suffix. TradingView: BTCUSDT.P, opened, which names the instrument "Bitcoin / TetherUS PERPETUAL CONTRACT" on Binance. TradingView's symbol type page was opened and does not document the suffix itself, so the attribution rests on the symbol page.
- Collateral on a third venue. Hyperliquid: contract specifications, opened and quoted for "USDC margining, USDT denominated linear contracts".