40c0e808-7a93-4c45-adc4-f88bc2250f55IMD JOB

**Deliverable:** `artifacts/answer.json` (untracked; `artifacts/` is git-ignored here, so nothing was added to the index). **Answer:** ranked `address[]`, leader `0x0000000000000000000000000000000000000000` with 9 units; the leading non-zero recipient is `0xbe24e64bac17b8347e41c49cbb7559364369912b` with 6. `figure` is `"9"`. **How it was computed:** a scratch Node script (`test/scratch/scan.mjs`) walked blocks 26014296–26021468 with `eth_getLogs` filtered to `0xd4416b13d2b3a9abae7acd5d6c2bbdbe25686401` and topic0 `0xc3d5…0f62`, halving the range on any 403/429/timeout, de-duplicating by `(blockHash, logIndex)`, asserting 4 topics / 128-hex data / in-window block number per log, and summing the second data word per indexed `to`. Window holds 40 TransferSingle logs, 20 distinct recipients. **Verification:** - Closing-block hash matched the pinned `0x931d2878…` and `eth_chainId` returned `0x1` on flashbots, mevblocker, publicnode, nodereal and blxrbdn. - The full scan was run independently on three operators (publicnode, mevblocker, nodereal) with chunk sizes 1000/1500/2000 — all three returned the same 40 logs, 20 recipients and identical ranking, so no endpoint truncated. - Contract identity checked on chain: `name()` returns `"NameWrapper"`. - blxrbdn refused `eth_getLogs` and was dropped; `one.valve.city` answered `eth_chainId` but errored on block reads. **The one judgment call, stated plainly:** I kept the zero address as a recipient key, so it is the first entry. The request defines the ranking as the contract's TransferSingle logs grouped by `to` with no exclusion, and the `log-rank` recipe the deployer reruns has no parameter that can drop a key — excluding unwrap burns would have produced an answer its own recipe does not reproduce. This is recorded under `definitions.zeroAddressRecipient` along with the leading non-zero recipient, since `head` is 1 and this choice decides that position. A panel member who reads "received" as excluding burns will disagree with me here; I chose reproducibility from the stated recipe. **Not done:** nothing else was written or modified; no config, lib or workflow files were touched.

Created and validated [answer.json](/home/imd-worker/.identitymd/work/40c0e808-7a93-4c45-adc4-f88bc2250f55/84c3cb5d-441d-4312-803a-06e7ee67a688/artifacts/answer.json). The top recipient is `0x0000000000000000000000000000000000000000` with `9` raw units.

Created `artifacts/answer.json` with the reproducible recipe. The zero address received the most units: **9**, including burns as required by the pinned definitions. Two independent RPC scans agreed; JSON and recipe checks passed.

Taylor, done. `artifacts/answer.json` is written and left untracked. **Answer:** `0x0000000000000000000000000000000000000000` — 9 token units over blocks 26014296–26021468 (40 TransferSingle logs total, 20 distinct recipients). **Recipe:** `log-rank` on the Name Wrapper `0xd4416b13…6401`, event `TransferSingle`, `sumArg: value`, `groupBy: to`, `topN: 8`. **Verification:** chain id and pinned closing hash checked on publicnode and mevblocker; both chunked scans returned identical logs and sums. A single-shot full-range query on nodereal returned the same 40 logs and ranking. Flashbots rejected `eth_getLogs` and was excluded (noted). **One flag:** the leader is the zero address — Name Wrapper unwraps burn via `TransferSingle(to=0x0)`. The pinned `ranking` definition groups by `to` with no exclusion and `log-rank` has no exclude parameter, so I kept it to stay reproducible by the deployer's rerun. I added a `zeroAddressRecipient` definition stating this and naming the top non-burn recipient (`0xbe24e64b…912b`, 6 units), which is second in the list.

Done. `artifacts/answer.json` is written, untracked, and is the only path outside `test/scratch/` I touched. **Answer:** `0x0000000000000000000000000000000000000000` — figure `9`. **How it was computed** - Scanned `TransferSingle` logs (topic0 verified via `cast keccak`) from the Name Wrapper `0xd4416b13d2b3a9abae7acd5d6c2bbdbe25686401` over blocks 26014296–26021468 inclusive, grouped by indexed `to`, summed `value`. - Two independent operators agreed exactly: `ethereum-rpc.publicnode.com` (4 × 2000-block chunks) and `rpc.mevblocker.io/fast` (single call). Both returned 40 logs, 20 distinct recipients, identical ranking. Both passed `eth_chainId` = 1 and the pinned closing-block hash. `rpc.flashbots.net/fast` passed the hash check but refused every `eth_getLogs` range, so it's named in notes as unused for the scan. - Recipe: `log-rank` with `groupBy: to`, `sumArg: value`, `abs: false`, `topN: 6`, no filter — matching the pinned definitions exactly. **One thing worth flagging:** the leader is the zero address, because the pinned definitions group by the indexed `to` with no exclusion and count gross incoming value, and 9 of the 40 logs in the window were unwrap/burn transfers to `0x0`. I followed the definitions literally rather than inventing a burn filter (which would be a different recipe and split the panel), stated this under `definitions.zeroAddress`, and noted in `notes` that the leading non-zero recipient is `0xbe24e64bac17b8347e41c49cbb7559364369912b` with 6 units. The list carries 6 entries beyond `head: 1` for context; the tie at 2 units is ordered by address ascending.

Created and validated [artifacts/answer.json](artifacts/answer.json). The zero address ranked first with **9 units**, including burns under the pinned definitions. Two independent public RPC endpoints returned identical logs.

I wrote `artifacts/answer.json`. By the request's own definition the answer is the zero address, `0x0000000000000000000000000000000000000000`, with 9 token units. Those units are burns (transfers to `0x0`, such as unwraps), not a holder receiving tokens. The pinned ranking groups every `TransferSingle` by its `to` address and has no exclusion, and the `log-rank` recipe has no parameter for one, so I did not drop the zero address. If it were excluded, the leader would be `0xbe24e64bac17b8347e41c49cbb7559364369912b` with 6. I noted this in `definitions` and `notes`. - **Scan:** I pulled every `TransferSingle` log from the Name Wrapper (`0xd4416b13d2b3a9abae7acd5d6c2bbdbe25686401`) over blocks 26014296 to 26021468, both inclusive. That gave 40 logs. - **Ranking:** the top five are `0x0000…0000` (9), `0xbe24…912b` (6), `0xb929…1896` (4), `0x106b…b9b494` (3) and `0x9e58…446b` (2). The answer lists these five. - **Recipe:** `log-rank` on the Name Wrapper, summing `value` grouped by `to`, `topN` 5. - **Cross-check:** two endpoints, `https://ethereum-rpc.publicnode.com` and `https://rpc.mevblocker.io/fast`, returned the same top-10 ranking. The closing block hash matched the pinned one on both, and on `https://rpc.flashbots.net/fast`. - **Not used:** a scan on the flashbots endpoint was too slow to finish, so it isn't part of the cross-check. The file is untracked and nothing else was touched. My scan script is in `test/scratch/`, which isn't submitted.

Created `artifacts/answer.json` with the typed answer and reproducible recipe. Winner: `0x0000000000000000000000000000000000000000`, receiving **9 units**. Burn transfers count under the pinned definitions. Verified matching logs from two RPC operators and validated the JSON.

Created and validated [artifacts/answer.json](/home/imd-worker/.identitymd/work/40c0e808-7a93-4c45-adc4-f88bc2250f55/84c3cb5d-441d-4312-803a-06e7ee67a688/artifacts/answer.json). The result was independently reproduced across three public RPC providers.