-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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/dydx v4 perpetual derivative #6987
base: development
Are you sure you want to change the base?
Feat/dydx v4 perpetual derivative #6987
Conversation
…1/hummingbot into feat/dydx_perpetual_derivative
1 similar comment
…1/hummingbot into feat/dydx_perpetual_derivative
…into feat/dydx_perpetual_derivative
@yancong001 are you going to submit the test soon? so I can review everything together |
Yes, I will submit it soon |
…1/hummingbot into feat/dydx_perpetual_derivative
…1/hummingbot into feat/dydx_perpetual_derivative
…1/hummingbot into feat/dydx_perpetual_derivative
Unittest has submitted, separate passed (coverage run - m nose "test/hummingbot/connector/derivative/dydx_v4_perpetual") @cardosofede |
Test commit
Steps to reproduce:
https://drive.google.com/drive/folders/10KrgraekoCV6q96Z-MXgz4L2tJ3kTtQu |
fixed |
I have pulled this branch down to assist with some QA. At first I was getting an error with the password, that was solved by clearing out the CONFIG_PASSWORD in the docker-compose.yml Now I have hummingbot loaded up, I am looking to actually load the V4 DyDx and play with it. Any suggestions welcome on getting started on this. |
Hi @lukebyrne Note: both setup below share same folders for configs, logs and scripts
For docker build
|
Great I am up and running.
I don’t see anyway to connect to DyDx V4?
I can see the dydx_perpetual but my understanding is that’s the old V3 api?
…On 24 May 2024 at 3:10 PM +0800, hummingbot/hummingbot ***@***.***>, wrote:
docker attach hummingbot
|
Please recheck the instructions above and change the Please see recording below on connecting to dydxv4 |
@rapcmia thanks for the update, I needed to switch the right git branch |
Hey @yancong001 have you had any luck fixing the injective and dydx conflicts? I am trying to use a cross-dex strategy with both... Found a bit of a hacky way to get Description: My understanding of the issue is that the Since injective and dydx are both cosmos chains and have some overlap in terms of the packages, e.g. However, as they are running both slightly different versions of cosmos-sdk ( Solution: IT'S A HACK AND I AM NOT PROUD. To solve this I simply ensure all the duplicate protos being registered are identical. Thus I run the following script that replaces #!/bin/bash
# Directories to copy from and to
SRC_DIR="/path/to/anaconda3/envs/hummingbot/lib/python3.10/site-packages/v4_proto/cosmos"
DEST_DIR="/path/to/anaconda3/envs/hummingbot/lib/python3.10/site-packages/pyinjective/proto/cosmos"
# Ensure source directory exists
if [ ! -d "$SRC_DIR" ]; then
echo "Source directory $SRC_DIR does not exist."
exit 1
fi
# Ensure destination directory exists
if [ ! -d "$DEST_DIR" ]; then
echo "Destination directory $DEST_DIR does not exist."
exit 1
fi
# Copy directories and files
for dir in $(ls "$SRC_DIR"); do
if [ -d "$SRC_DIR/$dir" ]; then
echo "Copying directory $dir from $SRC_DIR to $DEST_DIR"
cp -r "$SRC_DIR/$dir"/* "$DEST_DIR/$dir"/
fi
done
echo "Copy complete." Thus far I am able to perform all queries (e.g. balances and market data) without any issues. HTH Outro: I guess solving this is kinda important since any other cosmos chains that integrate through a connector would likely face the same issue right? (e.g. Hyperliquid soon) |
Before submitting this PR, please make sure:
A description of the changes proposed in the pull request:
This PR create dydx v4 connector to the latest standards.
Tests performed by the developer:
Tips for QA testing: