> FETCHING JOB RECORD
skill:oracle-assess
Answer this question about chain 56 over blocks 123188276 to 123196270, exactly as .imd/reads/oracle.json pins it: Which address received the most ETH (Ethereum Token, token 0x2170ed0880ac9a755fd29b2688956bd959f933f8) on BNB Smart Chain in the last 1 hours? Rank recipients by the sum of value over Transfer events of that contract; answer the top 5, largest first, ties by ascending address. 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 [artifacts/answer.json](/home/imd-worker/.identitymd/work/ad667ae4-3a4b-407b-a9d5-b40873eda607/24d4cde3-157e-4b55-878a-bd948dde616e/artifacts/answer.json). Validation passed: `check-answer.mjs` printed `ok`. The pinned block hash was independently confirmed through a second public RPC.
`artifacts/answer.json` is written and `check-answer.mjs` prints `ok` (exit 0). **Result** — top 5 recipients of Binance-Peg ETH (`0x2170ed08…f933f8`) over blocks 123188276–123196270 on chain 56, by summed `Transfer.value`: | # | recipient | total (wei) | |---|---|---| | 1 | `0x76801132a22801640284cd67f7dd41fed2926b6a` | 636318304399640843147 | | 2 | `0xd0e226f674bbf064f54ab47f42473ff80db98cba` | 592972949089096075756 | | 3 | `0x44baf1777729db71fb59867888df5745e375170e` | 250000000000000000000 | | 4 | `0x8e76ebb1c71939982c9ac267c0eb25f4aa739535` | 186547118695575316629 | | 5 | `0x8894e0a0c962cb723c1976a4421c95949be2d4e3` | 173945726741278840890 | How it was computed: - Pinned closing hash confirmed on `bsc-rpc.publicnode.com` before scanning, and again by the scan script itself (`pinned: true`). - Scan via the delivered `scan.mjs` on `https://bsc.rpc.sentio.xyz` — 19336 Transfer logs, 1079 distinct recipients, 4961 blocks with logs. `public.1rpc.io/bnb` was abandoned first (50-block `eth_getLogs` cap plus rate limiting); drpc/zan/meowrpc/blastapi refused with 400/429. - Because silent truncation is the one thing that makes honest members disagree, I re-ran the same scan on a second operator (`rpc-bsc.blockmachine.io`): identical log count, key count and top 5. That cross-check cost ~3 seconds. - Recipe is `log-rank` over the token's `Transfer`, `sumArg: value`, `groupBy: to`, `abs: false`, `topN: 5` — the same event, contract and arguments the scan used, so the deployer's rerun lands on this list. - `definitions` fixes what the question left open: recipient = the `to` argument with nothing excluded (including the zero address), denomination = raw 18-decimal token units with no price conversion, window = the pinned block range rather than a wall-clock hour, and source = that contract's Transfer logs only. One thing worth flagging for the panel: sixth place (`0xbe1418…01a5`, 172087147041094703935) sits about 1% below fifth, so any member whose scan was truncated will most likely diverge at position 5. `head` is 1, so agreement should still hold on the leader.
Created [artifacts/answer.json](/home/worker/.identitymd/work/ad667ae4-3a4b-407b-a9d5-b40873eda607/24d4cde3-157e-4b55-878a-bd948dde616e/artifacts/answer.json). Validation passed: `check-answer.mjs` printed `ok`.
The check passes with `ok`. No durable, applicable lesson from this session worth saving to memory — this was a self-contained task execution with no user correction or standing preference expressed. **Summary:** Scanned Transfer logs for the ETH token (0x2170ed...) on BNB Smart Chain over blocks 123188276–123196270 via `rpc.swiftnodes.io/rpc/bsc` (after `public.1rpc.io/bnb` failed), ranked recipients by summed value, and cross-confirmed the pinned block hash on a second independent endpoint (`bsc-rpc.publicnode.com`). Wrote `artifacts/answer.json` with a `log-rank` recipe (top 5, largest first: `0x76801132...`, `0xd0e226f6...`, `0x44baf177...`, `0x8e76ebb1...`, `0x8894e0a0...`), which passes `check-answer.mjs` (`ok`).
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.