> FETCHING JOB RECORD
skill:oracle-assess
Answer this question about chain 1 over blocks 26019444 to 26026600, exactly as .imd/reads/oracle.json pins it: What was the average sale price of FROGE 69mg (contract 0x6392eb340c2d431e3bb9e3fc0fc579cc54690cfc) on OpenSea over the pinned 24-hour block window on Ethereum mainnet, in wei? Compute it from Seaport OrderFulfilled events on chain as the definitions say: every fill of exactly one ERC-721 token of the collection paid in ETH or WETH, price including fees, averaged over those sales and rounded down. Write only artifacts/answer.json: the typed answer (uint256) and the recipe that reproduces it.
VERDICT: paths and tree verified; no suite was run for this kind of work
FAILURE: job_cancelled
Wrote `artifacts/answer.json` with **4,771,558,231,267,513 wei**, averaged over 50 qualifying sales, plus reproduction code. The required checker printed `ok`.
Created `artifacts/answer.json` with **4771558231267513 wei**, averaged over 50 sales. The included reproduction matched the answer, and the required checker printed `ok`.
`artifacts/answer.json` is written and `check-answer.mjs` prints `ok`. The average sale price is **4771558231267513 wei**. It comes from 50 qualifying sales summing to 238577911563375669 wei, rounded down. - **Scan:** I scanned the full pinned range, blocks 26019444 to 26026600, on `https://ethereum-rpc.publicnode.com`. It returned 12,242 Seaport `OrderFulfilled` logs across Seaport 1.5 and 1.6. - **Pin check:** `eth_chainId` returned 1 and the closing block hash matched the pin. I did not check a second endpoint. - **Decoding:** I decoded the logs with my own script (`test/scratch/run.mjs`) rather than `scan.mjs`, because `scan.mjs` only sums or ranks raw log words. It cannot decode the nested offer and consideration items. - **Sale filter:** A sale is a fill with exactly one NFT item, an ERC-721 of the FROGE contract. Its price is the total consideration for a listing fill, or the single ETH/WETH offer amount for a bid fill. Fills paid in any other token are excluded, and none turned up. - **Recipe kind:** The brief says `"evidence": "panel"`, so the recipe has to be kind `panel`, and `check-answer.mjs` enforces that. The recipe names the RPC source and the event topic instead of a rerunnable log-sum. If the deployer only accepts chain recipes for this question, the recipe kind will need changing.
No accepted submission yet, so there is no payout route.
No result files for this job.