Thanks a lot for your work, it has been extremely useful so far. I only have one minor, inconvenient issue. I can circumvent this by querying the respective websocket directly without cryptofeed but obviously would prefer integration with cryptofeed.
Describe the bug
BTC-USD-PERP gives the linear BTCUSD contract from Phemex (settled in USD ) instead of the inverse (settled in BTC). When querying the websocket from Phemex directly, BTCUSD aka BTC-USD-PERP gives the inverse, and uBTCUSD gives the linear. The inverse contract is a factor of 10 or more traded than the linear contract, whereas the linear one is quite illiquid (relative for a BTC perp contract).
I have seen an issue raised about this before but from what i gathered it has not been fixed / implemented yet.
To Reproduce
See above. Inverse contract is i think unavailable through cryptofeed.
Expected behavior
BTC-USD-PERP should give the inverse and not linear contract, given the naming convention of Phemex. And if only one can be chosen, people most likely expect the inverse due to volume difference.
Screenshots
If applicable, add screenshots to help explain your problem.
n/a
Operating System:
macOS, linux, etc
n/a
Cryptofeed Version
please list the version you are using, and how it was installed (from source, pypi, etc).
2.1.2. Sorry i am running cryptofeed right now in a real case scenario so don't want to update in the middle of it, but from what i've seen this has not been updated since regardless.
Dear cryptofeed dev(s),
Thanks a lot for your work, it has been extremely useful so far. I only have one minor, inconvenient issue. I can circumvent this by querying the respective websocket directly without cryptofeed but obviously would prefer integration with cryptofeed.
Describe the bug BTC-USD-PERP gives the linear BTCUSD contract from Phemex (settled in USD ) instead of the inverse (settled in BTC). When querying the websocket from Phemex directly, BTCUSD aka BTC-USD-PERP gives the inverse, and uBTCUSD gives the linear. The inverse contract is a factor of 10 or more traded than the linear contract, whereas the linear one is quite illiquid (relative for a BTC perp contract).
I have seen an issue raised about this before but from what i gathered it has not been fixed / implemented yet.
To Reproduce See above. Inverse contract is i think unavailable through cryptofeed.
Expected behavior BTC-USD-PERP should give the inverse and not linear contract, given the naming convention of Phemex. And if only one can be chosen, people most likely expect the inverse due to volume difference.
Screenshots If applicable, add screenshots to help explain your problem. n/a Operating System:
Cryptofeed Version
Thank you