Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
please revert new HitBTC stuff
See original GitHub issueHi @timmolter
Can I request that we revert the new HitBTC implementation as we’ve lost some functionality.
I recently added methods to move funds between the accounts in HitbtcAccountService but they’ve been deleted. This functionality is crucial for my software, and is still supported by the exchange, there’s no reason to remove it.
Could you please revert the commit until any missing functionality is added back in?
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
The Phishing Scam - How to Avoid it ? - HitBTC
There are a lot of scams going on. Many scammers use well known brands to trick people into giving out their details.
Read more >Read Customer Service Reviews of hitbtc.com - Trustpilot
Please report this issue by submitting a ticket here https://support.hitbtc.com/en/support/tickets/new or by sending an email to support@hitbtc.com.
Read more >HitBTC Exchange Review 2021 - Is It Safe or Scam?
It allows traders to change the asset used as collateral for open positions. Supported currencies are BTC, ETH, TRX, BCH, ADA, DOT, SOL,...
Read more >HitBTC price alerts and HitBTC exchange listing alerts
Be the first to know when a new coin is listed on an exchange. View our recent detections. Choose from 9 different ways...
Read more >Connect your Bot to HitBTC - Cryptohopper Documentation
Cryptohopper needs this bridge in order to do all the automated things you love such as, placing automated orders and reading your balance...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I believe the names of the methods were closely named to the API calls. Since they have changed the API the names changed a bit. However that is good feedback, and I think I can adjust the code.
I wasn’t quite ready for the merge to happen (thus the *** NOT READY FOR MERGE*** at the top of the PR.
However I would like to take your suggestions and move forward with a new PR I can get going rather than reverting if that is OK?
OK, merge reverted. Thanks for working together on this!