In production
The terminal we shipped to production.
Verdict is an outcome-markets terminal built on Hyperliquid HIP-4 and running at verdict.pm. It is the reference build for this studio: a real front end over a live venue, with the order book, the portfolio and the settlement path that a trading interface actually needs.
Status
Live In production on mainnet, with a testnet instance alongside it.
Venue
Hyperliquid HIP-4. Orders route to the venue, we never take the other side.
Economics
A 0.05% builder code on routed orders. No listing fee, no spread of ours.
Custody
None. Users sign with their own wallet.
What it took to build
A terminal is not a dashboard. Most of the work is in the parts that only show up when a venue is live and someone is watching a position.
Live data plane
Websocket mids and trades, order books, candles, all read-only and cached with request coalescing so a busy screen does not hammer the venue.
Order signing
Orders signed in the browser against the venue's exchange endpoint, including the builder-fee approval flow that has to happen before the first trade.
Portfolio and settlement
Positions read on chain, settlements resolved from fills, and paper positions settled at expiry so nothing dangles.
Failure handling
Watchdog on the websocket, timeouts on every fetch, tolerant boot when the venue is unreachable, and generic errors that never leak internals.
Workspace layout
Three columns: market list, market with chart and book, permanent ticket. Risk, break-even, slippage and payout computed in the ticket before anything is signed.
Jurisdiction handling
An attestation gate at first visit, and geoblocking sitting dormant behind a flag, ready if counsel calls for it.
Why we run it ourselves
A terminal on a live venue teaches things a design file never will, and it pays for itself without anyone having to buy it.
Related reading
Trading outcome markets?
Verdict is open at verdict.pm. If something is missing or broken, tell us.