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
Feat/polkadex v2 #6558
Feat/polkadex v2 #6558
Conversation
PR update:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the changes are okey but just check that and see if you want to implement it in another PR or do the changes on this one.
Btw, I think that we should also trigger the event of the order book updates what do you think?
hummingbot/core/event/events.py
Outdated
@@ -37,6 +37,8 @@ class MarketEvent(Enum): | |||
|
|||
class OrderBookEvent(int, Enum): | |||
TradeEvent = 901 | |||
OrderBookDataSourceUpdateEvent = 904 | |||
PublicTradeEvent = 905 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@petioptrv hey pet, the TradeEvent is actually the public trade event check that the order book is triggering it when a new trade arrives
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The idea here was to differentiate the "data-source" event from the event that the clients of the exchange connector want to consume, but I agree that, in this case, it's redundant. I'll make the change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done, @rapcmia, the only part of the functionality that needs to be re-tested is that public trade events are being received by the bot
Before submitting this PR, please make sure:
A description of the changes proposed in the pull request:
This PR introduces an update to the Polkadex connector to use the V2 API.
Tests performed by the developer:
Tips for QA testing:
Note that every now and then, the periodic order status update may fail because it happened immediately after submitting an order. Since Polkadex is a decentralized exchange, it takes a couple of seconds for the order to make it onto the chain and to become available for order status updates.
[ch-43708]