“Half-day prompt job” is what people say right before they ship something wrong, unreproducible, and quietly broken the moment HiveSQL/RPC behavior changes.
A front-end is not the product. The product is a durable, auditable pipeline + public dataset that stays correct over time.
Funds are for:
Hardening the data pipeline (HiveSQL + RPC reconciliation, integrity checks, deterministic rebuilds)
Operating the public dataset (scheduled rebuilds, monitoring/alerts, caching, hosting/uptime)
Auditability (versioned JSON outputs, changelog, methodology docs, reproducible scripts)
Product completion (deeper account drilldowns, per-proposal breakdowns, exchange-flow labeling, UI clarity)
Maintenance work (bug fixes, adapting to upstream API/SQL changes)
Also: nobody said “a .com costs 8k.” That’s a strawman. A domain is not the budget.
If it really was “half a day,” this would already exist and remain correct and be openly auditable.
It didn’t. So this is what real work looks like.
RE: Who Is Printing Hive, Who Is Getting Paid, and How Much?