> 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 CULT 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
Created and validated `artifacts/answer.json`. Top recipient: `0x6698e46683e269ca977f751991f3a6abfe35f632`. Two independent public RPC scans matched all 41 Transfer events and recipient totals.
Wrote `artifacts/answer.json` with the computed `address[]` answer and reproducible `log-rank` recipe. Validated the JSON and checked the pinned `requestId`, chain, window, answer type, lowercase address format, and decimal figure. Two complete public RPC scans agreed on the leader: `0x6698e46683e269ca977f751991f3a6abfe35f632` with `509418093241059563227058465` raw CULT units.
Created `artifacts/answer.json` with the typed answer and reproducible recipe. Top recipient: `0x6698e46683e269ca977f751991f3a6abfe35f632`. Validated all 41 Transfer logs and matching totals across two independent RPC operators.
Taylor, done. `artifacts/answer.json` is written and left untracked. **Answer:** `0x6698e46683e269ca977f751991f3a6abfe35f632` received the most CULT in blocks 26014298–26021470 — 509,418,093,241,059,563,227,058,465 raw units (~509.42M CULT). **How:** `eth_getLogs` on the CULT contract's `Transfer` topic over exactly the pinned window, grouped by indexed `to`, summed `value`. Recipe is `log-rank` with `topN: 5` (head is 1, so extra entries are padding). **Verification:** chainId and closing block hash checked on every endpoint. Three independent operators — publicnode, mevblocker, nodereal (500-block steps) — all returned the same 41 logs / 16 recipients and identical ranking. Flashbots was dropped because it returns HTML throttle pages for `eth_getLogs`; that's noted in the answer. No ties in the top 5.
I wrote `artifacts/answer.json`. The address that received the most CULT over blocks 26014298–26021470 is `0x6698e46683e269ca977f751991f3a6abfe35f632`, with 509418093241059563227058465 raw units (18 decimals). The file parses as valid JSON. I did not run a separate check of its schema against the member answer shape beyond copying the request id, chain and window from the brief. - **Method:** I pulled the CULT `Transfer` logs for the whole window (inclusive), grouped them by the indexed `to` address and summed `value`. Ties would break by ascending address. Nothing is subtracted and no address is excluded. - **Cross-check:** I ran the scan on two operators, `https://ethereum-rpc.publicnode.com` and `https://rpc.flashbots.net/fast`. Both reported chain id 1 and the pinned closing hash for block 26021470. Both returned the same 41 logs and the same top-6 ranking. - **Answer list:** It has the top five addresses. The runner-up is the 1inch router (`0x111111125421ca6dc452d289314280a0f8842a65`) at 461663949037208396814315727. - **Recipe:** It is a `log-rank` grouped by `to`, summing `value`, with `topN` 5. - **Files:** The scratch script is in `test/scratch/scan.py`, which is deleted before submission. `artifacts/answer.json` is untracked and nothing else in the repository changed.
Created `artifacts/answer.json` with the typed answer and reproducible recipe. Winner: `0x6698e46683e269ca977f751991f3a6abfe35f632`. Validated the JSON and cross-checked all 41 Transfer logs across two independent public RPC operators.
`artifacts/answer.json` is written and parses as valid JSON. It names `0x6698e46683e269ca977f751991f3a6abfe35f632` as the address that received the most CULT over blocks 26014298 to 26021470, with 509418093241059563227058465 raw units. I scanned all CULT `Transfer` logs over exactly the pinned range on two operators, `ethereum-rpc.publicnode.com` and `rpc.mevblocker.io/fast`. Both returned the same 41 logs and the same ranking. Five endpoints, including those two, returned the pinned hash for block 26021470 and `eth_chainId` 1 (I didn't check chain id on `one.valve.city`, which was down). The recipe is `log-rank` grouped by `to`, summing `value` with no absolute values, top 5. The answer lists the top five by gross incoming value: 1. `0x6698e46683e269ca977f751991f3a6abfe35f632` 2. `0x111111125421ca6dc452d289314280a0f8842a65` 3. `0x74de5d4fcbf63e00296fd95d33236b9794016631` 4. `0x29e512a8632609725efff6d4eaef2a96a4580cba` 5. `0xb8358b31bca82989d3d6611911da3be38fe242f7` I treated "last 24 hours" as the pinned window and stated that under `definitions`. There is no tie at the top. The scan script is in `test/scratch/`, which isn't submitted.
Created and validated [artifacts/answer.json](/home/imd-worker/.identitymd/work/0937aef8-1c6c-4d68-9f44-9c4348fd4559/a6a6d528-62b0-40c5-a354-70892386abe7/artifacts/answer.json). Top recipient: `0x6698e46683e269ca977f751991f3a6abfe35f632` with `509418093241059563227058465` raw CULT units.
Created `artifacts/answer.json` with the typed answer and reproducible recipe. Winner: `0x6698e46683e269ca977f751991f3a6abfe35f632`. Validated the pinned range and identical results from three public RPC operators.
Created `artifacts/answer.json` with the typed answer, definitions, and reproducible recipe. Top recipient: `0x6698e46683e269ca977f751991f3a6abfe35f632`. Validated JSON and confirmed identical results from three independent public RPC endpoints over the exact pinned range.
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.