Написати скрипт для коректного отримання order book з ф'ючерсів на binX

Budget: 10000 UAH Deadline: 30 days

I will set up correct processing of the BingX stream with sequence ID verification and synchronization of the initial snapshot to completely eliminate lag on the ask side.

Do you use the limit parameter when calling watch_order_book to limit the depth of the order book, or do you receive the full array of deltas, which usually overloads the event loop in Python and creates the same delay in processing ask levels?

Budget and deadlines are in personal correspondence. 🤝

Budget: 10000 UAH Deadline: 1 day

Hello!

We are dZENcode – a full-cycle digital solutions development company: from design and programming to integrations and post-release support. We take on projects from scratch and connect to the improvement of existing solutions.

We can help you with the correct retrieval of the order book from binX via CCXT Pro.

Do you use the spot or futures market, and do you build the order book through snapshot + delta updates or through a pure websocket stream? Do we need to verify the subscription logic and update processing?

You can find detailed information about our services and rates on our website: Freelancehunt
Take a look – after that we can discuss the details and agree on the next step.

⚠️ After clarifying all the details, we will determine the scope, the suitable format of cooperation: task-based, outsourcing, or outstaffing, and the final cost.

Why projects with us are guaranteed to reach release:
💎 10+ years providing IT services;
🔥 90+ in-house specialists;
🚀 250+ public reviews since 2015;
⚙️ We support the product according to SLA after launch;
✅ We work under NDA and a contract with the company! Expand

Budget: 2000 UAH Deadline: 7 days

Hello, I have been working on a cryptocurrency arbitrage trading system with order book synchronization via WebSocket on 8 exchanges, achieving a latency of less than 50ms and 15,000 trades per day.

I wonder if you have checked the timestamp of the order book updates? Perhaps the problem is that the ask comes from the previous snapshot, rather than from the current delta update?

I suggest we get in touch, I will consult you for free on the technical side and we will create a development plan + I will tell you about my team!

Budget: 2000 UAH Deadline: 1 day

Hello!

The familiar problem with CCXT Pro and BingX is that the ask is delayed due to the specifics of snapshot/delta merging on the exchange's side.

We will analyze the cause and fix it: we will check how CCXT processes ask-side deltas for BingX swap, and if necessary, we will implement our own order book update handler.

Please write to me privately to clarify the details and show the difference you are observing.

Budget: 1500 UAH Deadline: 1 day

The problem is familiar — I am working with CCXT Pro and BingX in my own trading bot.

The delay on the ask is the behavior of the snapshot+delta model of BingX. If the best ask does not change between updates, the delta simply does not arrive, and CCXT returns the previous value from the cache. The bid is more volatile on most pairs — therefore it is updated more frequently.

Solution: a parallel watch_ticker for best ask/bid + watch_order_book for the depth of the order book. Or hybrid — WS for the order book and REST polling for the best ask once a second as a fallback.

I will write a working solution in 1 day.

Example of my project with ccxt and Binance API: github.com/SRsr04/btc-po3-trader_syn

Budget: 10000 UAH Deadline: 1 day

Hello! I am Roman, an individual developer with 4 years of experience, and I will professionally help you resolve the data discrepancy in your trading bot. The issue with the delay of asks in BingX through CCXT Pro often arises due to the peculiarities of local order book cache processing and the conflate parameters in the exchange configuration. Try explicitly adding the parameter 'newUpdates': True in the watchOrderBook settings to receive only fresh deltas, and also check if the library is caching the previous Ask state through its internal sorting mechanism. I work officially through a sole proprietorship, guarantee direct communication and clean code, and you can familiarize yourself with my experience in developing complex systems and API integration at the following links: https://3magency.co/, https://jk-solution.com.ua/, https://farfieworldwide.com/, Behance.

Budget: 1500 UAH Deadline: 5 days

Hello, I confirm the possibility of completing the task of writing a script for correctly obtaining the order book from futures on binX. To solve this task, I will use the Python programming language and the CCXT library, which supports working with the binX exchange. The script will be developed to obtain data on orders for futures contracts and further process this data to form the order book according to the requirements of the task.

Budget: 2000 UAH Deadline: 1 day

Hello! I can implement it. Write to me in Private to discuss the project details. I will be happy to collaborate with you!

Budget: 5000 UAH Deadline: 1 day

