29004801-2d92-45e6-ab99-52138b92ff63IMD JOB

`artifacts/answer.json` is written, and `check-answer.mjs` prints `ok` for it. The file is untracked (`artifacts/` isn't ignored, so it will show as untracked in `git status`). The top recipient is 0x8894e0a0c962cb723c1976a4421c95949be2d4e3, with 13,453,048.81 USDC received over the window. The top 5, largest first: | Rank | Address | Received (raw units, 18 decimals) | | --- | --- | --- | | 1 | `0x8894e0a0c962cb723c1976a4421c95949be2d4e3` | 13453048808629430661071977 | | 2 | `0x13f12f5d8b269197be17f0ad4f0a5b27463c7839` | 9000000000000000000000000 | | 3 | `0xf2688fb5b81049dfb7703ada5e770543770612c4` | 1090252404253246876755437 | | 4 | `0xb92fe925dc43a0ecde6c8b1a2709c170ec4fff4f` | 1027014522546007051685748 | | 5 | `0x28e2ea090877bf75740558f6bfb36a5ffee9e9df` | 921064325094173036750977 | - **Scan:** I ran `scan.mjs` once over blocks 123188271 to 123196266 from `https://rpc.swiftnodes.io/rpc/bsc`. It matched the pinned closing hash, saw 107,441 Transfer logs and 13,447 distinct recipients, and there are no ties in the top 5. - **Second endpoint:** The closing block hash also matched on `https://api.zan.top/bsc-mainnet`. `https://public.1rpc.io/bnb` returned 403, so I skipped it. - **Recipe and definitions:** The recipe is `log-rank`, grouping by `to` and summing `value` with `abs` false. Under `definitions` I state that amounts are raw 18-decimal token units, that every Transfer counts (mints and transfers to contracts included), and that both window bounds are inclusive.

Created `artifacts/answer.json` with the top five recipients, definitions, and reproducible recipe. Scanned 107,441 Transfer events over the exact pinned range. Validator printed `ok`.

`artifacts/answer.json` is written, and `check-answer.mjs` prints `ok` for it. The top 5 recipients of USDC on BNB Smart Chain over blocks 123188271–123196266, largest first: 1. `0x8894e0a0c962cb723c1976a4421c95949be2d4e3` (raw sum 13453048808629430661071977, which is the `figure`) 2. `0x13f12f5d8b269197be17f0ad4f0a5b27463c7839` 3. `0xf2688fb5b81049dfb7703ada5e770543770612c4` 4. `0xb92fe925dc43a0ecde6c8b1a2709c170ec4fff4f` 5. `0x28e2ea090877bf75740558f6bfb36a5ffee9e9df` - **Scan:** I ran `scan.mjs` once, against `https://rpc.swiftnodes.io/rpc/bsc`. It confirmed chain id 56 and the pinned closing hash, and covered 107,441 Transfer logs across 13,447 recipients. - **Boundary:** Sixth place is `0xabb72d8a54acf84bbee5880974a63ec251d16e6f` at 894000 tokens, well below fifth, so there is no tie at the cutoff. - **Recipe:** It is a `log-rank` grouping the `to` argument and summing `value`, with `topN` 5. - **Definitions:** Sums are raw token units (18 decimals on BSC, not converted to USD). Mint and burn transfers are not excluded. - **Cross-check:** I did not check the closing hash on a second endpoint. The first endpoint, `public.1rpc.io`, returned 403, so only swiftnodes was used. The notes say so.