BTCB2, XBT, BIP110: Are They the Same Coin?
Your pool pays BTCB2, one exchange shows XBT, and another says BIP110. Did you mine the wrong coin, or must you convert it before depositing? The confusion is understandable: different services really do label this BLAKE2b fork differently.
One chain can have several tickers, while one ticker can refer to different chains. Whether a conversion is needed depends on the recipient’s supported network, not just a few letters.
First ask who chose the label
On Neoxa (NeoxEX), the market page now displays XBT with the name Bitcoin BLAKE2b, while its links still use paths such as BTCB2_USDC. Display labels and internal market codes can differ. We verified the current display, but have not found a formal renaming announcement or effective date. Neoxa / NeoxEX ↗
NonKYC rechecked on September 13: its asset API name is XBT ( BTCB2 / Blake2b fork), and its network label is XBT ( BTCB2 BIP110 / Blake2b fork). The asset ID 6a9ac7b05eba1fc0c907c964, BTCB2 ticker and BTCB2/USDT market path remain unchanged; the market API still names it Bitcoin Blake2B. The API name recorded on September 8 was Bitcoin BIP110 (BLAKE2b); the formal renaming date remains unverified. The venue explicitly says not to deposit BTC. Before sending, verify that the recipient supports this BLAKE2b fork. NonKYC API ↗NonKYC BTCB2/USDT API ↗NonKYC BTCB2/USDT ↗
SafeTrade now uses XBT: its listing announcement explicitly identifies Bitcoin Blake2B, and its live market displayed XBT/USDT on September 9. BIP110 was the venue’s earlier label; that label change alone does not mean you must convert your BTCB2 pool payout into another coin. SafeTrade:XBT / Bitcoin Blake2B ↗
In these specifically identified BLAKE2b-fork contexts, the labels refer to the same chain’s asset; changing a ticker alone does not require conversion. Trading links and the dated comparison are kept on the coin page, rather than maintaining a second market list here. View exchange names and trading links ↗
Why does BIP110 appear in a coin name?
BIP-110 originally proposed a temporary soft fork restricting certain data uses. The later BLAKE2b change altered proof of work in a separate hard-fork change. The developments are historically related, but seeing BIP110 as a trading ticker does not mean the original proposal required a new mining algorithm. BIP-110 ↗BLAKE2b developer documentation ↗
BTCB2 lets pools and exchanges label the BLAKE2b chain separately. Bitcoin BIP110 is the name used by bitcoinbip110.org, whose technical page specifies BIP110 as its preferred ticker. bitcoin-blake2b.org titles its site Bitcoin. These are naming choices by services and information sites, not evidence of a joint decision by every developer, pool and exchange. BitcoinBIP110.org ↗Bitcoin-Blake2b.org ↗
Separate Luke, Knots, Chris Guida and the information sites
Luke Dashjr, using luke-jr, opened the BLAKE2b hard-fork PR in the Bitcoin Knots repository and described intended compatibility with existing PoW hardware. That is a directly verifiable development action. Knots has its own repository and releases; this cannot be described as a Bitcoin Core team decision to rename Bitcoin or change its algorithm. Luke / Knots PR #359 ↗
Chris Guida also participated in the PR’s public review; one comment asks for the wording to say Knots. Reviewing code and advocating a universal market name are separate matters. We did not obtain verifiable complete first-person statements from him or Luke requiring all platforms to use XBT or BIP110, so circulating paraphrases are not presented as their joint position. Chris Guida’s review comment ↗
Information sites have positions of their own. BitcoinBIP110.org promotes Bitcoin BIP110 / BIP110 and has published a warning about Neoxa; Bitcoin-Blake2b.org describes the chain it supports as Bitcoin. Those statements document each site’s stance, not automatically that of Luke, Chris or the entire community. Learn retains BTCB2 as its internal identifier without adjudicating naming legitimacy or treating a listing as an exchange safety endorsement. Information-site announcements and position ↗Bitcoin-Blake2b.org ↗
The practical question is which network receives your coins
Suppose you receive a BTCB2 pool payout and want to deposit into a market labelled XBT. Check that the exchange’s asset and deposit pages explicitly identify the BLAKE2b fork and link the relevant explorer and project information. Bitcoin or XBT alone is insufficient—ask the venue if the network is unclear. A BTC-looking address is not enough. Chain identity and deposit integration ↗
XBT is particularly easy to confuse. Kraken’s official documentation uses XBT for mainstream Bitcoin, retaining it in some APIs and records. Neoxa’s use of XBT therefore cannot establish that XBT elsewhere means BTCB2, and Learn does not create that global mapping. Kraken:XBT / BTC ↗
After identifying the network, check current deposit and withdrawal availability, confirmation requirements and minimums; a small end-to-end test may be appropriate. Different tickers on the same chain generally do not require conversion. A mainstream BTC recipient cannot simply receive BTCB2. For how this chain creates mining and rental options for SC hardware, continue with the mining guide. BTCB2 mining and hashrate rental ↗Which wallet should I use for BTCB2 mining? ↗Trading links and verification date ↗