deribit implementation #1032
Closed
deribit implementation #1032
Conversation
This file contains 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
|
Firstly, thank you for looking into this! ATM no one is working on Deribit aside from the PR you have already seen, but after OKX v5/Kucoin and Gateiov4 this is next on the list. The goal is to cover all the highest volume derivative exchanges based on https://ftx.com/volume-monitor |
gloriousCode
added
help wanted
and removed
review me
|
@samuael has took this exchange implementation on and is working on it here: https://github.com/samuael/gocryptotrader/tree/gderibit :) |
|
Superseded by #1082 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PR Description
Is someone still working on the deribit implementation?
I have some work here and thought I'd share in case there's interest. It is based on #705 but also has added websocket implementation for creating orders.
It has been tested against the live exchange, but will of course need to be built upon to add the other endpoints to complete the implementation. Happy to work on fleshing this out further (as time permits) if it's of interest and no one is working on it already.