> FETCHING JOB RECORD
skill:oracle-assess
Answer this question about chain 1 over blocks 26014298 to 26021470, exactly as .imd/reads/oracle.json pins it: Which address received the most PRIME on Ethereum mainnet in the last 24 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 and parses as valid JSON. The address that received the most PRIME in blocks 26014298–26021470 is `0x0d0707963952f2fba59dd06f2b425ace40b492fe`, with 47524704815693289689005 raw units (about 47,524.7 PRIME). I scanned every PRIME `Transfer` log in the pinned range and summed `value` by the `to` address, counting gross incoming transfers as the request defines them. There were 92 logs. I ran the same scan on `https://ethereum-rpc.publicnode.com` and `https://one.valve.city/rpc/vk_demo/evm/1`. Both returned chain 1, the pinned block 26021470 hash, and identical totals. The answer lists the top five recipients, and the recipe is a `log-rank` with `groupBy: to` and `topN: 5`: 1. `0x0d07…92fe` 2. `0x8782…07b3` (39049062255930000000000) 3. `0xa312…b647` (16197207601703662046777) 4. `0x95ec…9dd3` (15764600000000000000000) 5. `0x0051…6cea` (11312600000000000000000) A sixth address, `0xa9d1e08c7793af67e9d92fe308d5697fb81d3e43`, ties fifth place at 11312600000000000000000. The ascending-address tie-break puts it after `0x0051…`, so it is not in the list. I did not run the recipe through the deployer's own tooling. `git status` shows no tracked changes; `artifacts/answer.json` and the scan script in `test/scratch/` are left untracked.
Created `artifacts/answer.json` with the typed answer and reproducible recipe. Winner: `0x0d0707963952f2fba59dd06f2b425ace40b492fe` Received **47,524.704815693289689005 PRIME**. Validated the exact pinned window and matching logs across three RPC operators.
Created and validated [artifacts/answer.json](/home/imd-worker/.identitymd/work/48df6a8f-115d-4d0c-b133-c982deb59626/4cb04624-9396-4b3a-a311-a844ce7fcff7/artifacts/answer.json). Top recipient: `0x0d0707963952f2fba59dd06f2b425ace40b492fe` Received: `47524704815693289689005` raw PRIME units.
I wrote `artifacts/answer.json`. The address that received the most PRIME in the window is `0x0d0707963952f2fba59dd06f2b425ace40b492fe`, with 47524704815693289689005 raw units (about 47,524.70 PRIME). - **Scan:** I summed PRIME `Transfer` logs by the indexed `to` address over blocks 26014298 to 26021470 inclusive. I found 92 logs. The recipe is `log-rank` with `groupBy: to` and `topN: 5`. - **Cross-check:** four independent endpoints returned identical totals: publicnode, mevblocker, valve.city and nodereal. All four reported chain id 1 and the pinned closing hash. - **Flashbots:** `rpc.flashbots.net/fast` matched the chain id and hash but timed out on `eth_getLogs`, so I didn't use it for the figure. - **Ranking:** the second place is `0x8782163068c7cd74d2510768a61135c1e4eb07b3` with about 39,049.06 PRIME. Fifth and sixth place tie at 11,312.6 PRIME. The answer lists the lower address first, `0x0051cc1d8bbf0b3373b02e22ea5a2fe483266cea`, as the rules require. The file is valid JSON and is left untracked. My scan script is in `test/scratch/`, which is not submitted.
Done. `artifacts/answer.json` is written (untracked, not committed — `git status` is clean because `artifacts/` and `test/scratch/` are ignored/untracked as intended). **Answer:** `0x0d0707963952f2fba59dd06f2b425ace40b492fe` received the most PRIME over blocks 26014298–26021470 inclusive — **47524704815693289689005** raw units (~47,524.70 PRIME) across 3 incoming transfers. **How it was computed** - `eth_getLogs` on PRIME `0xb23d80f5fefcddaa212212f028021b41ded428cf`, topic0 = `Transfer`, over exactly the pinned range in 2000-block chunks; grouped by indexed `to`, summed `value`, sorted descending with ties by address ascending — matching every definition the request pinned. - Each endpoint was checked for `eth_chainId = 0x1` and the pinned closing hash before use. - **Three independent operators agree**: publicnode and nodereal produced byte-identical full rankings (92 transfers, 57 recipients); mevblocker returned the same 92 logs in a single whole-window call and the same leader sum. - `rpc.flashbots.net/fast` timed out (504) on every `eth_getLogs` range down to one block, so it was dropped per the rotation rule; this is recorded in `notes`. **Recipe:** `log-rank` with `address`, `event`, `sumArg: value`, `abs: false`, `groupBy: to`, `topN: 8` (head is 1; a few extra positions included as the reference suggests). The one open point — how "last 24 hours" maps to the window — is stated under `definitions` as exactly the pinned block range with no wall-clock filtering, and all requester-fixed definitions are copied verbatim.
Created `artifacts/answer.json` with the typed answer and reproducible recipe. Two independent RPC providers agreed on all 92 transfers and the ranking. JSON validation passed.
Created and validated [artifacts/answer.json](artifacts/answer.json), left untracked. Top recipient: `0x0d0707963952f2fba59dd06f2b425ace40b492fe`. Two independent public RPC scans matched across the exact pinned range.
Created `artifacts/answer.json` with the computed `address[]` answer and reproducible `log-rank` recipe. Verified: - JSON parses with `jq`. - Request id, chain id, block window, and closing hash match `.imd/reads/oracle.json`. - Cross-check RPC reductions agreed on leader and figure: `0x0d0707963952f2fba59dd06f2b425ace40b492fe`, figure `47524704815693289689005`.
Created `artifacts/answer.json` with the typed ranking, definitions, and reproducible recipe. Top recipient: `0x0d0707963952f2fba59dd06f2b425ace40b492fe`. Validated the JSON and cross-checked all 92 Transfer logs against two independent RPC providers.
Created `artifacts/answer.json` with the typed answer and reproducible recipe. Top recipient: `0x0d0707963952f2fba59dd06f2b425ace40b492fe`. Validated 92 matching logs from two independent RPC operators over the exact pinned window.
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.