Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sBTC has token ticker collisions, should it be changed? #116

Open
314159265359879 opened this issue Jan 30, 2023 · 4 comments
Open

sBTC has token ticker collisions, should it be changed? #116

314159265359879 opened this issue Jan 30, 2023 · 4 comments

Comments

@314159265359879
Copy link
Contributor

image

There are at least four other tokens with the same ticker. Should a different ticker be used?

@Hero-Gamer
Copy link
Contributor

Hero-Gamer commented Feb 1, 2023

(without having digging into what others are exactly, so pls take my comment with a grain of salt)

  • On a general level, I'm not personally concerned.
  • Even if we were to launch ours first, there is nothing stopping multiple people (scam or not scam) launching theirs with the same sbtc name. Sandbox or Solana could launch their sandbox/solana backed BTC sBTC anytime.
  • It's probably just about making our documentation, links etc on Coinmarketcap or CoinGecko look professional and legitimate.
    Keep to hear others thought though.

@badonyx
Copy link

badonyx commented Feb 12, 2023

Yes it should be changed, but not for this reason.

https://twitter.com/0xbabo/status/1623004605713096705

I still don't like "sBTC" as the name for Stacks' native BTC. It's inconsistent with established branding around the letter 'X' (STX, PoX, ALEX, xBTC, xUSD). And it's just begging to be nicknamed "shitcoin-BTC" by BTC purists.

I always liked the ticker "xBTC" but never liked the instrument and I don't think anyone will want to use it after sBTC. So there's no reason not to co-opt the ticker other than to avoid collisions. Existing asset tickers xBTC and xUSD would need to be rebranded to avoid confusion but I don't think this would be particularly difficult considering the limited reach of these assets (basically contained entirely within the ALEX and Arkadiko ecosystems).

@cuevasm
Copy link

cuevasm commented Apr 27, 2023

Anyone that feels strongly about this/naming in general should get involved in the brand WG: stacks-network/stacks#483

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants
@cuevasm @314159265359879 @Hero-Gamer @badonyx and others