Engineering — stack, API, fingerprints

Inferred from public repos, docs, and HTTP. The platform itself is closed-source.

Stack

Who built it

The snapshot client still pointed at https://01resolved.var-meta.com/api/v1 (Vietnamese IP). A May 26 docs commit moved /api/v1//v1/ for production. VAR META (~50 engineers, Hanoi / Da Nang) built the backend. Lead engineer here means bringing that codebase in-house.

Dune is a second source: the snapshot microsite caches Dune queries (2h refresh) for protocol metrics (e.g. Omnipair) alongside their Treasury Intelligence API.

James also uses Radix/shadcn, framer-motion, TanStack Query, wagmi/viem (EVM fluency) in other repos. Upstream: metaDAOproject/programs (Anchor).

API surface (~86 GET endpoints)

No POST/webhook/stream yet — alerting is Telegram-only.

Slug vs project params are inconsistent across groups — organic growth; a v2 coherence pass is the obvious first cleanup.

Tracked slugs

Ownership coins: metadao (META), avici, solomon (SOLO), p2p-protocol, umbra, omnipair (OMFG), loyal, jurassic-finance (RAWR), paystream (PAYS), zklsol (ZKFG), superclaw, futardio-cult, rip-cars, credible, kimia, ordr.trade, laso-finance, areal-finance, basket, gesim, kollan-house, kyros, coal.

Established DAOs: jito-dao, sanctum, drift, marinade, save-dao, island-dao, mtncapital, ore, ranger (liquidated), flash-trade (winding down), futuredao.

Shipped catalog: src/projects.js.

Rough edges

All research