Notional
Maintaining the CLOB trading system that settles and finalises trade execution on Hyperliquid, and shipping a Polymarket integration that lets prediction-market bets settle on the same rails.
The system
Notional runs a central limit order book (CLOB), the same matching model used by traditional exchanges, where buy and sell orders are ranked by price and time priority and matched directly against each other, rather than against a liquidity pool. My work has been maintaining the parts of that system responsible for operating, settling, and finalising trade execution on Hyperliquid and its HyperCore EVM.
That's a different job from writing the matching engine itself: it's making sure that once two orders match, the trade actually clears: positions update, balances settle, and the on-chain and off-chain views of the book never drift out of sync under load.
Extending it: Polymarket on Hyperliquid
I designed, implemented, and shipped to production a Polymarket integration on top of that infrastructure, letting Notional users place prediction-market bets that settle and execute on Hyperliquid rather than requiring a separate venue. That meant threading a market type with fundamentally different resolution logic (binary outcomes resolved by an oracle, not continuous price discovery) through a settlement pipeline that was built around conventional trade execution.
A settlement layer only earns the right to carry more product on top of it once it's proven it won't lose track of a trade under load. Polymarket-style markets are a second product line running through the same settlement path I maintain. That's only possible because the underlying pipeline had already earned enough trust internally to extend, rather than needing a separate system built beside it. Extending existing infrastructure instead of duplicating it is the difference between shipping a new revenue line in weeks and shipping it in quarters.