← ALL WORK · CASE 01
MOXAT
Custodial USDT payments and escrow for transactions where the two sides don't trust each other yet — and shouldn't have to.
ESCROW STATE MACHINE — EVERY TRANSACTION WALKS THIS PATH
DISPUTED → FUNDS HELD → ARBITRATED RELEASE — NO UNILATERAL EXIT
01 — WARP
What had to be true first
Custody is a liability before it is a feature. Before any interface existed we set the wallet infrastructure: segregated custodial wallets, a double-entry ledger for every USDT movement, and an escrow engine whose states — created, funded, in escrow, released, settled — are the only paths money can take. There is no admin override that bypasses the ledger.
02 — WEFT
What we wove through it
Onto that warp we shipped the product in weekly passes: wallet provisioning and deposit detection, automated escrow workflows triggered by delivery conditions, a dispute flow that freezes funds instead of guessing, and a settlement view where both sides watch the same state — because it is the same state.
03 — BEAT
How it was pressed tight
Every merge was beaten in: review on the money paths, deterministic tests on every escrow transition, and rehearsals of the ugly cases — double deposits, partial funding, disputes raised mid-release. The code that guards funds is boring by design.
04 — WEAR
Life in production
MOXAT runs in production today. Wallet infrastructure, escrow workflows and settlement operate unattended, and disputes take the arbitrated path we designed instead of a support ticket. Cloth, being worn.
NEXT CASE — 02
GM SWAP →