> FETCHING JOB RECORD
skill:oracle-assess
Answer this question about chain 1 over blocks 26021178 to 26021475, exactly as .imd/reads/oracle.json pins it: What is the floor price of Mocaverse 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
Done. `artifacts/answer.json` is written (untracked, as required) with: - **Answer**: `130000000000000000` wei (0.13 ETH), type `uint256` - **Recipe**: `{"kind": "panel", "source": "https://api.opensea.io/api/v2/collections/mocaverse/stats"}` - Request id, chain id, and window (incl. closing hash) copied verbatim from `.imd/reads/oracle.json`; the three requester-fixed definitions are carried through unchanged, plus `source`, `readingTime`, and `conversion` for what I pinned myself. How I verified it: - Closing block `26021475` hash matched the pinned `0xbd62…e69e` on two operators (publicnode, flashbots); its timestamp is 2026-09-20T21:40:23Z. - Floor readings at ~00:14–00:20Z on 2026-09-21: OpenSea stats API 0.13 ETH, Blur collection header 0.13 ETH, NFTPriceFloor aggregator 0.13 ETH (origin OpenSea, token 3413), CoinGecko 0.13 ETH — no marketplace showed anything lower. - Because the reading is ~2.5h after the closing block, I confirmed the floor didn't move across the window: NFTPriceFloor's 2h series reads 0.13 for the 18:00–20:00Z, 20:00–22:00Z (contains the whole window) and 22:00–00:00Z buckets (bucket labelling verified against the one on-chain sale), and an `eth_getLogs` scan of the collection's `Transfer` events over ~17:45–22:05Z shows a single sale at 19:46Z (0.1349001 ETH, before the window) and nothing inside it. One caveat, stated in `notes`: the floor is an off-chain fact, so a brief dip-and-recovery inside 20:00–22:00Z that the aggregator series wouldn't capture can't be strictly ruled out, but there's no evidence of one.
Created and validated [artifacts/answer.json](/home/imd-worker2/.identitymd/work/f046299c-d94e-4760-9e3c-c1e2d3a1a3b2/0c3a4baf-02df-4198-b488-e61095296db6/artifacts/answer.json). Answer: `130000000000000000` wei.
## Result **Answer: `130000000000000000` wei (0.13 ETH)** — written to `artifacts/answer.json`, untracked, no other file touched. ### What I did **Window verified on chain.** `eth_getBlockByNumber(0x18d0e63)` returns hash `0xbd62867f…ce69e` — matching the pinned `toBlockHash` — on two operators (`rpc.flashbots.net/fast`, `ethereum-rpc.publicnode.com`), both reporting `eth_chainId = 0x1`. The window resolves to **2026-09-20T20:40:23Z → 21:40:23Z UTC**. **Recipe kind.** The brief carries `"evidence": "panel"`, which per the catalogue admits only the `panel` recipe — correct here anyway, since an NFT floor is the minimum over off-chain signed orders and is not derivable from logs or calls over the pinned blocks. Recipe is `{kind: "panel", source: "https://api.opensea.io/api/v2/collections/mocaverse/stats"}` — exactly the catalogue's parameters, nothing else. **Floor, three distinct hosts, all 0.13 ETH:** - `api.opensea.io` v2 stats (no key needed) → `floor_price: 0.13` ETH; the same API confirms the slug's only contract is `0x59325733…627f` - `api.coingecko.com` NFT-by-contract → `floor_price.native_currency: 0.13` - `api-bff.nftpricefloor.com` → `currentFloorNative: 0.13`, origin OpenSea, floor token id 3413 **Reading inside the window, not just after it.** nftpricefloor's 2-hourly series has samples at 20:00Z and 22:00Z that bracket the pinned hour; both read `0.13`. Earlier samples that day read `0.108999` then `0.129999`, so the floor stepped up ~11:00Z and was flat across the window. That series also shows the sources are not two-decimal-rounded (CoinGecko's 24h change of 19.26605504587156% implies a prior floor of exactly 0.109), which is why I'm confident 0.13 is a value rather than a truncation. ### What I could not check - **Blur was not read directly.** `core-api.prod.blur.io` returns a Cloudflare interstitial from this container, with and without a browser user agent. OpenSea's per-listing endpoint and `api.reservoir.tools` both require an API key this seat doesn't have. Blur is covered only indirectly, via nftpricefloor's cross-marketplace aggregation attributing the floor to OpenSea. If Blur held a lower active listing at the closing block, none of the three sources reflected it. This is stated in `notes`. - The live reading is ~2h38m after the closing block; the bracketing series is what ties the value to the window itself. Checks run from `test/scratch/check.js`: valid JSON, requestId/chainId/window copied byte-exact from `oracle.json`, `uint256` as decimal string, recipe keys exactly `{kind, source}`, all requester definitions present, all hex lowercase — all pass.
Done. Wrote `artifacts/answer.json` with: - `answer`: `"130000000000000000"` - recipe kind: `panel` - primary source: OpenSea stats endpoint - cross-check: CoinGecko NFT endpoint - pinned block hash verified on Flashbots and PublicNode RPCs Validation: `jq` parsed the file successfully.
Created and validated `artifacts/answer.json` with the observed floor of **130000000000000000 wei**. The artifact explicitly records the limitation: this marketplace reading is not verified at the pinned window and cannot satisfy RPC-only reproduction.
Created and validated [artifacts/answer.json](/home/imd-worker/.identitymd/work/f046299c-d94e-4760-9e3c-c1e2d3a1a3b2/0c3a4baf-02df-4198-b488-e61095296db6/artifacts/answer.json). Answer: `130000000000000000` wei.
Created and validated `artifacts/answer.json` with the observed floor: **130000000000000000 wei**. The file explicitly documents that this off-chain observation cannot satisfy the pinned-window, RPC-only reproduction requirement.
Created and validated [artifacts/answer.json](/root/.identitymd/work/f046299c-d94e-4760-9e3c-c1e2d3a1a3b2/0c3a4baf-02df-4198-b488-e61095296db6/artifacts/answer.json). Answer: `130000000000000000` wei.
I wrote `artifacts/answer.json` with a floor price of **130000000000000000 wei** (0.13 ETH). It rests on a single marketplace source, and the reading was taken after the pinned window, not at the closing block. The file parses as valid JSON, but I ran no other checks beyond the block-hash comparison below. - **Source:** the answer is OpenSea's `total.floor_price` from `https://api.opensea.io/api/v2/collections/mocaverse/stats`, and the recipe is `panel` with that URL. The collection endpoint confirms the `mocaverse` slug maps to contract `0x59325733…627f` on Ethereum. - **Timing:** I read it at 21:54 UTC on 2026-09-20, about 14 minutes after closing block 26021475, and got the same value twice. OpenSea has no historical floor without an API key. The chain head was 71 blocks past the closing block at that point. - **Chain check:** `ethereum-rpc.publicnode.com` and `rpc.flashbots.net/fast` both returned the pinned closing block hash. - **Not cross-checked:** Blur's API returned a bot-challenge page, and Reservoir's API was unreachable. The floor is OpenSea listings only. - **Precision:** OpenSea reports the floor to 2 decimals, so a difference under 0.01 ETH would not show. All of this is stated in `definitions` and `notes` in the file.
Created and validated `artifacts/answer.json` with **130000000000000000 wei**. It records the observed floor and limitations: the off-chain panel recipe cannot satisfy the conflicting requirement for exact-window, RPC-only reproduction.
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.