tjwells's comments

On: Show HN: Onyx – Trading Terminal for Polymarket

[tjwells]

Hi HN, I’m currently building an all-in-one trading terminal for Polymarket.

The Problem: Polymarket is now doing billions in volume, but the native web interface is built for retail. It lacks basic execution tools, has UI latency, and doesn't support stop losses. When trading volatile events, that click-latency leads to significant slippage.

The Solution: I built Onyx to treat prediction markets like traditional financial markets. It'll feature fast execution, advanced risk management, and in depth analytics.

I'm planning on launching a closed beta soon so would love if anyone could join the waitlist and help provide feedback.

On: Show HN: C++ order book matching engine (3.2M orders/SEC, ~320ns)

[tjwells]

currently it just handles standard limit and market orders, with price-time priority

On: Show HN: C++ order book matching engine (3.2M orders/SEC, ~320ns)

[tjwells]

I’m a student interested in market microstructure and low-latency systems. I built Mercury to learn how matching engines work under the hood.

It’s a single-threaded C++ engine that achieves ~320ns insertion latency and 3.2m+ orders/sec throughput.

Technical details:

Memory: Everything is pre-allocated. No new/malloc on the hot path.

Data Structures: I wrote a custom Robin Hood hash map and intrusive lists to keep order management O(1) and cache-friendly.

Architecture: It includes a pre-trade risk check and a backtester.

The code is obviously not production-ready for a real exchange, but I’d love feedback on the C++ implementation and memory layout.

Repo: https://github.com/eelixir/mercury