GithubHelp home page GithubHelp logo

Comments (5)

cjdsellers avatar cjdsellers commented on June 12, 2024

Hi @dimitar-petrov

Thanks for bringing this to my attention, it should now be fixed from 6f96865 on develop branch.

I was able to run two Binance data clients, and two Binance execution clients. Let me know how you go when you get a chance.

from nautilus_trader.

dimitar-petrov avatar dimitar-petrov commented on June 12, 2024

@cjdsellers,

I had some time to test simultateous connections to SPOT and PERP on binance and the following issue arised:

2024-04-21T16:01:41.603724782Z [INFO] SPOT_PERP_MM-104.BinanceWebSocketClient: Connected to wss://fstream.binance.com
2024-04-21T16:01:41.603833564Z [INFO] SPOT_PERP_MM-104.DataClient-BINANCE_PERP: Subscribed trades WUSDT.BINANCE
2024-04-21T16:01:41.609275961Z [INFO] SPOT_PERP_MM-104.DataClient-BINANCE_PERP: Subscribed quotes WUSDT.BINANCE
2024-04-21T16:01:41.609327651Z [INFO] SPOT_PERP_MM-104.DataClient-BINANCE_PERP: OrderBook snapshot rebuild for WUSDT.BINANCE @ depth 1000 starting
2024-04-21T16:01:41.897892729Z [INFO] SPOT_PERP_MM-104.DataClient-BINANCE_PERP: OrderBook snapshot rebuild for WUSDT.BINANCE completed
2024-04-21T16:01:41.898032915Z [INFO] SPOT_PERP_MM-104.DataClient-BINANCE_PERP: Subscribed order book deltas WUSDT.BINANCE depth=0

Looks like instruments cannot be routed to correct data provider for subscription, since VENUE for both binance spot and perp is the same.

Maybe PERP and SPOT exchanges should be treated as different venues.

from nautilus_trader.

cjdsellers avatar cjdsellers commented on June 12, 2024

Hi @dimitar-petrov

Yes, this is known and currently the intent is that you would add your two client sets for SPOT and FUTURES, then use the client_id param for commands to specifically route to those clients, e.g.

client_id=ClientId("BINANCE_PERP")
    cpdef void subscribe_quote_ticks(self, InstrumentId instrument_id, ClientId client_id=*)

from nautilus_trader.

dimitar-petrov avatar dimitar-petrov commented on June 12, 2024

@cjdsellers, thanks for the clarification.

I did not notice that client_id was added to the subscribe methods.

from nautilus_trader.

cjdsellers avatar cjdsellers commented on June 12, 2024

Yes, client_id has actually been in the API a long time as well. 👍

from nautilus_trader.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.