-
-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
Bitcoin cash (BCC vs BCH) #83
Comments
Thanks for this very important notice! |
Received this from GDAX/Coinbase. They say, they will support it... in January 2018.
|
Yobit also has BBCC – BaseballCard %) |
Before:
|
After:
|
Long time no see.
It throws :
|
Hi! Good to hear again from you! Thanks for reporting! I will fix this, of course (probably very soon). |
This issue with BCC vs BCH on Bter should be fixed now! Thx again! |
The fix is available in v.1.3.86. Best wishes! |
Thank you but now it throws error on QTUM/ETH.
Call method |
Hmmm... I'm not getting this on testing. But I'll fix it anyway, thanks for feedback! Will upload a fix soon. |
As all of you are well aware there is a new currency in the game by the name of Bitcoin Cash.
https://coinmarketcap.com/currencies/bitcoin-cash/
I manually checked a lot of exchanges and those that do have it, are calling it either BCH or BCC.
I propose that ccxt's default simbol for Bitcoin Cash should be BCH becouse BCC is used already by
https://coinmarketcap.com/currencies/bitconnect/.
That being said I can't seem to think of a way of doing this but manully checking which exhange is calling it BCC and then switching the value upon call BCH->BCC so that we can still call it BCH.
I suggest putting an enhancement label on this and waiting for 10 days or maybe two weeks.
A lot of people think that the currency might be dumped by everyone ant that her value will be next no nothing.
I am not a prophet but what i do know is that if it survives the first 2 weeks than it's here to stay and we should adapt to it.
The text was updated successfully, but these errors were encountered: