d2704525-bc53-4ebf-b537-42168527fc92IMD JOB

Created `artifacts/answer.json`: **91184873913805555 wei**, averaged over 36 qualifying sales, with reproduction details. The required checker printed `ok`.

`artifacts/answer.json` is written and `check-answer.mjs` prints `ok`. The average TROLLS sale price on OpenSea over blocks 26019444–26026600 is **91184873913805555 wei**. - **How I got it:** I took the 39 ERC-721 `Transfer` events of the collection in the window, which fall in 33 blocks. For those blocks only, I fetched Seaport 1.5 and 1.6 `OrderFulfilled` logs and decoded them. - **Sales counted:** 36 fills qualified. The other 3 transfers were not Seaport fills. None were excluded as bundles, ERC-1155, or non-ETH/WETH payments. - **Arithmetic:** the 36 prices sum to 3282655460897000000 wei. Divided by 36 and rounded down, that gives the answer above. - **Cross-check:** I reran the whole computation on a second operator's endpoint and got the same result. The pinned closing hash matched on both endpoints. - **Recipe kind:** the brief is `"evidence": "panel"`, so the checker only accepts a `panel` recipe. I named the RPC and the OrderFulfilled topic as its `source`, and put the decoding rules under `definitions` and `notes`. I did not use `scan.mjs` for the sales figure because it cannot decode Seaport's item arrays. My decoder is in `test/scratch/sales.mjs`, which is not submitted. The deployer will need to re-decode the logs itself, since the panel recipe reruns nothing. The checker also required `window` keys in the brief's order (`toBlock`, `fromBlock`, `toBlockHash`), so I matched that.

Created [artifacts/answer.json](artifacts/answer.json) with the reproduction procedure. Average: **91,184,873,913,805,555 wei** across **36 qualifying sales**. The required checker printed `ok`.