> FETCHING JOB RECORD
skill:oracle-assess
Answer this question about chain 1 over blocks 26019678 to 26021469, exactly as .imd/reads/oracle.json pins it: Which address received the most SAND on Ethereum mainnet in the last 6 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. It answers that `0x28c6c06298d514db089934071355e5743bf21d60` received the most SAND in blocks 26019678 to 26021469, inclusive. - **Amount:** it received 1301865032406750000000000 raw units of SAND, which is about 1.30 million SAND at 18 decimals. The `figure` field holds this number. The next largest recipient, `0x187c…4100`, received about 0.80 million. - **Recipe:** it is `log-rank`. It sums `Transfer.value` of the SAND contract grouped by `to`, with `topN` 5, so the answer lists the top five addresses. - **Cross-check:** I read the window from two operators, publicnode and mevblocker. Both reported chain id 1 and the pinned closing hash, and both returned the same 229 logs and the same top-8 ranking. `https://rpc.flashbots.net/fast` refused the log queries even at one block, so it was not used. `git status` is clean and `artifacts/answer.json` is untracked, as required. The scan script is in `test/scratch/`, which is not submitted.
Created and validated [artifacts/answer.json](/root/.identitymd/work/90c92679-5905-432c-981a-5ca3b0f4c2a6/b28282cb-f024-4e96-b970-5484693f2397/artifacts/answer.json). Top recipient: `0x28c6c06298d514db089934071355e5743bf21d60` Gross received: `1,301,865.03240675 SAND`
Created and validated [artifacts/answer.json](artifacts/answer.json). Top recipient: `0x28c6c06298d514db089934071355e5743bf21d60`. The computation covers the exact pinned range and matches across two independent public RPC providers.
Created [artifacts/answer.json](artifacts/answer.json) with the ranked addresses and reproducible recipe. Top recipient: `0x28c6c06298d514db089934071355e5743bf21d60` — **1,301,865.03240675 SAND**. Verified matching logs from two independent RPC providers over the exact pinned range.
Created and validated [artifacts/answer.json](/home/imd-worker/.identitymd/work/90c92679-5905-432c-981a-5ca3b0f4c2a6/b28282cb-f024-4e96-b970-5484693f2397/artifacts/answer.json). The result was independently reproduced on two public RPC providers.
Done. `artifacts/answer.json` is written (untracked, not committed, per the delivery rules). **Answer:** `0x28c6c06298d514db089934071355e5743bf21d60` received the most SAND over blocks 26019678–26021469 inclusive — **1,301,865,032,406,750,000,000,000 raw units** (~1,301,865 SAND). This is Binance's hot wallet 14, which is the unsurprising leader for exchange inflows. **How it was computed** - `eth_getLogs` on SAND `0x3845…a5d0`, topic0 = `Transfer(address,address,uint256)`, chunked 512 blocks, deduplicated on `(blockHash, logIndex)`, grouped by indexed `to`, summed `value`, sorted descending with ties by address ascending. - Every endpoint was first checked for `eth_chainId == 0x1` and that block `0x18d0e5d`'s hash equals the pinned `toBlockHash`. - Result: 229 Transfer logs, 125 distinct recipients. **Cross-check** - Three independent operators — publicnode, mevblocker, valve.city — returned identical log counts and identical top-10 rankings. A single whole-window request also returned 229 logs, ruling out truncation. - `rpc.flashbots.net/fast` passed the chain/hash check but refused every `eth_getLogs` range ("block range extends beyond current head block"), so it was dropped and noted. **Recipe:** `log-rank` with `address`, `event`, `sumArg: value`, `abs: false`, `groupBy: to`, `topN: 5` — exactly the catalogue's parameters (optional `filter` omitted). The answer lists the top 5 since `head` is 1; there are no ties within the top 5. All seven of the request's definitions are copied verbatim, plus one stating that "last 6 hours" was taken as exactly the pinned block range.
Created and validated `artifacts/answer.json`. Winner: `0x28c6c06298d514db089934071355e5743bf21d60`. Cross-checked 229 Transfer logs across two independent RPC providers over the exact pinned range.
Taylor, done. **Answer:** `0x28c6c06298d514db089934071355e5743bf21d60` (Binance 14) received the most SAND over blocks 26019678–26021469: `1301865032406750000000000` raw units (~1.30M SAND). **What I did** - Scanned SAND `Transfer` logs over the exact pinned window (400-block chunks), grouped by `to`, summed raw `value`. - Verified `eth_chainId = 1` and the pinned closing-block hash on each endpoint first. - Three independent operators (publicnode, mevblocker, nodereal) returned identical results: 229 logs, same top-10. Flashbots refused `eth_getLogs` for the range and was excluded (noted in `notes`). - Wrote `artifacts/answer.json` with recipe `log-rank` (address/event/sumArg/abs/groupBy/topN only), definitions copied verbatim from the request, top 5 addresses, and `figure` = leader's sum. It's untracked, not staged. Scratch scanner lives in `test/scratch/scan.py`; nothing else was touched.
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.