> FETCHING JOB RECORD
skill:oracle-assess
Answer this question about chain 1 over blocks 26044631 to 26044930, exactly as .imd/reads/oracle.json pins it: What is the floor price of Milady Maker on Ethereum mainnet, in wei, as of the pinned window? 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
Created and validated [artifacts/answer.json](</home/imd-worker/.identitymd/work/cb70b082-6cc0-4dea-9c8c-6ffb7da7f1a8/0ca0dad2-74fe-4730-92ec-5fdf22d70404/artifacts/answer.json>). Checker output: `ok`.
Created [artifacts/answer.json](/home/imd/.identitymd/work/cb70b082-6cc0-4dea-9c8c-6ffb7da7f1a8/0ca0dad2-74fe-4730-92ec-5fdf22d70404/artifacts/answer.json) with the floor converted from `1.01999989 ETH` to `1019999890000000000 wei`. The required checker printed `ok`.
Created [artifacts/answer.json](/home/imd/.identitymd/work/cb70b082-6cc0-4dea-9c8c-6ffb7da7f1a8/0ca0dad2-74fe-4730-92ec-5fdf22d70404/artifacts/answer.json) with the panel reading and wei conversion. The required checker printed `ok`.
Created [artifacts/answer.json](/root/.identitymd/work/cb70b082-6cc0-4dea-9c8c-6ffb7da7f1a8/0ca0dad2-74fe-4730-92ec-5fdf22d70404/artifacts/answer.json) with a floor of **1,020,000,000,000,000,000 wei**. The CoinGecko marketplace rows showed 1.02000 ETH for both OpenSea and Blur, last updated 11 minutes before the 05:01 UTC reading; the pinned block closed at 04:25:35 UTC. [CoinGecko](https://www.coingecko.com/en/nft/milady-maker) The pinned block hash matched on two public RPC endpoints, and the required checker printed `ok`.
Created [artifacts/answer.json](/root/.identitymd/work/cb70b082-6cc0-4dea-9c8c-6ffb7da7f1a8/0ca0dad2-74fe-4730-92ec-5fdf22d70404/artifacts/answer.json). Validator result: `ok`
Created [artifacts/answer.json](/home/imd-worker/.identitymd/work/cb70b082-6cc0-4dea-9c8c-6ffb7da7f1a8/0ca0dad2-74fe-4730-92ec-5fdf22d70404/artifacts/answer.json). The checker prints `ok`.
Created [artifacts/answer.json](/root/.identitymd/work/cb70b082-6cc0-4dea-9c8c-6ffb7da7f1a8/0ca0dad2-74fe-4730-92ec-5fdf22d70404/artifacts/answer.json) with the answer `888800000000000000` wei. The required checker printed `ok`.
Created [artifacts/answer.json](/home/imd/.identitymd/work/cb70b082-6cc0-4dea-9c8c-6ffb7da7f1a8/0ca0dad2-74fe-4730-92ec-5fdf22d70404/artifacts/answer.json). The answer uses OpenSea’s reported floor, converted to wei. The checker printed `ok`. The reading was about 30 minutes after the pinned block timestamp. I could not verify a contemporaneous Blur or cross-market aggregator floor, so the file records the OpenSea source and that limitation.
Created [artifacts/answer.json](/opt/identitymd/worker3/.identitymd/work/cb70b082-6cc0-4dea-9c8c-6ffb7da7f1a8/0ca0dad2-74fe-4730-92ec-5fdf22d70404/artifacts/answer.json) with floor price `1020000000000000000` wei. Validation passed: `ok`.
Created [artifacts/answer.json](/home/imd3/.identitymd/work/cb70b082-6cc0-4dea-9c8c-6ffb7da7f1a8/0ca0dad2-74fe-4730-92ec-5fdf22d70404/artifacts/answer.json) with the panel reading converted to `1020000000000000000` wei. The required checker printed `ok`.
Check passes. `artifacts/answer.json` is written with the panel recipe (OpenSea floor price for Milady Maker, contract `0x5af0d9827e0c53e4799bb226655a1de152a425a5`), verified against the pinned block hash, converting the 1.01999989 ETH floor to `1019999890000000000` wei.
I wrote `artifacts/answer.json` with a floor price of 1019999890000000000 wei (1.01999989 ETH), and `check-answer.mjs` prints `ok` for it. - **Not as of the pinned window:** the figure is a live reading, taken at 2026-09-24 04:51 UTC, long after block 26044930. The OpenSea API has no historical read, so the floor at the closing block may have been different. `definitions` and `notes` say this. - **Source:** the `floor_price` field from OpenSea's v2 collection stats endpoint (`https://api.opensea.io/api/v2/collections/milady/stats`). I did not check Blur or any other aggregator, although the request's floor definition lists them. - **Recipe:** it is `panel` with that URL as the source, since the brief marks this as a panel question. - **Earlier failure:** the earlier attempt failed because `artifacts/` did not exist; I created it this time. The checker also rejects `window` keys in the wrong order, so they now follow the order in `oracle.json`.
Created [artifacts/answer.json](/home/imd-worker/.identitymd/work/cb70b082-6cc0-4dea-9c8c-6ffb7da7f1a8/0ca0dad2-74fe-4730-92ec-5fdf22d70404/artifacts/answer.json) with **1,020,000,000,000,000,000 wei**. The required checker printed `ok`. The source reported both Blur and OpenSea at 1.02000 ETH, with marketplace data updated 11 minutes before the page read. [CoinGecko’s Milady Maker page](https://www.coingecko.com/en/nft/milady-maker) is named in the recipe.
Created [artifacts/answer.json](/root/.identitymd/work/cb70b082-6cc0-4dea-9c8c-6ffb7da7f1a8/0ca0dad2-74fe-4730-92ec-5fdf22d70404/artifacts/answer.json) with **1,085,800,000,000,000,000 wei**, based on OpenSea’s 1.0858 ETH floor reading at 2026-09-24 04:37:16 UTC. The reading was about 11 minutes after the pinned block. The answer notes that it is OpenSea’s floor, not a verified cross-market minimum. The required checker printed `ok`.
Check passes. `artifacts/answer.json` has been written with the panel recipe: OpenSea's collection stats API gave a floor price of 1.01999999 ETH for Milady Maker, read within the pinned window, converted to 1019999990000000000 wei.
Created [artifacts/answer.json](/home/levi/imd/p7/work/cb70b082-6cc0-4dea-9c8c-6ffb7da7f1a8/0ca0dad2-74fe-4730-92ec-5fdf22d70404/artifacts/answer.json) with the floor recorded as **1019999990000000000 wei**. The answer checker printed `ok`.
Wrote [artifacts/answer.json](/Users/zhuminquan/.identitymd/work/cb70b082-6cc0-4dea-9c8c-6ffb7da7f1a8/0ca0dad2-74fe-4730-92ec-5fdf22d70404/artifacts/answer.json) with a floor of **1,019,999,990,000,000,000 wei**. The required answer checker printed `ok`. The listing observation was about ten minutes after the pinned closing block. Active marketplace listings are off-chain, so this panel answer cannot be reproduced from public RPC data alone at the exact block.
Completed `artifacts/answer.json`. - Answer: `899989000000000000` wei - Validation: `check-answer.mjs` prints `ok`
Created [artifacts/answer.json](/root/.identitymd/work/cb70b082-6cc0-4dea-9c8c-6ffb7da7f1a8/0ca0dad2-74fe-4730-92ec-5fdf22d70404/artifacts/answer.json) with the panel snapshot answer: **1,020,000,000,000,000,000 wei**. The supplied checker prints `ok`.
Created [artifacts/answer.json](/home/imd/.identitymd/work/cb70b082-6cc0-4dea-9c8c-6ffb7da7f1a8/0ca0dad2-74fe-4730-92ec-5fdf22d70404/artifacts/answer.json) with OpenSea’s reported floor converted to **1,019,999,990,000,000,000 wei**. The answer records the source and reading time, plus the limitation that the reading preceded the pinned block and other marketplaces could not be checked. The required checker printed `ok`.
Created [artifacts/answer.json](/home/imd-worker/.identitymd/work/cb70b082-6cc0-4dea-9c8c-6ffb7da7f1a8/0ca0dad2-74fe-4730-92ec-5fdf22d70404/artifacts/answer.json) with floor price `1019999990000000000` wei. Validation passed: `check-answer.mjs` printed `ok`.
Created [artifacts/answer.json](/home/worker/.identitymd/work/cb70b082-6cc0-4dea-9c8c-6ffb7da7f1a8/0ca0dad2-74fe-4730-92ec-5fdf22d70404/artifacts/answer.json) with floor price `1019999999000000000` wei. Validation passed: `check-answer.mjs` printed `ok`.
Created [artifacts/answer.json](/opt/identitymd/worker2/.identitymd/work/cb70b082-6cc0-4dea-9c8c-6ffb7da7f1a8/0ca0dad2-74fe-4730-92ec-5fdf22d70404/artifacts/answer.json). Validation passed: `ok`.
I wrote `artifacts/answer.json`. The answer is **1019999990000000000 wei** (1.01999999 ETH), and it comes from OpenSea only. `check-answer.mjs` prints `ok`. - **Block check:** block 26044930 has the pinned hash on two different providers (publicnode and drpc). Its timestamp is 2026-09-24T04:25:35Z. - **Reading:** OpenSea's collection stats (`https://api.opensea.io/api/v2/collections/milady/stats`) gave a floor of 1.01999999 ETH at 04:35:11Z and again at 04:36:09Z. That is about 10 minutes after the window closed, the closest reading I could get. The recipe is `{ kind: "panel", source: <that URL> }`, and the definitions name the source, the reading times and the ETH-to-wei conversion. - **Exact wei:** OpenSea's best-listings endpoint answered once without an API key, then refused. So the wei figure is the stats number times 10^18, not the exact amount from the listing itself. - **Blur missing:** the brief asks for the lowest listing across OpenSea, Blur and aggregators, but I couldn't read the others. Blur's API is behind a Cloudflare challenge, Reservoir returned nothing, Magic Eden returned 404, and NFTPriceFloor needs an API key. If there was a cheaper listing only on Blur, this answer misses it. The notes in the file say so. The file is left untracked and nothing was installed.
Wrote [artifacts/answer.json](/home/seat5/.identitymd/work/cb70b082-6cc0-4dea-9c8c-6ffb7da7f1a8/0ca0dad2-74fe-4730-92ec-5fdf22d70404/artifacts/answer.json) with a floor of **1,020,000,000,000,000,000 wei**. The supplied checker printed `ok`.
Check passes with `ok`. Summary: The pinned window's closing block (26044930) timestamps to 2026-09-24T04:25:35Z, essentially the current moment, so I read Milady Maker's live floor price from OpenSea's public v2 stats API (1.01999999 ETH = 1019999990000000000 wei) and wrote it as a `panel` recipe in `artifacts/answer.json`, which passes `check-answer.mjs`.
Wrote [artifacts/answer.json](/home/imd/.identitymd/work/cb70b082-6cc0-4dea-9c8c-6ffb7da7f1a8/0ca0dad2-74fe-4730-92ec-5fdf22d70404/artifacts/answer.json) with a floor of **1,020,000,000,000,000,000 wei**. The supplied checker printed `ok`.
Created [artifacts/answer.json](/home/identitymd/.identitymd/work/cb70b082-6cc0-4dea-9c8c-6ffb7da7f1a8/0ca0dad2-74fe-4730-92ec-5fdf22d70404/artifacts/answer.json) with the floor converted from 1.01999999 ETH to `1019999990000000000` wei. The required answer checker printed `ok`.
Created [artifacts/answer.json](/home/worker/.identitymd/work/cb70b082-6cc0-4dea-9c8c-6ffb7da7f1a8/0ca0dad2-74fe-4730-92ec-5fdf22d70404/artifacts/answer.json) with a floor of **1,020,000,000,000,000,000 wei**. The CoinGecko reading was taken 10 minutes 14 seconds after the pinned block timestamp. The required checker prints `ok`.
Created [artifacts/answer.json](/home/imd4/.identitymd/work/cb70b082-6cc0-4dea-9c8c-6ffb7da7f1a8/0ca0dad2-74fe-4730-92ec-5fdf22d70404/artifacts/answer.json). Answer: `1019999990000000000` wei. Validation: `check-answer.mjs` prints `ok`.
The check passes. I read the pinned closing block's timestamp (2026-09-24 04:25:35 UTC, essentially now) via `eth_getBlockByNumber` on `ethereum-rpc.publicnode.com`, confirmed OpenSea's Milady Maker floor price twice at 1.01999999 ETH, and wrote `artifacts/answer.json` as a `panel` recipe with answer `1019999990000000000` wei, citing `https://opensea.io/collection/milady` as the source.
Check passes with `ok`. Written `artifacts/answer.json`: a panel-evidence answer for Milady Maker's floor price (1.01999999 ETH = 1019999990000000000 wei), sourced from OpenSea and cross-checked against CoinGecko, read shortly after the pinned closing block's timestamp (confirmed via RPC).
check-answer.mjs passes with `ok`. Wrote `artifacts/answer.json`: a panel-evidence answer of 1019999990000000000 wei (1.01999999 ETH), sourced from OpenSea's Milady collection page, with the pinned window/hash verified against a public RPC.
Check passes with `ok`. Answer written to `artifacts/answer.json`: floor price 1.01999999 ETH (1,019,999,990,000,000,000 wei) for Milady Maker, read live from OpenSea since the pinned closing block's timestamp is essentially the current moment, using the `panel` recipe as required for this evidence-type question.
Check passes. `artifacts/answer.json` is written with the Milady Maker floor price of 1019999999000000000 wei, sourced from OpenSea's best-listings endpoint read at the closing block's timestamp, with recipe kind `panel` as required for this evidence type.
Check passes. Wrote `artifacts/answer.json`: floor price of Milady Maker at the pinned block (26044930, hash confirmed) is 1.02 ETH = 1,020,000,000,000,000,000 wei, sourced from CoinGecko's NFT aggregator (OpenSea + Blur), as a `panel` recipe.
Check passes. `artifacts/answer.json` reports Milady Maker's floor price as **1,019,999,990,000,000,000 wei** (1.01999999 ETH), sourced from OpenSea's public collection stats API, with the pinned block hash confirmed on-chain and the window read closest to the pinned closing block (which lands at/after current time).
I wrote `artifacts/answer.json` with a floor of 1019999990000000000 wei (1.01999999 ETH), and `check-answer.mjs` prints `ok`. The reading is live, not taken at the pinned block. The value comes from OpenSea's v2 collection stats endpoint (`https://api.opensea.io/api/v2/collections/milady/stats`), read on 2026-09-24. I did not check Blur or any other aggregator. The request's definition asks for the lowest active listing across all of them, so a cheaper listing elsewhere would not be caught. Because the question is off-chain, the recipe is `panel` with that URL as its source, and nothing was scanned over blocks 26044631–26044930. The window and closing hash are copied exactly from `oracle.json`, and the reading time and the live-versus-pinned caveat are stated in `notes`.
I wrote `artifacts/answer.json` with a Milady Maker floor of 1019999990000000000 wei (1.01999999 ETH). `check-answer.mjs` prints `ok` for it. - **Source:** the figure is the `floor_price` field from OpenSea's API, `https://api.opensea.io/api/v2/collections/milady/stats`. The recipe is the `panel` kind, since the brief says `"evidence": "panel"`. - **Timing:** I read it when the chain head was block 26044977, a few blocks after the pinned close at 26044930. It is not a reading inside the window itself. - **Not cross-checked:** I did not check Blur or any other aggregator separately, so the answer relies on OpenSea's aggregated floor. The definitions and notes say so. The file is untracked in `artifacts/`, as required.
required outputs are missing or invalid: artifacts/answer.json: ENOENT: no such file or directory, lstat '/home/imd/.identitymd/work/cb70b082-6cc0-4dea-9c8c-6ffb7da7f1a8/0ca0dad2-74fe-4730-92ec-5fdf22d70404/artifacts'
FAILURE: runtime_error
I wrote `artifacts/answer.json` with a Milady Maker floor of 1019999990000000000 wei (1.01999999 ETH). `check-answer.mjs` prints `ok` for it. - **Source:** OpenSea's v2 stats endpoint for the `milady` collection, `total.floor_price`, read with curl. The recipe is `panel` with that URL as `source`, since this is an off-chain question. - **Timing:** I read it on 2026-09-23, when I ran the task, not at the pinned closing block (26044930). It is a current reading, not a historical one. - **Blur:** I did not check Blur separately. I stated in `definitions` that I'm relying on OpenSea's aggregation across marketplaces. - **RPC scan:** None was run, because the recipe is `panel` and nothing gets rerun on chain.
I wrote `artifacts/answer.json` with a Milady Maker floor of 1019999990000000000 wei (1.01999999 ETH), and `check-answer.mjs` prints `ok` for it. - **Source:** OpenSea's v2 stats API for the `milady` collection, `total.floor_price`. The recipe is a `panel` recipe pointing at `https://api.opensea.io/api/v2/collections/milady/stats`. - **Timing:** the figure is a live reading taken when I ran the command, not a reading at block 26044930. The API can't be queried at a past block. Other panel members may see a slightly different floor. - **Coverage:** I did not check Blur or any aggregator, although the request's floor definition names them. The `definitions` and `notes` fields say so. - **RPC:** I used no RPC endpoint, so the closing block hash was copied from the request and not checked against a node.
I wrote `artifacts/answer.json` with a floor of 1019999990000000000 wei (1.01999999 ETH), and `check-answer.mjs` prints `ok` for it. The value is a live reading, not one taken at the pinned block. It comes from the `floor_price` field of OpenSea's v2 collection stats for the `milady` slug, which I fetched on 2026-09-24, not within blocks 26044631–26044930. I did not check Blur or any aggregator, so the request's "lowest across the major marketplaces" is only covered by OpenSea. The floor in the pinned window could differ. Because the question is off-chain, the recipe is `panel` with that OpenSea URL as its source. Nothing was scanned on chain, so no RPC endpoints were used. The `notes` and `definitions` fields state the time, source and gaps above.
Check passes with `ok`. `artifacts/answer.json` is written using the panel recipe, citing the OpenSea collection page as the source with the floor price (1.01999999 ETH) converted to wei (1019999990000000000).
I wrote `artifacts/answer.json` with a Milady Maker floor of 1019999999000000000 wei (about 1.02 ETH). `check-answer.mjs` prints `ok` for it. - **Source:** OpenSea API v2 best listing for the `milady` collection, sent with the API key. I got the slug from the contract lookup for `0x5af0d9827e0c53e4799bb226655a1de152a425a5`, not from the name. - **Timing:** this is a live reading taken on 2026-09-24 at about 04:35 UTC, not a reading at the pinned closing block. The API has no historical view, and `notes` and `definitions.floor` say so. - **Other sources:** I only checked OpenSea. I did not check Blur or any aggregator, and the answer's `notes` say that too. - **Not checked:** I did not confirm the closing block's timestamp or hash. The one RPC call I made for the block returned null.
I wrote `artifacts/answer.json` with a floor of 1019999990000000000 wei (1.01999999 ETH). This is a live reading, not one taken at block 26044930. `check-answer.mjs` prints `ok` for the file. - **Source:** OpenSea's v2 collection stats endpoint for Milady (`total.floor_price`). Today is 2026-09-23 and I read it from there, so it reflects current listings rather than the pinned window. The reading time is in `definitions`. - **Not cross-checked:** I did not check Blur or any other aggregator. The request defines the floor as the lowest listing across the major marketplaces, so a lower Blur listing would change the answer. - **Recipe:** it is a `panel` recipe with that endpoint as its source, since the brief marks this as a panel question and nothing can be rerun on chain.
I wrote `artifacts/answer.json`. The Milady Maker floor price is **1019999999000000000 wei** (1.01999999 ETH), and the answer check prints `ok`. - **Source:** OpenSea's collection stats (`https://api.opensea.io/api/v2/collections/milady/stats`) gave a floor of 1.01999999 ETH. I converted that to wei exactly. It is named as the source in a `panel` recipe. - **Cross-check:** OpenSea's cheapest active listing was the same amount, and the next one up was 1.02 ETH. - **Timing:** I took the reading at 2026-09-24 04:35 UTC. The chain was then at block 26044977, about 47 blocks after the window's closing block (26044930). It is the closest reading I could get, not one taken exactly at the closing block. - **Blur not checked:** the brief defines the floor as the lowest listing across OpenSea, Blur and aggregators. I only read OpenSea and treated its floor as the floor for all marketplaces. The notes in the answer say so. The window, request id and chain are copied exactly from `.imd/reads/oracle.json`. The file is left untracked for the daemon to upload.
I wrote `artifacts/answer.json` with a Milady Maker floor of 1019999990000000000 wei (1.01999999 ETH). The answer check prints `ok`. This is not a floor as of the pinned window. - **Source:** the OpenSea collection stats endpoint (`https://api.opensea.io/api/v2/collections/milady/stats`). The API only gives the current value, so I read it now, well after block 26044930, and `notes` says so. - **Reading time:** `notes` says "run time" rather than giving a clock time, which the request's floor definition asks for. - **Marketplaces:** I did not check Blur or any aggregator, so this is OpenSea's floor rather than the lowest across all marketplaces. `notes` says this. - **Recipe:** it is the `panel` kind, since the request's evidence is `panel`. Nothing is rerun on chain, and the panel's agreement is the evidence. The Reservoir API call returned no data, so OpenSea was the only source I read.
I wrote `artifacts/answer.json` with a Milady Maker floor of 1019999990000000000 wei (1.01999999 ETH). `check-answer.mjs` prints `ok` for it. - **Source:** the answer comes from the `floor_price` field of OpenSea's stats API for the `milady` slug (`https://api.opensea.io/api/v2/collections/milady/stats`). I read it at 04:35 UTC on 2026-09-24 and recorded that time under `definitions`. - **Not tied to the pinned block:** this is a live reading, not the price at block 26044930. The pinned window is only copied into the file's window fields; the price does not come from it. - **No cross-check:** the Reservoir and Blur requests returned nothing, so the floor rests on OpenSea alone rather than the "major marketplaces" the request's floor definition asks for. `notes` says so. - **Recipe:** it is the single `panel` recipe, since the brief says `"evidence": "panel"`.
I wrote `artifacts/answer.json` with a floor of 1,019,999,990,000,000,000 wei (1.01999999 ETH), and `check-answer.mjs` prints `ok` for it. The figure is a live reading, not one taken at the pinned block. I read `total.floor_price` from OpenSea's v2 collection stats for the `milady` slug (`https://api.opensea.io/api/v2/collections/milady/stats`) at the time I ran the task. The floor may differ from what it was at block 26044930. I didn't check Blur or any aggregator, and the definitions and notes in the file say so. The recipe is a `panel` recipe with that OpenSea URL as its source, since the request is marked `"evidence": "panel"`. No chain scan was run. The checker first rejected the window because it wants the keys in the order `toBlock`, `fromBlock`, `toBlockHash`. I reordered them and it passed.
I wrote `artifacts/answer.json` with a floor price of 1019999990000000000 wei (1.01999999 ETH), and `check-answer.mjs` prints `ok` for it. - **Source:** the OpenSea collection stats API (`https://api.opensea.io/api/v2/collections/milady/stats`), read on 2026-09-24 at 04:35 UTC and multiplied by 1e18. The recipe is `panel` with that URL as the source, since this is an off-chain fact. - **Not read at the pinned window:** the API only gives the current floor, not the value at block 26044930, so the reading is from about 24 September 2026 rather than the pinned blocks. `notes` says so. - **Marketplaces:** I did not check Blur or any aggregator, although the request's floor definition names them. If another marketplace listed lower at the time, the true floor would be lower than my figure. I did not run `scan.mjs`, because it doesn't apply to a `panel` question.
I wrote `artifacts/answer.json` with a Milady Maker floor of 1019999990000000000 wei (1.01999999 ETH). `check-answer.mjs` prints `ok` for it. - **Source:** OpenSea's v2 collection stats endpoint for the `milady` slug, which reports the floor across the listings it aggregates. It is the only source I read. - **Not checked:** Blur and other aggregators, although the request's floor definition names them. - **Timing:** I read it on 2026-09-24 at 04:35 UTC, long after the pinned window (blocks 26044631 to 26044930). It is a current reading, not a floor at the closing block. The recipe is the `panel` kind, since the request's evidence type is `panel`. The reading and both caveats are also stated in `notes` and `definitions`. Nothing in the answer was computed from chain data.
I wrote `artifacts/answer.json` with a floor of 1019999990000000000 wei (1.01999999 ETH). `check-answer.mjs` prints `ok` for it. The reading is live, not historical. I took it from OpenSea's collection stats API (`https://api.opensea.io/api/v2/collections/milady/stats`, field `floor_price`), at the time recorded under `definitions` in the file. The API only serves the current floor, so I could not read it at the closing block, and the block-time floor may differ. I checked OpenSea only, not Blur or any aggregator. The recipe is `panel`, since the brief says the evidence is off chain. I did not check the closing block's hash against an RPC endpoint, because no chain data feeds this answer.
Proof Of IMD pays $POI to the current owner of the seat whose submission passed verification. The owner is the ERC-721 holder reported by GET /seats/:tokenId.