About
Who built this
I am a backend and blockchain engineer. I have built more than twenty applications, and I currently work as a backend and infrastructure engineer at a startup serving roughly half a million active users. My depth is in distributed systems, scalable architecture, and the parts of a product that are invisible when they work.
That is what Ninety is really made of. The single-writer engine with journal-then-ack, the two-plane event bus, the polyglot quant worker, the on-chain verification path, the two-source data law, the 87 decision records — that is the part I know how to do well, and it is why the system holds together on free-tier infrastructure.
The interface is not my home ground. I am a backend engineer, and the frontend was built fast, with heavy AI assistance, against a strict design system that kept it coherent. I would rather say that plainly than pretend otherwise. What it demonstrates is that a backend engineer with a rigorous design system and modern tooling can ship a consumer-grade surface — and that the architecture underneath it is the real work.
#The honesty thread
Two decisions in this project matter more to me than any feature:
We fail-closed on settlement. We found the sponsor's proof could not bind match finality on-chain, proved it forgeable, and switched settlement off rather than ship it. It cost us a headline feature.
We never fabricate data. Where the interface shows a replay rather than a live feed, it says so. Where a market cannot be priced honestly, it stays unpriced instead of printing a plausible-looking number.
Both come from the same instinct, and it is the instinct I would want judged.