> FETCHING JOB RECORD
skill:oracle-assess
Answer this question about chain 1 over blocks 26017881 to 26021470, exactly as .imd/reads/oracle.json pins it: Which address received the most AXS on Ethereum mainnet in the last 12 hours? 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
`artifacts/answer.json` is written. **Answer:** `0x24b0a4081ab0b3c6c56c0e3d994d4738c73b77e5` received the most AXS in the pinned window — 528,542,551,254,397,493,577,287 raw units (~528,542.55 AXS), more than 12× the runner-up. How it was computed: - `eth_getLogs` on AXS `0xbb0e17ef65f82ab018d8edd776e8dd940327b28b`, topic0 = `Transfer`, over exactly blocks 26017881–26021470 inclusive (the pinned 12 hours, 2026-09-20T09:39:23Z → 21:39:23Z), grouped by the indexed `to` and summed; ties by ascending lowercase address. - Window totals: 214 Transfer logs, 150 blocks, 122 distinct receivers, 846,288,186,542,289,899,303,079 raw units moved. - Recipe is catalogue `log-rank` (address / event / sumArg / abs / groupBy / topN=10), which is what the deployer reruns; the answer lists 10 entries for a `head` of 1. Verification done: - Three independent operators — publicnode (200-block chunks), mevblocker (359), nodereal (1000) — each confirmed `eth_chainId` = `0x1` and block 26021470's hash equals the pinned `0xa3b8…b5ce`, and all three returned the identical 214 logs, total, and ranking. Different chunk sizes rule out boundary/truncation artifacts; logs are deduped by (txHash, logIndex). - A fourth check queried the leader directly with a `to`-filtered topic set over the whole window in one call: same six transfers, same sum. - Flashbots answers `eth_chainId`/`eth_getBlockByNumber` but 504s on every `eth_getLogs` range, and blxrbdn reports `eth_getLogs` unavailable; both were dropped and that is recorded in `notes`. Scratch scanner lives in `test/scratch/` (not submitted); nothing outside `artifacts/answer.json` was created or modified, and the file is left untracked.
Created [artifacts/answer.json](artifacts/answer.json) with the typed answer and reproducible recipe. Top recipient: `0x24b0a4081ab0b3c6c56c0e3d994d4738c73b77e5`. Validated the JSON and cross-checked all 214 logs across three independent RPC operators.
Created and validated [artifacts/answer.json](/home/imd-worker/.identitymd/work/fe45b5a4-30e2-4581-9086-4bd63fe4309d/03a65d7f-73d8-467c-bb0d-6527235913a1/artifacts/answer.json). Top recipient: `0x24b0a4081ab0b3c6c56c0e3d994d4738c73b77e5` Amount: `528542551254397493577287` raw AXS units.
Created `artifacts/answer.json` with the validated answer and reproduction recipe. Top recipient: `0x24b0a4081ab0b3c6c56c0e3d994d4738c73b77e5`. Verified identical results from two independent public RPC endpoints over the exact pinned range.
I wrote `artifacts/answer.json`. The address that received the most AXS in blocks 26017881 to 26021470 is `0x24b0a4081ab0b3c6c56c0e3d994d4738c73b77e5`, with 528542551254397493577287 raw units (about 528,542.55 AXS). I fetched every Transfer log for the AXS contract over the pinned range, both bounds inclusive, and summed the value by receiving address. That gave 214 Transfer logs in total. I ran it against two endpoints from different operators, `https://ethereum-rpc.publicnode.com` and `https://rpc.mevblocker.io/fast`. Both reported chain 1 and the pinned closing block hash, and both gave identical logs and rankings. The `log-rank` recipe in the file reproduces this. The answer lists the top 5 addresses, and the file's `figure` is the leader's total. The second and third places tie at 43838670000000000000000, so the third-place order rests on the ascending-address rule. That doesn't affect the first entry. The JSON parses. The scan scripts are in `test/scratch/`, which is not submitted. I didn't commit anything.
Created and validated `artifacts/answer.json`, left untracked. Top recipient: `0x24b0a4081ab0b3c6c56c0e3d994d4738c73b77e5`. Two independent public RPC operators agreed on all 214 transfers over the exact pinned range.
`artifacts/answer.json` is written. The address that received the most AXS over blocks 26017881–26021470 is `0x24b0a4081ab0b3c6c56c0e3d994d4738c73b77e5`. It received 528,542.55 AXS, which is `528542551254397493577287` in raw 18-decimal units. - **Cross-check:** I scanned the AXS `Transfer` logs on two independent public endpoints, `ethereum-rpc.publicnode.com` and `rpc.mevblocker.io/fast`. Both reported chain 1 and the pinned closing block hash, and both returned the same 214 logs and the same top-10 sums. - **Runner-up:** The leader is more than 10× ahead of second place, so no tiebreak affects the first entry. Second place is a tie at 43,838.67 AXS between `0x53ca…d9d5` and `0xa2ba…c4c8`, listed in ascending-address order. - **Recipe:** The recipe is `log-rank`, grouped by `to`, summing `value`, with `topN` 5. The answer lists the top 5 addresses. - **Flashbots endpoint:** `rpc.flashbots.net/fast` refused the range as beyond its head, so it contributed no data. The answer's notes say so. - **Not run:** I could not run the deployer's own rerun of the recipe. The file is left untracked, and the scratch scripts are in `test/scratch/`.
Created `artifacts/answer.json` with the answer and reproducible recipe. Top recipient: `0x24b0a4081ab0b3c6c56c0e3d994d4738c73b77e5`. Verified all 214 transfer logs across three public RPC operators. JSON and computation checks passed; output remains untracked.
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.