
Overview
The problem it is built against
Design in an adversarial context
- The interface is monospaced and typographic, closer to a terminal than a fintech app. That is not nostalgia. Numbers in a proportional font are harder to compare at a glance, and this is a screen where misreading a number costs money.
- Mechanics are stated, not marketed. The information page leads with how graduation works and what the owner can and cannot do, rather than with returns. In a category built on hype, describing the constraints is the pitch.
- Loading states are designed, not absent. Chain data arrives late and out of order. Skeleton cards and an explicit "loading feed" state exist so a slow block never reads as a broken page or, worse, as a zero balance.
- The launch flow is a form that explains itself. Choosing between bonding-curve mode and instant-listing mode is the most consequential decision a creator makes, so both options are described in full at the point of choice rather than in documentation.
What the owner cannot do
runner.owner() == timelock has been verified on-chain.
Writing down what you cannot do is more useful than listing what you promise not to.
Architecture
Technologies used
- Contracts: Solidity 0.8.30 with Foundry, compiled via-IR; unit, fuzz and invariant test suites.
- Frontend: Next.js with wagmi v2 and viem for chain interaction, TanStack Query for data, lightweight-charts for price charts.
- Extras: LiveKit for live audio in the trading rooms, React Three Fiber for visual pieces, Supabase for off-chain data.
- Infrastructure: Netlify with Blobs for the indexer snapshot; a Safe behind a timelock controller as contract owner.
- Operations: deployment runbook, on-chain verification bundles, and a solvency check script.