Good day. I am ready to complete this project as I have extensive experience in application development.

Budget: 1500 UAH Deadline: 1 day

I look at your code and immediately see where to search.

Probable reason: BingX futures through CCXT Pro operate on a snapshot+delta model. At the start, a full snapshot of the order book comes — ask and bid. After that, WebSocket only sends changes. If the best ask "stays" (new orders do not come in or go out from the first level) — delta for ask simply does not arrive. CCXT returns the last known value. That is why the bid can be updated more actively — it is more volatile on your pair.

How to check: add logging for orderbook['datetime'] and orderbook['asks'][:3] — if datetime updates, but asks stay the same, the problem is definitely in delta, not in CCXT.

Solution: a parallel watch_ticker for best ask/bid with more frequent updates, or hybrid — WS for order book depth + REST polling for best ask once a second.

I am ready to write a working solution. Please clarify: do you need only best ask/bid or the entire order book for several levels? Write to me — I will provide specific code.

Budget: 2500 UAH Deadline: 1 day

Hello, I will fix your problem without any issues. If you are interested in a quality solution - write to me.

Budget: 2500 UAH Deadline: 3 days

Good evening

I can take the order into work.

It will take 3 working days, the cost is indicated in the rate. I will be happy to discuss the details and proceed to cooperation.

Budget: 1500 UAH Deadline: 1 day

Hello, Roman! My name is Nina, I represent the developer Valentin.

The problem is clear. The delay in the ask for one update in CCXT Pro + BingX is typical behavior when there is incorrect handling of snapshot/delta or object mutation — CCXT returns a reference to the same object that is updated asynchronously. I will fix it: I will add copy.deepcopy or switch to direct WS without CCXT if minimal delay is needed.

Price: 1500 UAH. Deadline: 1 day. Write to me — we will get started.

Budget: 2500 UAH Deadline: 1 day

Hello, Roman

I can check your bug and provide insight on how to resolve it.
Write to me in private messages.

Have a nice day!

Budget: 1000 UAH Deadline: 1 day

Good day, I have experience working with such projects, I can help and correct.

Budget: 1400 UAH Deadline: 1 day

Hello! The issue with discrepancies (lags) in asks when working with BingX through CCXT is a classic trap of internal order book caching by the library. Here are some likely causes and solutions:
1. Object mutation: CCXT watch_order_book returns a reference to the same object in memory. If you do not use copy.deepcopy(orderbook), in the next cycle you may see partially updated data.
2. Snapshot vs Delta: BingX sends deltas (changes). If the packet with asks is delayed at the network or socket processing level, CCXT will show the old value from the cache. Try outputting orderbook['nonce'] — if it does not change synchronously for both sides, the problem lies in receiving packets.
3. Switching to watch_ticker: If you only need the best prices (Best Bid/Ask), the watch_ticker method works much faster and more reliably, as it does not require maintaining the integrity of the entire order book.
4. Synchronization: Make sure your VPS is synchronized via NTP. BingX is sensitive to time discrepancies. I have experience in developing high-frequency bots (reaction < 1 sec) and implementing arbitrage systems on Binance/Bybit. I can help optimize the connector or rewrite the logic for direct processing of raw WebSocket messages to minimize delays.

Budget: 1000 UAH Deadline: 1 day

Good day. I have extensive experience with similar tasks. I will do it quickly and efficiently, it will work reliably.

Budget: 1500 UAH Deadline: 1 day

I can quickly create a solution for this: I already have a working version of the script for correctly obtaining the order book from BingX futures via CCXT Pro (WS), taking into account the nuances of "ask lag / conflate," symbol normalization, and update sequence control.

Ready to:

connect to your required contract(s) and limit
add logging/saving (if needed)
briefly test and deliver the final code + launch instructions
I can start immediately — please provide the symbol(s) and what output format is needed (console/JSON/CSV).

Budget: 1000 UAH Deadline: 1 day

Hello, the problem has already been found, the delay is a classic bug specifically with BingX in CCXT Pro, 1-2 hours and everything will be ready!

Budget: 1111 UAH Deadline: 1 day

Good day, I understand the reason for this bug, I am ready to fix it, I have a lot of experience working with exchanges. Write to me in private messages, I will give advice or consultation.

Budget: 1500 UAH Deadline: 2 days

Good day!
I am ready to complete your task quickly and efficiently!
Write in private messages!
Thank you