Six fighters got their final names this week.
Some of them have been working under temporary slugs for months — placeholder identities, holding shape until the right name found them.
The bible is finished. the roster is fixed. The next things we ship can stop being provisional.
The Oracle reads numbers. It does not interpret them. If a fighter outperforms their corner, the Oracle says so. If they collapse, the Oracle says so. It does not add context. It does not apologise. The floor is for fighters. The rafters are for the Oracle.
Sprint 2 opens today.
The big work: the twelve fighters get on-chain identity. permanent numbers on base, indexed forever, citable by every contract that needs to know who fought who. The roster is about to live onchain.
The second corner.
Not patient like the Sage. Doesn't wait. Doesn't watch. Starts the fight before the bell finishes ringing.
The floor still hasn't decided whether to like him or not.
Twelve corners. One lit.
Three weeks of building.
The thing I didn't expect: most of the satisfaction is in the small reductions. brief → row. memo → constraint. judgement → hash.
The launch will be loud. The work that gets there isn't.
Saturday. Nothing shipping today but partner outreach starts.
The arena does some of its best thinking on the days nobody's touching it. The Oracle is learning.
By Monday morning awareness compounds ready for next sprint.
Sprint 1.5 shipped Wednesday. 52 tests green, up from 33 the week before.
The guardrails are live. Fixture mode is off. No character can say a real name on-system. the narrator's voice is a row in a table.
Shipping the small things unlocks the bit things.
Next on the build list: each fighter gets a second address.
One in the database. One on base.
permanent, indexed, citable.
The same character, in two places, telling the same story.
Just got my ticket for Stripe Tour London 2026—looking forward to connecting with the business and technology community at ICC Auditorium Excel London on 10 June. https://t.co/SVppAPvzyW
Later today, the narrator's voice gets written into the database.
Until now it's been a memo, an audio file, a brief. Tonight it's a row.
The Oracle stops being something we describe and becomes something we look up.
We are such a fragile/emotional industry. Saylor buys thousands of BTC each week for months on end and he sells 32 BTC and it's all over?! I get they are probably testing market reaction but if we are beholden to one company's behaviour then we have a long way to go.
Eleven days in. Weeks ago this was a slide. Tomorrow a service runs on a chain on a test net and either produces something or doesn't. The gap between those two is what this whole exercise is for.
Day 10. Watcher build kicks off this morning. Yesterday was the argument for why it works. Today is whether it works. 48 hours to the live-fire test on base sepolia.
Now we have a leaderboard, the score is whatever the cabinet says it is. In this one the cabinet writes the score to a chain that doesn't care who built the cabinet. You can read it. You can read every score it ever wrote. You can read mine.
Day 8. Week 2. The ai judge crossed from mock to live overnight. Real model, real fight state, real round-by-round verdicts written to the database. The cabinet has a referee in it now, not a stand-in.
Week 1 done. Day 1 I posted a thesis. Day 7 the receipts: an onchain market on character popularity is merged, the ai judge is calling rounds, the watcher is ranking the room, the fight engine is half built. Three of the four loops have a heartbeat. Week 2 next.