Built a second copy of the allocation data from on-chain events only, no subgraph involved
At Arbitrum One block 510,395,917 it reports the same 14,415 active allocations as the network subgraph, matched by allocation ID
ID lists and the commands to rerun it: graph-allocations-nest/verification/2026-09-30 at main · nightswatchhq/graph-allocations-nest · GitHub
(checked against a grafted deployment of the network subgraph, not the canonical gateway one)
Its a nuthatch nest, so one binary and SQL over the events.