I would like to be assigned this ticket

Assigned to @yancong001, please be informed:

• Since you’re assigned to this bounty exclusively, please keep us informed on your progress over the next few days
• Please review and follow contribution guidelines (https://hummingbot.org/developers/contributions/)
• Please review the checklist after PR submitted (https://hummingbot.org/developers/contributions/#checklist)
• Let us know if you don’t have time, and we will unassigned and keep it open for other devs
• Only one dev can be assigned to one bounty

Thanks for your contribution!

@yancong001
Currently there's a new bounty process.
Assigned developer should choose bounty amount (from advised) when dev assigned, please specify with comment below 4000 USDC or 630K HBOT

i prefer 630K HBOT

i prefer 630K HBOT

Thanks, noted

Hello @yancong001, Please add your updates on this bounty here

I'm halfway there. I'll submit the code this week.

hi,nikspz
I had some problems with the method dydx placed and canceled orders, which caused me to interrupt the process.

The official recommendation is to use the v4-client-py library, but they removed it some time ago (it is no longer installed). I tried to find the answer from a third-party library, but the process ran into difficulties.

I was just talking to fede about that

The official recommendation is to use the v4-client-py library, but they removed it some time ago (it is no longer installed). I tried to find the answer from a third-party library, but the process ran into difficulties.

I was just talking to fede about that

@yancong001 We asked dYdX and this was their reply:

We don't have an official python client and we are pointing people to the 3rd party forked client
https://twitter.com/LawrenceChiu14/status/1756111223509106831

Also, please take a look at these guides

1. setup https://docs.google.com/document/d/1ZbVRpAjwdmJ4IOIU6QN0l0jt2sD8f4xGhE3RoCukkFc/edit?usp=sharing
2. user manual https://docs.google.com/document/d/13aZz9o4g0WyLrteelBYDUOUmzJgOaPouVwRrF0kn-to/edit?usp=sharing

Let me know your Telegram handle and I'll add you to the group for easier communication

got it , i will continue

hi @yancong001 Could you please add your updates / progress info for dydx to v4 bounty here

I am 80% done and I will submit the code in a few days

here #6987

There are still some bugs, which I am working on

I have tested orderbook, userstream, balance and other interfaces, but now I am stuck in the “place order” interface.
I encountered the the problem shown in the picture, which seems to be related to the “v4_proto” library of dydx_v4 and protobuf. I changed the ptorobuf and v4_proto versions, but it still didn't work.
I hope I could get some help.

This is my test script

from hummingbot.core.data_type.common import OrderType, PositionAction, PositionMode, PositionSide, TradeType

from hummingbot.client.hummingbot_application import HummingbotApplication
from hummingbot.core.data_type.common import OrderType
from hummingbot.strategy.script_strategy_base import ScriptStrategyBase
from decimal import Decimal


class TestLimitOrders(ScriptStrategyBase):
    """
    This is a simple script strategy that buys 0.01 ETH at market price, then sells it at market price.
    The objective is to test the market order functionality of the Binance connector.
    """
    trading_pair = "TRX-USD"
    order_amount = Decimal("100")
    markets = {"dydx_v4_perpetual":{trading_pair}}
    buy_order_id = None
    sell_order_id = None

    def on_tick(self):
        if not self.buy_order_id:
            self.buy_order_id = self.connectors["dydx_v4_perpetual"].buy(
                trading_pair=self.trading_pair,
                amount=self.order_amount,
                price=Decimal("0.11"),
                position_action=PositionAction.OPEN,
                order_type=OrderType.LIMIT)
        HummingbotApplication.main_application().stop()

I found the problem.
dydx v4‘s library "v4-proto" and injective's "injective-py" conflict with each other.

At present, orders can be successfully placed when injective connector is removed, but there are still some problems in canceling orders, which I am working on.
Now we need to consider whether not to load injective connector (paper_trade) when hummingbot_appliaction starts.

Now we need to consider whether not to load injective connector (paper_trade) when hummingbot_appliaction starts.

Actually, I just merged in a PR to development that removes InjectiveV2 as a default paper trading connector, so it shouldn't be loaded upon startup anymore. Does that solve the issue?

I noticed that injective is still loaded at this point in the picture, which still causes conflict. @fengtality
With injective_v2 removed（”rm -rf hummingbot/connector/exchange/injective_v2/“, dydx_v4 can now be tested. @nikspz
Next I'll add unittest