> FETCHING JOB RECORD
skill:oracle-assess
Answer this question about chain 56 over blocks 123188278 to 123196273, exactly as .imd/reads/oracle.json pins it: Which address sent the most DOGE (Dogecoin, token 0xba2ae424d960c26247dd6c32edc70b295c744c43) on BNB Smart Chain in the last 1 hours? Rank senders by the sum of value over Transfer events of that contract, grouped by from; 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` with the top five senders, definitions, and reproducible recipe over the exact pinned range. Validation printed `ok`. The file remains untracked.
Created `artifacts/answer.json` with the top five senders, definitions, and reproducible recipe for the exact pinned range. Scanned 2,005 Transfer events. Validation printed `ok`.
`artifacts/answer.json` is written, and `check-answer.mjs` prints `ok` for it. The top DOGE sender in the pinned window is `0x278d858f05b94576c1e6f73285886876ff6ef8d2`. The top 5 senders, largest first, are: 1. `0x278d858f05b94576c1e6f73285886876ff6ef8d2` (sum 42756655026333) 2. `0x353d328efbef48b79a570cbc2fde20f40e9f2063` (sum 32395789581892) 3. `0xe6b82c6eccdfb2d6bc55bb11a61bae5ab2c3f807` (sum 26677428216929) 4. `0xe2fc31f816a9b94326492132018c3aecc4a93ae1` (sum 21649308099813) 5. `0xce6160bb594fc055c943f59de92cee30b8c6b32c` (sum 15020378650044) - **Scan:** one full run over blocks 123188278 to 123196273 on `https://rpc.swiftnodes.io/rpc/bsc`. It matched the pinned closing hash and returned 2005 Transfer logs from 254 distinct senders. - **Cross-check:** `https://bsc-rpc.publicnode.com` returns the same hash for block 123196273. `https://public.1rpc.io/bnb` returned 403, so I skipped it. - **Recipe:** `log-rank` on the DOGE contract, grouping the Transfer event by `from` and summing `value`, with `topN` 5. - **Definitions:** sums are raw token base units, and mints and contract senders are counted like any other address. The definitions and the exact command I ran are in the file. - **Repo state:** `git status` shows nothing to commit because the output stays untracked, as required.
Done — `artifacts/answer.json` is written and the plane's checker prints `ok`. **Answer (top 5 DOGE senders on BSC over blocks 123188278–123196273, largest first):** 1. `0x278d858f05b94576c1e6f73285886876ff6ef8d2` — 42,756,655,026,333 base units (~427,567 DOGE) 2. `0x353d328efbef48b79a570cbc2fde20f40e9f2063` — 32,395,789,581,892 3. `0xe6b82c6eccdfb2d6bc55bb11a61bae5ab2c3f807` — 26,677,428,216,929 4. `0xe2fc31f816a9b94326492132018c3aecc4a93ae1` — 21,649,308,099,813 5. `0xce6160bb594fc055c943f59de92cee30b8c6b32c` — 15,020,378,650,044 How it was computed: one whole scan of the pinned window with the provided `scan.mjs` against `https://bsc-rpc.publicnode.com` (the first-listed endpoint, `public.1rpc.io/bnb`, caps `eth_getLogs` at 50 blocks and then errored, so I moved to the next operator). The scan confirmed chain id 56 and the pinned closing hash, read 2,005 Transfer logs of the DOGE contract across 254 distinct senders, and ranked by summed `value` grouped by `from`. I also cross-checked the closing block hash on a second operator (`bsc-dataseed.bnbchain.org`) — it matches. Sixth place (14,696,700,000,000) is well below fifth, so the top-5 cut isn't tie-sensitive. The recipe in the answer is `log-rank` on `event Transfer(address indexed from, address indexed to, uint256 value)` at the token contract, `sumArg: value`, `groupBy: from`, `topN: 5`, `abs: false`, with the open choices (raw 8-decimal base units, no zero-address exclusion, tie ordering) stated under `definitions`. The file is left untracked for the daemon to pick up.
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.