Architecture

One launch transaction

1. Commit canonical metadata and bind hosted registration to a signed creator acceptance.
2. Deterministically deploy an unrestricted fixed-supply token ending in …1111.
3. Create and initialize the canonical 1% WETH v3 pool.
4. Mint one-sided liquidity using the complete supply and transfer the NFT to the permanent locker.
5. Optionally execute the creator’s initial buy with slippage protection and no wallet cap.

Trust boundaries

Contracts

Ownership, supply, pool, lock, and fee routing

Chain logs

Canonical event history and rebuild source

PostgreSQL

Rebuildable read model; never custody

Redis

Disposable cache and realtime fan-out

Hosted media

Moderated presentation content; not ERC-20 identity

Wallet

Signs acceptance and transactions; service never holds keys

Data flow

Robinhood Chain logs
  -> append-only raw log store
  -> reorg-aware projections
  -> PostgreSQL read model
  -> REST + Server-Sent Events
  -> web discovery and token detail

Pending and confirmed state remain distinct. Robinhood L2 height and Ethereum L1 block.number are stored as different concepts.