Ledgerline
A live market interface that holds still while the data underneath moves — because the interface is not the news.
A trading interface has to do two contradictory things: stay current to the millisecond, and stay calm enough to read.
Ledgerline solves the contradiction by separating the stream from the surface. A multiplexed Binance WebSocket feed runs in a worker, parses every frame into typed updates, and pushes those updates through a buffered queue. The interface — candles, order book, trades tape, ticker stats — subscribes to that queue at the rate it can actually render, not the rate the wire delivers. The market doesn't dictate the frame rate. The frame rate dictates what the market is allowed to show.
That single architectural decision changes everything downstream. The order book stops flickering, because rows that update faster than the eye can register are coalesced. The trades tape stops jumping, because new rows fade in over 120 milliseconds instead of teleporting. Candles stop redrawing on every tick, because the chart subscribes to a once-per-second aggregate. The page reads as still, even though the data underneath it has changed five hundred times since you started this sentence.
The telemetry layer is the second half of the work. Ledgerline measures dropped frames, queue depth, parse latency, and reconnect cycles, and surfaces them in a small developer panel that you can pop open with a keyboard shortcut. The product is a chart. The instrumentation is what lets me trust the chart.
“The market doesn't dictate the frame rate. The frame rate dictates what the market is allowed to show.”
The stream runs in a worker
WebSocket parsing, multiplexing, and queueing all happen off the main thread. The render thread receives typed batches at a cadence it can actually paint.
The order book coalesces, the tape fades
Updates that arrive faster than the eye can register collapse into one render. New trades fade in over 120ms. Stillness is engineered, not accidental.
Telemetry is a keyboard shortcut
Press ? and a small panel surfaces queue depth, parse latency, dropped frames, and reconnects. The instrumentation is shipped with the product, not bolted on after.