[ANN] Whale Core: Zero-Latency Binance Futures Liquidation & CVD Tracker

[aallexf]

Hello Bitcointalk community,

I want to share a technical project I’ve been building from scratch called Whale Core.

If you trade Binance Futures, you know that during high-volatility events (liquidation cascades, stop-hunts), standard REST APIs become completely useless due to rate limits and latency. By the time your indicator parses the data, the move is already over and retail becomes exit liquidity.

To solve this, I built a custom Python asyncio engine that connects directly to the raw Binance WebSocket streams.

What it does differently:

Zero-Latency Parsing: Processes thousands of events per second without dropping packets or starving the event loop.
Liquidation Isolation: Catches aggressive stop-hunts (e.g., catching a single $500k liquidation order) the exact millisecond it happens on the exchange matching engine.
CVD Anomalies: Tracks Cumulative Volume Delta in real-time to spot when algorithmic market makers are absorbing retail momentum.
I've put this engine behind a clean dashboard so you don't have to write your own WebSocket handlers to see the data.

Check out the live terminal here: sigma-liq.fun See how it works (YouTube demo): youtube.com/watch?v=G8vAjxQG0t4

I am constantly optimizing the backend architecture. If there are any algorithmic traders or Python devs here, I would love to hear your feedback on handling extreme websocket loads during high volatility, or any metrics you'd like to see added.

Happy trading!

[Charles-Tim]

So how is it going to be useful to traders?

Anyone that uses high leverage would have been liquidated during volatile market regardless of the tools that he is using to track liquidation.

Another thing is that you are not trusted on this forum.

[shinratensei_]

So how is it going to be useful to traders?

Anyone that uses high leverage would have been liquidated during volatile market regardless of the tools that he is using to track liquidation.

Another thing is that you are not trusted on this forum.

Might be useful for traders who hunt massive liquidity even and buy at bottom, Binance's REST API was returning 503 temporary service unavailble when the 10/10 occurred and caused cascading liquidation, some traders who created their own tool and used the REST API can't execute orders.

That being said, even websocket stream isn't necessarily free of that error, the solution by OP if not useless is unproven because you won't know until another cascading liquidation event happened again and see if there is an error or the same 503 that disabled REST API use on the Binance's websocket, the environment is hard to replicate. Moreover, you can easily create one just like what OP have with AI. No need to trust random person on the internet.