1d782647-5df1-4902-9cf8-702d480f854dIMD JOB

I've written `artifacts/answer.json`, and `check-answer.mjs` prints `ok` for it. **Answer:** the top 5 WBNB recipients over blocks 123188269 to 123196265 on BNB Smart Chain, largest first: 1. `0x76801132a22801640284cd67f7dd41fed2926b6a`: 8797.34 WBNB (`figure` = 8797335414498255654163 wei) 2. `0x10ed43c718714eb63d5aa57b78b54704e256024e`: 7945.04 WBNB 3. `0x172fcd41e0913e95784454622d1c3724f546f849`: 7783.51 WBNB 4. `0x16b9a82891338f9ba80e2d6970fdda79d1eb0dae`: 4515.89 WBNB 5. `0x8e76ebb1c71939982c9ac267c0eb25f4aa739535`: 2506.82 WBNB No two sums are equal, including at the cut: sixth place is 2222.77 WBNB, well below fifth. **Recipe:** `log-rank` on the WBNB contract's `Transfer` event. It groups by `to`, sums `value` without `abs`, and returns the top 5. **How I computed and checked it:** - I ran the provided `scan.mjs` once over exactly the pinned range on `https://bsc-rpc.publicnode.com`. It confirmed chain id 56 and the pinned closing hash, and read 229,237 logs in 32 chunks with no refused chunks. The logs came from 7,996 of the range's 7,997 blocks and went to 10,652 distinct recipients. - I checked the closing block hash against a second operator, `https://bsc-dataseed1.bnbchain.org`, and it matched. - I did not complete a second full scan. My attempt on `bsc.drpc.org` failed and I didn't retry it, since the deployer reruns the recipe anyway. **Definitions stated in the file:** - The recipient is the `to` address on each Transfer. - Amounts are raw wei, with nothing filtered out: mints, burns, routers and contracts all count. - Only `Transfer` logs from the WBNB contract count, not its `Deposit` or `Withdrawal` events. I kept the list to 5, matching the question and `topN`, rather than adding extra entries beyond `head`. That keeps my recipe identical to any other member who uses `topN: 5`, so we group together. I changed nothing outside `artifacts/answer.json`, and left it untracked as instructed.

Created `artifacts/answer.json` with the top five recipients, definitions, and reproducible recipe. Computed from 229,237 Transfer events over the exact pinned range. Validator printed `ok`.

`artifacts/answer.json` is written and `check-answer.mjs` prints `ok`. It ranks recipients by WBNB received over blocks 123188269–123196265, and the top 5, largest first, are: 1. `0x76801132a22801640284cd67f7dd41fed2926b6a`: 8797335414498255654163 wei, which is also the `figure` 2. `0x10ed43c718714eb63d5aa57b78b54704e256024e`: 7945043247391456331739 wei 3. `0x172fcd41e0913e95784454622d1c3724f546f849`: 7783512854944574765475 wei 4. `0x16b9a82891338f9ba80e2d6970fdda79d1eb0dae`: 4515893407388455629211 wei 5. `0x8e76ebb1c71939982c9ac267c0eb25f4aa739535`: 2506815825465022358023 wei There is no tie at the cut: the 6th recipient has 2222769307880395299511 wei. - **Scan:** I ran `scan.mjs` once, whole, against `https://rpc.swiftnodes.io/rpc/bsc`. It matched the pinned closing hash and read 229,237 Transfer logs across 10,652 recipients. 7,996 of the 7,997 blocks in the window had WBNB Transfers, which is consistent with a complete scan. - **Endpoints:** I checked the closing hash on a second operator, `https://api.zan.top/bsc-mainnet`. `https://public.1rpc.io/bnb` hit its usage limit on the first attempt, so I used nothing from it. - **Recipe:** `log-rank` on the WBNB contract, event `Transfer`, summing `value` and grouping by `to`, with `topN` 5. - **Definitions:** I stated them in the file. The recipient is the indexed `to` argument, and no address is excluded, so routers and pools count. Amounts are raw wei, and only Transfer events count, not Deposit or Withdrawal. The `window` object has to list `toBlock` before `fromBlock` for the checker to accept it. My first version had them the other way round and was refused.