[binance] spot UserDataStreamService - move from REST to websocket authorization#5259
Open
rizer1980 wants to merge 5 commits intoknowm:developfrom
Open
[binance] spot UserDataStreamService - move from REST to websocket authorization#5259rizer1980 wants to merge 5 commits intoknowm:developfrom
rizer1980 wants to merge 5 commits intoknowm:developfrom
Conversation
…y mechanism. So, added new service to specially for SPOT with Ed25519 key one time authorization.
…PR/binance-spot-fix
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
[binance] spot UserDataStreamService - don't support REST authorization via loginKey anymore.
So, wee split SPOT and FUTURES UserDataService.
SPOT now work with websocket auth. and use Ed25519 API Key
FUTURE still work with REST loginKey and don't support websocket auth for now.