Stack
Foundry contracts on Robinhood Chain, direct event-level indexing with no third-party indexer in the critical path, Neon Postgres, and a Next.js frontend.
- Contracts — Foundry, Robinhood Chain mainnet
- Indexing — direct factory-event discovery over RPC. No third-party indexer in the critical path; event-level indexing is roughly an order of magnitude faster than the hosted alternatives on this chain and does not go down when they do
- Data — Neon Postgres: specimen index, epoch history, distribution ledger, event results
- Frontend — Next.js + viem/wagmi on Vercel
- Art — 32×32 native, deterministic composite, state-aware render from an edge function with aggressive cache invalidation on state-change events
"No third-party indexer in the critical path" is specifically about the read path that the terminal and the distributor depend on to function — not a blanket refusal of hosted services elsewhere. Direct factory-event discovery means listening for the events DsupSpecimen.sol and DsupDistributor.sol already emit (transfers, state changes, epoch settlements) and rebuilding index state from them, rather than depending on a hosted indexer's uptime and lag to know whether a specimen is currently in tun. The art render's cache invalidation has to be event-driven for the same reason §10 requires state-reactive art at all: a cached image of a specimen that just broke tun is a wrong image, not a slightly stale one.