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.
Missing symbols on Binance
See original GitHub issueHi there,
there seems to be missing symbols on Binance, specifically running [s for s in exchange.symbols if 'BTC' in s] in python returns only ['BTC/BUSD', 'BTC/USDT']. The same holds for [s for s in exchange.markets.keys() if 'BTC' in s]. Other exchanges seem to be ok.
ccxt version: 1.41.19 python: 3.8.7 os: win 10
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
python-binance api invalid symbol only for certain pairs
I am testing pairs from https://api.binance.com/api/v3/exchangeInfo there seems to be no rhyme or reason to the symbols that work or don't ...
Read more >Problems with Binance symbols #4 - CryptoMF/frostybot-php
frostybot binance:markets symbol=ADABNB { "results": { "code": 900, ... Looking at the config, Binance seems to be missing information.
Read more >How to Resolve Order Issues - Binance
Occasionally you may encounter problems with your orders when trading on Binance. We can divide these into two categories: 1.
Read more >How to Customize Binance Futures Trading Interface
Go to the Binance Futures trading interface and click on the [Settings] icon. This panel allows you to customize the appearance of your...
Read more >Summary of Failed Orders in Futures Trading - Binance
When you trade in the futures market, sometimes the order fails to be placed or is not filled. Here are some possible reasons....
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
@LukasUlrych ah, i see, hold on, will fix that in 1.41.20.
@kroitor Thank you, it helped! The issue seems to be that running just
defaults to defaultType = ‘future’ not defaultType = ‘spot’.