> FETCHING JOB RECORD
skill:oracle-assess
Answer this question about chain 1 over blocks 26021224 to 26028370, exactly as .imd/reads/oracle.json pins it: What is the current listing floor price of CryptoDickbutts on Ethereum mainnet, in wei (1 ETH = 10^18 wei)? Identify the exact collection from CoinGecko NFT id cryptodickbutts; verify its mainnet contract and any project/token-id restrictions. Independently attempt BOTH CoinGecko NFT API and OpenSea v2 collection stats/listings APIs. Cross-check the latest up to 3 sales in the pinned 24-hour block window via transaction receipts and decoded marketplace sale events when possible. Follow the definitions, report API access failures and source timestamps, and explain discrepancies. Do not substitute a last sale price for the listing floor or fabricate unavailable data. Return a panel recipe and cite the actual floor source URL; include both API attempts and onchain evidence in notes. 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 [artifacts/answer.json](/root/.identitymd/work/817a4689-c97b-4f88-9920-f214d41b9d7e/25c5a24d-4af4-482f-99db-3ff4de14eefb/artifacts/answer.json). Validated with the supplied checker: `ok`.
Completed [artifacts/answer.json](/root/.identitymd/work/817a4689-c97b-4f88-9920-f214d41b9d7e/25c5a24d-4af4-482f-99db-3ff4de14eefb/artifacts/answer.json). Validated successfully: `check-answer.mjs` prints `ok`.
Created [artifacts/answer.json](/home/worker/.imd/seat2/work/817a4689-c97b-4f88-9920-f214d41b9d7e/25c5a24d-4af4-482f-99db-3ff4de14eefb/artifacts/answer.json). Answer: `588443000000000000` wei. Validation passed: `check-answer.mjs` printed `ok`.
Completed [artifacts/answer.json](/home/identitymd/.identitymd/work/817a4689-c97b-4f88-9920-f214d41b9d7e/25c5a24d-4af4-482f-99db-3ff4de14eefb/artifacts/answer.json). It reports the fresh CoinGecko listing floor as `588443000000000000` wei, includes both provider attempts and decoded pinned-window sales evidence. Validator result: `ok`.
Created and validated [artifacts/answer.json](</home/imd2/.identitymd/work/817a4689-c97b-4f88-9920-f214d41b9d7e/25c5a24d-4af4-482f-99db-3ff4de14eefb/artifacts/answer.json). The checker reports `ok`.
Taylor — `artifacts/answer.json` written and checked, prints `ok`. Floor: 0.588443 ETH = 588443000000000000 wei, from CoinGecko's `nfts/cryptodickbutts` (contract `0x42069abfe407c60cf4ae4112bedead391dba1cdb`, verified). OpenSea v2 stats returned 401 (no API key) and the collection page didn't expose a floor, so it's a single-source answer — documented as such rather than faked. Onchain check via `scan.mjs` confirmed the pinned block/hash and found 7 Transfer logs in the window (roughly consistent with CoinGecko's 3 reported sales), but I didn't decode individual Seaport sale events for exact prices given the time budget — noted as a limitation, not fabricated.
Completed [artifacts/answer.json](</home/seat2/.identitymd/work/817a4689-c97b-4f88-9920-f214d41b9d7e/25c5a24d-4af4-482f-99db-3ff4de14eefb/artifacts/answer.json>). - Floor answer: `588443000000000000` wei - Includes CoinGecko and OpenSea API attempts, contract scope, pinned-window sales evidence, and discrepancy notes. - Validator result: `ok`
I wrote `artifacts/answer.json` with a floor of 588443000000000000 wei (0.588443 ETH), and `check-answer.mjs` prints `ok`. It rests on CoinGecko alone, and I did not do the onchain sales cross-check. - **Floor source:** the CoinGecko NFT API for `cryptodickbutts`, fetched live on 2026-09-21 at 21:23:48 UTC (HTTP 200). It reports the Ethereum contract `0x42069abfe407c60cf4ae4112bedead391dba1cdb`, and `floor_price.native_currency` is 0.588443 ETH. The payload has no `last_updated` field, so I could not check its freshness beyond the live fetch. - **OpenSea:** the v2 stats endpoint returned 401 (missing API key), and no credentials were available. The slug `cryptodickbutts-s3` was a guess I never verified. So I had no OpenSea floor and no percentage difference to report. The answer takes the CoinGecko floor because OpenSea was unavailable. - **Onchain sales:** I did not decode Seaport `OrderFulfilled` events or receipts for blocks 26021224–26028370, so no sales are reported. CoinGecko shows 3 sales in 24 hours, unverified onchain. `notes` says all of this. - **Recipe:** `panel`, with source `https://api.coingecko.com/api/v3/nfts/cryptodickbutts`.
Check passes with `ok`. Summary: `artifacts/answer.json` answers the CryptoDickbutts floor question with a `panel` recipe citing OpenSea's collection page (`https://opensea.io/collection/cryptodickbutts-s3`), answer `588351059000000000` wei (0.588351059 ETH). Both CoinGecko (API succeeded, 0.588443 ETH) and OpenSea (API 401'd, fell back to the official page, 0.588351059 ETH) were attempted and cross-checked (0.0156% apart); one genuine on-chain sale bundle (3 Seaport-decoded sales at ~0.47 ETH, block 26027224) was found and reported as corroborating evidence, not substituted for the floor.
Created [artifacts/answer.json](/home/imd-worker/.identitymd/work/817a4689-c97b-4f88-9920-f214d41b9d7e/25c5a24d-4af4-482f-99db-3ff4de14eefb/artifacts/answer.json). Answer: `588443000000000000` wei. Validator result: `ok`.
I wrote `artifacts/answer.json` with a floor of **588352060000000000 wei** (0.58835206 ETH), and `check-answer.mjs` prints `ok`. The on-chain sales cross-check the task asked for was not done. - **Source:** OpenSea v2 stats for `cryptodickbutts-s3` returned HTTP 200 without a key, with `floor_price_symbol` ETH. The recipe is a `panel` recipe citing that URL. I guessed the slug and it worked, rather than resolving it from the contract or collection links as the definitions require. - **Cross-check:** CoinGecko `cryptodickbutts` returned HTTP 200 with a floor of 0.588443 ETH, about 0.015% higher. It also gave contract `0x42069abfe407c60cf4ae4112bedead391dba1cdb` on Ethereum. That is under the 1% threshold, so I chose OpenSea per the floor rule. - **Timestamps:** I retrieved both at 2026-09-21T21:21:45Z. Neither response supplied a `last_updated` field. - **Not done:** I did not fetch receipts or decode Seaport sale events for the latest sales in the pinned blocks. I also did not verify the contract on chain over RPC. The notes in the answer say so. - **Window:** The floor is a live API value, not derived from the pinned block range.
I wrote `artifacts/answer.json` with a floor of 588443000000000000 wei (0.588443 ETH), and `check-answer.mjs` prints `ok`. Only one of the two providers returned a floor, and the sales cross-check was not done. - **CoinGecko:** `https://api.coingecko.com/api/v3/nfts/cryptodickbutts` returned HTTP 200 with `floor_price.native_currency` 0.588443 ETH, retrieved 2026-09-21T21:21Z. The response has no `last_updated` field that I could find, so freshness is only the retrieval time. - **Collection and contract:** CoinGecko gives the contract as `0x42069abfe407c60cf4ae4112bedead391dba1cdb` on Ethereum, and `eth_getCode` on publicnode confirmed it has code on chain 1. I treated it as a standalone contract with no project or token-id restriction. - **OpenSea:** the stats API returned 401 (missing API key). The slug `cryptodickbutts-v3` was my guess and I did not verify it. The collection page returned 200, but I did not extract a floor from it. So there is no OpenSea floor and no percentage difference between providers. I used CoinGecko under the fallback rule. - **Sales:** I did not decode any sales from transaction receipts, and the OpenSea API was unavailable for discovering them. The notes state this. CoinGecko shows 1.41 ETH of 24-hour volume, so sales probably exist but are unverified. - **Recipe:** it is a `panel` recipe with the CoinGecko URL as `source`. - **Block hash:** I did not check the pinned closing block hash on an RPC.
I wrote `artifacts/answer.json` with a floor of 588443000000000000 wei (0.588443 ETH), and `check-answer.mjs` prints `ok` for it. I did not do the onchain sales cross-check, and the OpenSea check failed. - **Floor source:** CoinGecko `https://api.coingecko.com/api/v3/nfts/cryptodickbutts` returned 200 at 2026-09-21T21:21:33Z. `floor_price.native_currency` is 0.588443 ETH. The response has no `last_updated` field, so freshness rests on the live fetch. - **Scope:** the CoinGecko listing gives the Ethereum contract `0x42069abfe407c60cf4ae4112bedead391dba1cdb`. I took it as a dedicated ERC721 contract and did not check it onchain. - **OpenSea:** `https://api.opensea.io/api/v2/collections/cryptodickbutts-1/stats` returned 401 ("Missing an API Key"), and no key was available. I guessed that slug rather than verifying it, and I did not try the opensea.io collection page. - **Sales:** I did not fetch receipts or decode Seaport events. CoinGecko reports 3 sales in the last day averaging 0.47 ETH, which is below the floor. I did not use that figure for the answer. - **Recipe:** the recipe is `panel`, with the CoinGecko URL as its source. The notes state the OpenSea failure and the missing sales check.
Created [artifacts/answer.json](/Users/sagark/.identitymd/work/817a4689-c97b-4f88-9920-f214d41b9d7e/25c5a24d-4af4-482f-99db-3ff4de14eefb/artifacts/answer.json). Validated successfully: `check-answer.mjs` prints `ok`.
`artifacts/answer.json` is written and untracked (excluded by `.git/info/exclude`), and `check-answer.mjs` prints **ok**. ## Answer **588362150000000000 wei** (0.58836215 ETH) — CryptoDickbutts S3 listing floor. **How it was established** *Collection scope.* CoinGecko id `cryptodickbutts` → contract `0x42069abfe407c60cf4ae4112bedead391dba1cdb`, platform ethereum, rank 28 (matches the brief's ranking pin). `eth_call` at latest confirms name `CryptoDickbutts S3`, symbol `CDB`, totalSupply 5200 — a dedicated ERC721, so no project/token-id filter applies. The OpenSea slug is **not** the CoinGecko id: the bare slug `cryptodickbutts` is a different, much smaller collection (floor 1.69 ETH, 119 owners) and was rejected on contract mismatch; `cryptodickbutts-s3` is `safelist_status: verified` with exactly that contract. *Both providers attempted, both fresh.* - OpenSea `/api/v2/collections/cryptodickbutts-s3/stats` — HTTP 200 three times (21:12:45Z, 21:13:01Z, 21:13:56Z UTC), identical: `total.floor_price 0.58836215`, `floor_price_symbol ETH`, header age 31s. - CoinGecko `/api/v3/nfts/cryptodickbutts` — HTTP 200 at 21:12:45Z and 21:13:56Z (one intervening 429, no key available): `floor_price.native_currency 0.588443`, `native_currency ethereum`. - **Failure reported:** OpenSea `/listings/collection/.../best` and `/all` both returned **401 "Missing an API Key"**, so the per-listing ladder could not be enumerated. Difference is **+0.0137%** (under 1%), attributable to refresh lag on a rising floor (CoinGecko reports +17.92% in 24h), not scope. Per `floorRule` the OpenSea figure is selected and no averaging was done. *Onchain corroboration over exactly blocks 26021224–26028370.* Pinned closing hash confirmed on two independent operators (flashbots, publicnode). The scan found 7 ERC721 Transfers; receipts decoded to **exactly 3 Seaport 1.6 sales**, all in tx `0xdddad4a5…afae` at block 26027224 — tokens 755/3804/1856 at 0.46999899 / 0.469999 / 0.47 ETH total consideration (seller + fee, native ETH). Their sum, **1.40999799 ETH**, reproduces OpenSea's `one_day` volume and CoinGecko's `volume_24h`/`one_day_sales` exactly. The other 4 transfers are a wallet round-trip with no sale event and were excluded. The sales sit ~20% *below* the floor because the sweep consumed the cheapest listings — noted as a discrepancy and explicitly not substituted for the floor.
Checker prints `ok`. Answer: floor = **588361158000000000 wei** (0.588361158 ETH) for CryptoDickbutts Series 3 (contract `0x42069abfe407c60cf4ae4112bedead391dba1cdb`, OpenSea slug `cryptodickbutts-s3`) — the collection the CoinGecko id `cryptodickbutts` actually points to, distinct from OpenSea's similarly-named `cryptodickbutts` (OG) collection at a different contract, which was excluded per scope. `artifacts/answer.json` written with both API attempts, the contract-mismatch discrepancy, and onchain Seaport sale evidence from block 26027224 in the pinned window.
I wrote `artifacts/answer.json` with a floor of **588443000000000000 wei** (0.588443 ETH), and `check-answer.mjs` prints `ok`. This is a CoinGecko-only answer: OpenSea gave no floor, and I did not run the onchain sales cross-check. - **CoinGecko:** `https://api.coingecko.com/api/v3/nfts/cryptodickbutts` returned HTTP 200 at 2026-09-21T21:12:30Z. It shows the collection at contract `0x42069abfe407c60cf4ae4112bedead391dba1cdb` on Ethereum, with `floor_price.native_currency` 0.588443 ETH. The response has no `last_updated` field, so freshness rests on the fetch time. - **OpenSea:** the stats API returned 401 because there is no API key. The `cryptodickbutts-1` slug is my guess and is unverified. The collection page loaded (200), but I could not parse a floor from its HTML, so it gave no verifiable price. - **Not done:** I did not decode Seaport sales receipts in the pinned block window, and no RPC endpoint was used. The notes say so and claim no sales. - **Recipe:** it is `panel`, with the CoinGecko URL above as the source. - **Notes:** they record both API attempts and the missing sales cross-check. Since only CoinGecko gave a floor, there is no cross-provider percentage difference to report.
I wrote `artifacts/answer.json` with a floor of 588443000000000000 wei (0.588443 ETH), taken from CoinGecko alone. `check-answer.mjs` prints `ok` for it. - **Floor source:** `https://api.coingecko.com/api/v3/nfts/cryptodickbutts` returned HTTP 200 at 2026-09-21T21:12Z. Its `floor_price.native_currency` is 0.588443 ETH, and the recipe is `panel` with that URL as the source. I did not check a `last_updated` field, so I can't state the source's own timestamp. - **Collection:** CoinGecko lists the contract as `0x42069abfe407c60cf4ae4112bedead391dba1cdb` on Ethereum. It is a dedicated contract, so no token-id filter applies. I took this from CoinGecko's response and did not check it on chain. - **OpenSea:** the stats call returned HTTP 401 (missing API key), so I have no OpenSea floor. I guessed the slug `cryptodickbutts-1` and did not verify it. Without an OpenSea figure there is no cross-provider percentage difference to report. - **Sales cross-check:** not done. I decoded no sales from receipts, and `notes` says so. No block-window check was made, so the pinned range and closing hash appear only in the required window field.
I wrote `artifacts/answer.json` with a floor of 588443000000000000 wei (0.588443 ETH). `check-answer.mjs` prints `ok`. The answer rests on the CoinGecko API alone. - **CoinGecko:** I fetched `https://api.coingecko.com/api/v3/nfts/cryptodickbutts` on 2026-09-21 at 21:12:32 UTC and got HTTP 200. It reports a floor of 0.588443 ETH, and the contract is `0x42069abfe407c60cf4ae4112bedead391dba1cdb` on Ethereum. I did not check whether the response carries a last-updated time, so the notes say the data was fetched fresh. - **OpenSea:** the stats call returned HTTP 401 because no API key was available. The slug I tried, `cryptodickbutts-1`, was a guess I never verified. I did not attempt the OpenSea collection page fallback, so the answer has no OpenSea floor and no percentage comparison. - **Sales cross-check:** I did not decode any Seaport sales in blocks 26021224 to 26028370. The notes state that limitation. CoinGecko reports 3 one-day sales, which matches the "up to 3" count but proves nothing on-chain. - **Recipe:** it is a `panel` recipe with the CoinGecko API URL as its source.
`artifacts/answer.json` is written and validated (`check-answer.mjs` prints `ok`). Summary of the work: - Resolved the correct OpenSea slug (`cryptodickbutts-s3`, contract `0x42069a...a1cdb`) after discovering the naive slug `cryptodickbutts` actually points to an unrelated collection (`CryptoDickbutts OG`). - Both CoinGecko (0.588443 ETH) and OpenSea (0.58837928 ETH) floors agree within 0.011%, well under the 1% threshold — OpenSea's value is reported per the `floorRule` preference, giving **588379280000000000 wei**. - Cross-checked the pinned block window on-chain via public RPC: confirmed the closing block hash, found 7 Transfer logs, filtered out 4 non-sale transfers (a vault deposit/withdraw round-trip), and manually decoded 3 genuine Seaport `OrderFulfilled` sales in one sweep transaction (~0.47 ETH each), whose average exactly matches CoinGecko's reported `one_day_average_sale_price` — confirming data consistency without substituting the sale price for the floor. - OpenSea's sale-events API returned a 401 (no key available), which is documented as an access failure in `notes`.
Created [artifacts/answer.json](/home/imd2/.identitymd/work/817a4689-c97b-4f88-9920-f214d41b9d7e/25c5a24d-4af4-482f-99db-3ff4de14eefb/artifacts/answer.json). Answer: `588443000000000000` wei. Validator result: `ok`.
Completed [artifacts/answer.json](/Users/git/.identitymd/work/817a4689-c97b-4f88-9920-f214d41b9d7e/25c5a24d-4af4-482f-99db-3ff4de14eefb/artifacts/answer.json). Validated successfully with the supplied checker (`ok`).
Completed [artifacts/answer.json](/home/imd/.identitymd/work/817a4689-c97b-4f88-9920-f214d41b9d7e/25c5a24d-4af4-482f-99db-3ff4de14eefb/artifacts/answer.json). It passes the provided verifier (`ok`) and records the selected OpenSea floor, both provider attempts, contract scope, and on-chain sales corroboration.
Created [artifacts/answer.json](/home/worker/.identitymd/work/817a4689-c97b-4f88-9920-f214d41b9d7e/25c5a24d-4af4-482f-99db-3ff4de14eefb/artifacts/answer.json). It validates successfully with the provided checker (`ok`).
Created [artifacts/answer.json](/home/imd/.identitymd/work/817a4689-c97b-4f88-9920-f214d41b9d7e/25c5a24d-4af4-482f-99db-3ff4de14eefb/artifacts/answer.json). Selected floor: `588379280000000000` wei. Validated with the provided checker: `ok`.
Created [artifacts/answer.json](/root/.identitymd/work/817a4689-c97b-4f88-9920-f214d41b9d7e/25c5a24d-4af4-482f-99db-3ff4de14eefb/artifacts/answer.json). Answer: `588379280000000000` wei. Local validator result: `ok`.
Created [artifacts/answer.json](/home/imd3/.identitymd/work/817a4689-c97b-4f88-9920-f214d41b9d7e/25c5a24d-4af4-482f-99db-3ff4de14eefb/artifacts/answer.json). The required validator passes: `ok`.
I wrote `artifacts/answer.json` with a floor of 588443000000000000 wei (0.588443 ETH), and `check-answer.mjs` prints `ok`. It rests on one source, and the onchain sales cross-check was not done. - **Floor source:** CoinGecko `https://api.coingecko.com/api/v3/nfts/cryptodickbutts` returned HTTP 200 at 2026-09-21T20:58Z. It gave `floor_price.native_currency` = 0.588443 with native currency ETH. The response has no `last_updated` field, so I only have my retrieval time. - **Collection scope:** CoinGecko lists it on Ethereum at contract `0x42069abfe407c60cf4ae4112bedead391dba1cdb`. That is a dedicated contract, so no token-id filter applies. - **OpenSea:** the v2 stats endpoint returned 401 (no API key), and the slug I used (`cryptodickbutts-s3`) was a guess. The OpenSea collection page returned HTTP 200, but I did not extract a floor from it. There is no OpenSea floor and no percentage comparison. Under the fallback rule, CoinGecko is the selected source. - **Sales:** I did not decode Seaport events or receipts for the latest 3 sales in blocks 26021224–26028370. `notes` says so and claims no sales evidence. - **Recipe:** `panel`, with source `https://api.coingecko.com/api/v3/nfts/cryptodickbutts`. CoinGecko reports the floor up about 18% over 24 hours, so it could differ from an OpenSea floor.
I wrote `artifacts/answer.json` with a floor of 588443000000000000 wei (0.588443 ETH), and `check-answer.mjs` prints `ok` for it. The sales cross-check and the OpenSea floor are not done, so only one provider backs this number. - **CoinGecko:** `https://api.coingecko.com/api/v3/nfts/cryptodickbutts` returned 200 at 2026-09-21T20:58Z. It confirms the collection as CryptoDickbutts (Series 3) on Ethereum at contract `0x42069abfe407c60cf4ae4112bedead391dba1cdb`. The response carried no `last_updated` field, so freshness rests on the retrieval time. - **OpenSea:** I only tried `https://api.opensea.io/api/v2/collections/cryptodickbutts-s3/stats`, which returned 401 for a missing API key. I had no key, and the slug was a guess I did not verify. I did not try the OpenSea collection page. There is no OpenSea floor and no percentage difference between providers. - **Source and recipe:** Under the request's floor rule, a failed OpenSea check means using the CoinGecko floor. The recipe is `panel`, with the CoinGecko URL above as its source. - **Sales cross-check:** I did not fetch any receipts or decode any Seaport sale events. The notes in the answer say so. CoinGecko reports 3 sales in 24 hours at an average of about 0.47 ETH, but I did not use that as the floor.
I wrote `artifacts/answer.json` with a floor of 588382310000000000 wei (0.58838231 ETH). The answer check prints `ok`. Only the OpenSea floor is confirmed. The CoinGecko check failed, and the onchain sales cross-check was not done. - **OpenSea:** `https://api.opensea.io/api/v2/collections/cryptodickbutts-s3/stats` returned HTTP 200 at 2026-09-21T20:56Z without credentials. Its `total.floor_price` is 0.58838231 ETH. The response has no `last_updated` time, so I could not check freshness against the one-hour limit. - **CoinGecko:** `https://api.coingecko.com/api/v3/nfts/cryptodickbutts` returned HTTP 429, so there is no second floor and no percentage difference to report. - **Collection scope:** The slug `cryptodickbutts-s3` is CryptoDickbutts Series 3, listed as verified on OpenSea. I did not verify the mainnet contract address onchain, so scope rests on OpenSea's metadata. - **Sales:** I did not scan blocks or decode any receipts. OpenSea reports 3 sales in its one-day interval, which I left unverified. `notes` says so. - **Recipe:** It is the `panel` kind with the OpenSea stats URL as its source. The floor is an offchain listing, so it is not reconstructed at the pinned blocks. The answer check first rejected the file because `window` keys must be in the order `toBlock`, `fromBlock`, `toBlockHash`. I reordered them and it now passes.
I wrote `artifacts/answer.json` with a floor of **588382310000000000 wei** (0.58838231 ETH), and `check-answer.mjs` prints `ok`. I did not do the onchain cross-check of the latest sales: no Seaport receipts were fetched or decoded for the pinned window. - **OpenSea:** `https://api.opensea.io/api/v2/collections/cryptodickbutts-s3/stats` returned HTTP 200 without a key. It gave `total.floor_price` 0.58838231 ETH, and that is the value I used. It supplies no `last_updated` time. - **CoinGecko:** `https://api.coingecko.com/api/v3/nfts/cryptodickbutts` returned HTTP 200 with a floor of 0.588443 ETH. It confirms the collection's mainnet contract, `0x42069abfe407c60cf4ae4112bedead391dba1cdb`. The two floors differ by about 0.001%, well under the 1% threshold. - **Sales:** both providers report 3 sales in the last 24 hours, which is consistent with the request but not verified onchain. The notes state this limitation. I retrieved both sources at about 20:55 UTC on 2026-09-21. The recipe is a `panel` recipe citing the OpenSea stats URL. The OpenSea slug `cryptodickbutts-s3` was a guess that worked. The returned stats (2,140 owners) match CoinGecko's unique-address count, but I did not resolve the slug from the contract's collection links.
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.