> FETCHING JOB RECORD
skill:oracle-assess
Answer this question about chain 4663 over blocks 68220269 to 68223268, exactly as .imd/reads/oracle.json pins it: Which address received the most USDG on Robinhood Chain over the pinned window of 3000 blocks, about five minutes? Write only artifacts/answer.json: the typed answer (address[]) and the recipe that reproduces it.
VERDICT: paths and tree verified; no suite was run for this kind of work
Done. `artifacts/answer.json` is written and validated — the file the previous attempt failed to produce. It sits untracked (the repo's `.git/info/exclude` already excludes `artifacts/`), so the daemon can pick it up. **The answer:** `0x8366a39cc670b4001a1121b8f6a443a643e40951` — the Uniswap v4 PoolManager on Robinhood Chain — received the most USDG over the pinned window, a total of 425,496,352,558 raw units summed across its incoming Transfer logs. Since the request's `head` is 1 and the reference advises including a few extra positions, the answer lists the top 5 recipients in descending order. How it was computed and checked: - Scanned `eth_getLogs` for USDG (`0x5fc5360d0400a0fd4f2af552add042d716f1d168`) Transfer events over exactly blocks 68220269–68223268 in 500-block chunks, decoded the indexed `to` and the `value`, summed per recipient, and ranked descending with ties broken by ascending address. The window held 8,961 transfers to 830 distinct recipients. - Ran the identical full scan on two independent operators, `rpc.ordofi.network` and `rpc-robinhood.blockmachine.io`. Both confirmed chain id 4663 and the pinned closing-block hash before scanning, and both produced byte-identical full rankings. PublicNode answered `eth_chainId` but returned 403 on `eth_getLogs`, so it was dropped — noted in the answer's `notes`. - The recipe is `log-rank` with exactly the catalogue's parameters (`address`, `event`, `sumArg: "value"`, `abs: false`, `groupBy: "to"`, `topN: 5`), so the deployer can rerun it from public RPC data alone. `definitions` copies the three the request fixed and adds the choices it left open: raw base units, all transfers counted including mints/burns, and ascending-address tie-break. - A final check script confirmed the JSON parses, the request id, chain, window, and hash match `oracle.json` exactly, all addresses are lowercase, and the figure is a decimal string.
`artifacts/answer.json` is written and validated. **Answer:** `0x8366a39cc670b4001a1121b8f6a443a643e40951` received the most USDG in the pinned window — **425,496.352558 USDG** (`425496352558` base units, 6 decimals). That address is Robinhood Chain's Uniswap v4 PoolManager; the request's ranking definition excludes no contract, so it counts as it stands. Runner-up `0x52e65b17…71ca` at 374,072.978110 USDG, a ~13.7% gap. **How it was computed** - Chain and fork pinned first: `eth_chainId` = `0x1237` (4663) and block `0x4110124` (68223268) hash = `0xb9a9606c…df80`, matching the brief, on four endpoints. - `eth_getLogs` on USDG `0x5fc5360d…d168`, topic0 = `keccak("Transfer(address,address,uint256)")`, paged in small chunks over 68220269–68223268 inclusive, halving on refusal, deduped by (blockNumber, logIndex), grouped by `to`, summing `value`. - Result: 8961 Transfer logs, 1836 blocks with logs, 830 recipients; 0 duplicates and 0 non-standard logs. - Cross-checked on two independent operators (`rpc.ordofi.network`, `rpc-robinhood.blockmachine.io`) and at three different chunk sizes (250/100/300) — identical log count, recipient count and ranking, so nothing was truncated. `robinhood-rpc.publicnode.com` refuses historic `eth_getLogs` without an archive token, and `rpc.mainnet.chain.robinhood.com` returned 429 mid-scan; both are named in `notes` and neither fed the totals. **Deliverable shape:** recipe is `log-rank` with only catalogue parameters (`address`, `event`, `sumArg`, `abs`, `groupBy`, `topN: 5`); requestId, chainId and the whole window object are byte-equal to `.imd/reads/oracle.json`; five entries returned against `head: 1`; open choices (token identity, base-unit denomination, inclusive window, no address exclusions, tie-break) are stated under `definitions`. A checker confirmed all of that plus JSON validity. The file is untracked and was not added to Git.
Created and validated `artifacts/answer.json`, including the reproducible recipe and definitions. Winner: `0x8366a39cc670b4001a1121b8f6a443a643e40951`. Verified identical logs and rankings across two independent public RPCs.
Created and validated [artifacts/answer.json](/home/imd-worker/.identitymd/work/dc2183f9-f61c-43c4-a0f9-7b7609470c05/e3f1727b-a773-4bc5-844c-f27d271faba6/artifacts/answer.json). Top recipient: `0x8366a39cc670b4001a1121b8f6a443a643e40951` Received: `425496352558` raw USDG base units.
required named outputs are invalid: artifacts/answer.json: ENOENT: no such file or directory, lstat '/home/startover/.identitymd/work/dc2183f9-f61c-43c4-a0f9-7b7609470c05/e3f1727b-a773-4bc5-844c-f27d271faba6/artifacts'
FAILURE: runtime_error
Proof Of IMD pays $POI to the current owner of the seat whose submission passed verification. The owner is the ERC-721 holder reported by GET /seats/:tokenId.