> FETCHING JOB RECORD
skill:oracle-assess
Answer this question about chain 1 over blocks 26047886 to 26048184, exactly as .imd/reads/oracle.json pins it: In what year did the Bitcoin value overflow incident occur? 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/bbf46d62-d748-446e-9f94-86f711dc1fb6/38677dde-0db9-4aa1-84be-a80adbee9658/artifacts/answer.json) with answer `2010` and the Bitcoin Wiki panel source. Validation passed: `check-answer.mjs` printed `ok`.
Wrote [artifacts/answer.json](/root/.identitymd/work/bbf46d62-d748-446e-9f94-86f711dc1fb6/38677dde-0db9-4aa1-84be-a80adbee9658/artifacts/answer.json) with the answer **2010**, based on the Bitcoin Wiki incident page. The supplied checker printed `ok`.
Created [artifacts/answer.json](/home/imd/.identitymd/work/bbf46d62-d748-446e-9f94-86f711dc1fb6/38677dde-0db9-4aa1-84be-a80adbee9658/artifacts/answer.json) with answer `2010`. Validated successfully: `check-answer.mjs` prints `ok`.
Completed [artifacts/answer.json](/home/imd-worker/.identitymd/work/bbf46d62-d748-446e-9f94-86f711dc1fb6/38677dde-0db9-4aa1-84be-a80adbee9658/artifacts/answer.json) with answer `2010` and the Bitcoin Wiki panel-source recipe. Validation passed: `check-answer.mjs` printed `ok`.
Wrote [artifacts/answer.json](/home/imd-worker/.identitymd/work/bbf46d62-d748-446e-9f94-86f711dc1fb6/38677dde-0db9-4aa1-84be-a80adbee9658/artifacts/answer.json) with the answer **2010**, based on the [Bitcoin Wiki’s Value overflow incident page](https://en.bitcoin.it/wiki/CVE-2010-5139). The required checker printed `ok`.
Wrote [artifacts/answer.json](/root/.identitymd/work/bbf46d62-d748-446e-9f94-86f711dc1fb6/38677dde-0db9-4aa1-84be-a80adbee9658/artifacts/answer.json) with the answer `2010`, based on the Bitcoin Wiki incident page. The required checker printed `ok`.
I wrote `artifacts/answer.json` with the answer 2010, and `check-answer.mjs` prints `ok` on it. The Bitcoin value overflow incident happened on 15 August 2010 (CVE-2010-5139). I fetched the Bitcoin Wiki page for it, `https://en.bitcoin.it/wiki/Value_overflow_incident`. My check only confirmed that the page mentions 2010. The 15 August date and block 74638 in the notes are from memory, not read off the page. The recipe is `panel` with that URL as the source. The chain window (blocks 26047886–26048184, closing hash) is copied from the brief and only timestamps the request. I did not run any block scan, because the brief calls for the `panel` recipe. The file went through one fix: the window keys had to appear in the brief's order (`toBlock`, then `fromBlock`). I didn't inspect the earlier rejected attempt's files, since the task said none survive. I wrote this one fresh and left it untracked.
I wrote `artifacts/answer.json` with the answer 2010, and `check-answer.mjs` prints `ok` for it. The answer comes from the Bitcoin wiki page "Value overflow incident" (https://en.bitcoin.it/wiki/Value_overflow_incident). I fetched the page and it says the overflow was discovered on August 15, 2010, in block 74638. The recipe is `panel` with that URL as its source. Nothing was computed on Ethereum, since the request's definitions say the chain and window only timestamp the question. The first check failed because the `window` keys were in the wrong order. The checker wants `toBlock`, then `fromBlock`, then `toBlockHash`, and I reordered them to match. I read only this one source, so the panel's agreement is the only cross-check on it. I did not check the closing block hash on an RPC endpoint, because the panel recipe reruns nothing. The file is untracked and not committed.
I wrote `artifacts/answer.json` with the answer 2010, and `check-answer.mjs` prints `ok` for it. The Bitcoin Wiki page "Value overflow incident" says that on August 15, 2010, block 74638 contained an overflowing transaction. I read that line from the page itself, at https://en.bitcoin.it/wiki/Value_overflow_incident. The recipe is the `panel` kind with that URL as its source. No chain data or RPC endpoint was used. The window, request id and closing block hash are copied from `oracle.json`. The first version failed the check because the window keys were in the wrong order, and I fixed that. I did not commit anything.
I wrote `artifacts/answer.json` with the answer 2010, and `check-answer.mjs` prints `ok` for it. The Bitcoin value overflow incident happened on 15 August 2010, when block 74638 created 184,467,440,737.09551616 bitcoins. I read that on the Bitcoin wiki page https://en.bitcoin.it/wiki/Value_overflow_incident, which is also the `source` in the `panel` recipe. - **Window:** the request id, chain and window are copied from `oracle.json`, with the window keys in the same order the brief uses. My first draft had them in a different order, and the checker rejected it until I reordered them. - **No scan:** this is a panel question about Bitcoin's history, so nothing was scanned on chain 1 and no RPC endpoints were used. The pinned window only timestamps the request, as the brief says. - **Untracked output:** I left the file untracked and didn't commit anything.
Check passes with `ok`. Answer written to `artifacts/answer.json`: the Bitcoin value overflow incident occurred in **2010** (CVE-2010-5139, block 74638, 2010-08-15), sourced from the Bitcoin Wiki, using the `panel` recipe kind as required for this off-chain historical fact.
I wrote `artifacts/answer.json` with the answer "2010", and `check-answer.mjs` prints ok. The Bitcoin value overflow incident (CVE-2010-5139) happened on 15 August 2010, at block 74638. That date comes from my recollection of the Bitcoin wiki page "Value overflow incident". I did not open the page in this session. The recipe is the `panel` kind. Its source is `https://en.bitcoin.it/wiki/Value_overflow_incident`. The window and request id are copied from `oracle.json`.
The answer is **2010**. I wrote [artifacts/answer.json](/home/seat14/.identitymd/work/bbf46d62-d748-446e-9f94-86f711dc1fb6/38677dde-0db9-4aa1-84be-a80adbee9658/artifacts/answer.json) with the Bitcoin Wiki source and panel recipe. The supplied checker printed `ok`.
Completed [artifacts/answer.json](/root/.identitymd/work/bbf46d62-d748-446e-9f94-86f711dc1fb6/38677dde-0db9-4aa1-84be-a80adbee9658/artifacts/answer.json). Answer: `2010`. The verifier reports `ok`.
Created [artifacts/answer.json](/home/worker/.identitymd/work/bbf46d62-d748-446e-9f94-86f711dc1fb6/38677dde-0db9-4aa1-84be-a80adbee9658/artifacts/answer.json) with answer `2010`. Validation passed: `check-answer.mjs` printed `ok`.
Created [artifacts/answer.json](/root/.identitymd/work/bbf46d62-d748-446e-9f94-86f711dc1fb6/38677dde-0db9-4aa1-84be-a80adbee9658/artifacts/answer.json) with answer `2010` and a Bitcoin Wiki panel recipe. Validation passed: `check-answer.mjs` printed `ok`.
Completed and validated: - Answer: `2010` - Validator: `ok` - File: [artifacts/answer.json](/home/imd-worker/.identitymd/work/bbf46d62-d748-446e-9f94-86f711dc1fb6/38677dde-0db9-4aa1-84be-a80adbee9658/artifacts/answer.json)
Created [artifacts/answer.json](/root/.identitymd/work/bbf46d62-d748-446e-9f94-86f711dc1fb6/38677dde-0db9-4aa1-84be-a80adbee9658/artifacts/answer.json) with the year **2010**, sourced from the Bitcoin Wiki’s “Value overflow incident” entry. The answer checker printed `ok`.
Wrote [artifacts/answer.json](/home/seat15/.identitymd/work/bbf46d62-d748-446e-9f94-86f711dc1fb6/38677dde-0db9-4aa1-84be-a80adbee9658/artifacts/answer.json) with the answer `2010` and the Bitcoin Wiki panel recipe. The required checker printed `ok`.
Created [artifacts/answer.json](/root/nft2/.identitymd/work/bbf46d62-d748-446e-9f94-86f711dc1fb6/38677dde-0db9-4aa1-84be-a80adbee9658/artifacts/answer.json) with the answer `2010` and the cited Bitcoin Wiki panel recipe. The required checker printed `ok`.
Wrote [artifacts/answer.json](/root/.identitymd/work/bbf46d62-d748-446e-9f94-86f711dc1fb6/38677dde-0db9-4aa1-84be-a80adbee9658/artifacts/answer.json) with answer `2010`, sourced to the Bitcoin Wiki’s reported discovery date. The provided checker printed `ok`.
Check passes. `artifacts/answer.json` is written with the panel-evidence answer: the Bitcoin value overflow incident occurred in **2010** (block 74638, 15 Aug 2010), sourced from the Bitcoin Wiki, with the request id/window copied exactly from `oracle.json`.
That path didn't exist to begin with (empty output confirms it's gone/never existed as a separate tree). The deliverable is at `artifacts/answer.json` in the correct working directory and passes `check-answer.mjs` with `ok`. **Answer: 2010** — the Bitcoin value overflow incident (block 74638, ~184.467 billion BTC created via a signed-integer overflow bug) occurred on August 15, 2010. Answered as a `panel` recipe citing the Bitcoin Wiki's "Value overflow incident" page, since this is a fact about Bitcoin's own history, not something derivable from the pinned Ethereum block window (which only timestamps the request per the brief's `subject` definition).
Check passes. `artifacts/answer.json` is written with the panel recipe answering **2010** — the year of the Bitcoin value overflow incident (CVE-2010-5139, block 74638, 15 August 2010), sourced from the Bitcoin wiki, with window/requestId copied exactly from `oracle.json`.
Created [artifacts/answer.json](/root/.identitymd/work/bbf46d62-d748-446e-9f94-86f711dc1fb6/38677dde-0db9-4aa1-84be-a80adbee9658/artifacts/answer.json) with the answer `2010` and a panel recipe citing the [Bitcoin Wiki’s Value overflow incident page](https://en.bitcoin.it/wiki/CVE-2010-5139). The required checker printed `ok`.
check-answer.mjs prints `ok`. artifacts/answer.json is complete: answer is 2010 (the Bitcoin value overflow incident, block 74638, 2010-08-15), sourced from the Bitcoin Wiki, using the `panel` recipe as required for this off-chain historical question.
Created [artifacts/answer.json](/Users/git/.identitymd/work/bbf46d62-d748-446e-9f94-86f711dc1fb6/38677dde-0db9-4aa1-84be-a80adbee9658/artifacts/answer.json) with the year **2010**. The Bitcoin Wiki says the incident was discovered on August 15, 2010. [Bitcoin Wiki: Value overflow incident](https://en.bitcoin.it/wiki/Value_overflow_incident) The required checker printed `ok`.
bundle upload failed (500)
FAILURE: internal_error
Created [artifacts/answer.json](/home/imd/.identitymd/work/bbf46d62-d748-446e-9f94-86f711dc1fb6/38677dde-0db9-4aa1-84be-a80adbee9658/artifacts/answer.json) with the answer **2010**, based on the [Bitcoin Wiki’s Value overflow incident article](https://en.bitcoin.it/wiki/CVE-2010-5139). The checker printed `ok`.
Created [artifacts/answer.json](/root/.identitymd/work/bbf46d62-d748-446e-9f94-86f711dc1fb6/38677dde-0db9-4aa1-84be-a80adbee9658/artifacts/answer.json) with the answer **2010**. The Bitcoin Wiki dates the incident’s discovery to August 15, 2010. [Source](https://en.bitcoin.it/wiki/CVE-2010-5139) The supplied checker printed `ok`.
`artifacts/answer.json` written and validated — answer is 2010, citing the Bitcoin wiki's "Value overflow incident" page (block 74638, 15 Aug 2010).
Created [artifacts/answer.json](/home/imd1/.identitymd/work/bbf46d62-d748-446e-9f94-86f711dc1fb6/38677dde-0db9-4aa1-84be-a80adbee9658/artifacts/answer.json) with the answer `2010` and the Bitcoin Wiki panel source. The page dates the incident to August 15, 2010. [Bitcoin Wiki: Value overflow incident](https://en.bitcoin.it/wiki/CVE-2010-5139) The pinned request checker printed `ok`.
Created [artifacts/answer.json](/opt/identitymd/worker3/.identitymd/work/bbf46d62-d748-446e-9f94-86f711dc1fb6/38677dde-0db9-4aa1-84be-a80adbee9658/artifacts/answer.json) with answer `2010`, sourced from the [Bitcoin Wiki incident page](https://en.bitcoin.it/wiki/Value_overflow_incident). Validation passed: `check-answer.mjs` printed `ok`.
Created [artifacts/answer.json](/root/.identitymd/work/bbf46d62-d748-446e-9f94-86f711dc1fb6/38677dde-0db9-4aa1-84be-a80adbee9658/artifacts/answer.json) with the answer **2010** and the BitcoinWiki source. The required checker printed `ok`.
Created and validated [artifacts/answer.json](/home/imd-worker/.identitymd/work/bbf46d62-d748-446e-9f94-86f711dc1fb6/38677dde-0db9-4aa1-84be-a80adbee9658/artifacts/answer.json). The checker prints `ok`; answer: `2010`.
check-answer.mjs prints `ok`. Answer: 2010 (Bitcoin value overflow incident, block 74638, source: Bitcoin Wiki), written to artifacts/answer.json as a `panel` recipe.
Created [artifacts/answer.json](/home/levi/imd/p8/work/bbf46d62-d748-446e-9f94-86f711dc1fb6/38677dde-0db9-4aa1-84be-a80adbee9658/artifacts/answer.json) with answer `2010`, based on the [Bitcoin Wiki incident page](https://en.bitcoin.it/wiki/CVE-2010-5139). The required checker printed `ok`.
Check passes. Answer: the Bitcoin value overflow incident occurred in **2010** (block 74638, 2010-08-15), sourced from the Bitcoin Wiki; written to `artifacts/answer.json` as a panel recipe.
Check passes. Answer: 2010, via `panel` recipe citing the Bitcoin Wiki's Value overflow incident page. Written to `artifacts/answer.json`.
Created [artifacts/answer.json](/root/.identitymd/work/bbf46d62-d748-446e-9f94-86f711dc1fb6/38677dde-0db9-4aa1-84be-a80adbee9658/artifacts/answer.json) with the answer **2010** and the Bitcoin Wiki panel source. The required checker printed `ok`.
Created [artifacts/answer.json](/root/.identitymd/work/bbf46d62-d748-446e-9f94-86f711dc1fb6/38677dde-0db9-4aa1-84be-a80adbee9658/artifacts/answer.json) with answer `2010`. Validated successfully: `check-answer.mjs` prints `ok`.
Check passes. `artifacts/answer.json` is written with the panel recipe, answer `2010` (the year of the Bitcoin value overflow incident, CVE-2010-5139), sourced from the Bitcoin Wiki.
Check passes with `ok`. The answer (2010, the year of Bitcoin's value overflow incident) is written to `artifacts/answer.json` as a panel-evidence recipe citing the Bitcoin wiki.
I wrote `artifacts/answer.json` with the answer **2010**, and `check-answer.mjs` prints `ok` for it. The value overflow incident was on 15 August 2010, at block 74638 (CVE-2010-5139). The source is the Bitcoin Wiki page "Value overflow incident", cited as the `panel` recipe's `source`. I fetched that page and only confirmed it mentions 2010. The day, block number and CVE come from my own knowledge, not from the fetched text. No chain data was used, since this is a panel question about Bitcoin history. The pinned window is copied into the file as the brief gives it.
I wrote `artifacts/answer.json` with the answer **2010**. `check-answer.mjs` prints `ok` for it. The Bitcoin wiki page on the value overflow incident says block 74638 contained a transaction that overflowed output values on August 15, 2010. I fetched that page and confirmed the date line, but did not read the rest of it. The question is about Bitcoin's history, so I used the `panel` recipe with that wiki URL as the source and ran no chain scan. The pinned window is only copied in as the timestamp. The first version failed the check because the window's keys were in the wrong order (`toBlock` before `fromBlock`). I reordered them to match `oracle.json`.
The Bitcoin value overflow incident happened in 2010, and I've written that to `artifacts/answer.json` as the uint256 answer `"2010"`. `check-answer.mjs` prints `ok` for it. I fetched the Bitcoin wiki's "Value overflow incident" page, which says that on August 15 2010 block 74638 contained a transaction that overflowed output values. The recipe is `panel` with that page as the source. I ran no chain scan, because the pinned Ethereum window only timestamps the request. The file is untracked.
Check passes: `ok`. Answer written to `artifacts/answer.json` — the Bitcoin value overflow incident occurred in **2010** (block 74638, 2010-08-15), sourced from the Bitcoin Wiki as a panel-evidence answer.
Created [artifacts/answer.json](/Users/dannyren/.identitymd/work/bbf46d62-d748-446e-9f94-86f711dc1fb6/38677dde-0db9-4aa1-84be-a80adbee9658/artifacts/answer.json) with answer `2010`. Validation passed: `check-answer.mjs` printed `ok`.
Answered **2010**, based on the Bitcoin Wiki’s [Value overflow incident page](https://en.bitcoin.it/wiki/CVE-2010-5139). The required checker printed `ok`. [answer.json](/root/.identitymd/work/bbf46d62-d748-446e-9f94-86f711dc1fb6/38677dde-0db9-4aa1-84be-a80adbee9658/artifacts/answer.json)
I wrote `artifacts/answer.json` with the answer 2010, and `check-answer.mjs` prints `ok` for it. The value overflow incident happened on 15 August 2010 (block 74638, CVE-2010-5139). I answered from what I already know, not from a page I read in this run, so I did not fetch the source. The recipe is `panel`, with `https://en.bitcoin.it/wiki/Value_overflow_incident` as the named source, and `notes` says the page was not fetched. No RPC was used; the request's chain and window are copied over unchanged.
The answer is **2010**, and it's written to `artifacts/answer.json`. The answer checker prints `ok`. - **Source:** the Bitcoin wiki page on the incident (https://en.bitcoin.it/wiki/Value_overflow_incident). It says: *"On August 15 2010, it was discovered that block 74638 contained a transaction that created 184,467,440,737.09551616 bitcoins for three different addresses."* - **Recipe:** `{ "kind": "panel", "source": "https://en.bitcoin.it/wiki/Value_overflow_incident" }`. This is a panel question (`"evidence": "panel"`), so it takes only the panel recipe. - **Chain data:** none was read. The brief says the Ethereum block range only timestamps the request, so the request id, chain and window are copied from `.imd/reads/oracle.json` exactly. - **Definitions:** the answer's unit (the four-digit UTC year), the source I read, and the subject are stated under `definitions`. On the first run the checker rejected the window because its keys weren't in the brief's order (`toBlock`, `fromBlock`, `toBlockHash`). I reordered them and it then printed `ok`. The file doesn't appear in `git status`, so it stays uncommitted as the upload expects.
Created [artifacts/answer.json](/home/identitymd3/.identitymd/work/bbf46d62-d748-446e-9f94-86f711dc1fb6/38677dde-0db9-4aa1-84be-a80adbee9658/artifacts/answer.json) with the answer **2010**, citing the Bitcoin Wiki incident page. The checker printed `ok`.
[artifacts/answer.json](/root/.identitymd/work/bbf46d62-d748-446e-9f94-86f711dc1fb6/38677dde-0db9-4aa1-84be-a80adbee9658/artifacts/answer.json) contains the answer, 2010, sourced from the Bitcoin Wiki. The checker printed `ok`.
Wrote [artifacts/answer.json](/home/levi/imd/p6/work/bbf46d62-d748-446e-9f94-86f711dc1fb6/38677dde-0db9-4aa1-84be-a80adbee9658/artifacts/answer.json) with the answer `2010` and a panel recipe citing the Bitcoin Wiki incident page. The required checker printed `ok`.
Check passes. `artifacts/answer.json` is written with answer 2010 (the Bitcoin value overflow incident, CVE-2010-5139, occurred 2010-08-15), using a `panel` recipe citing the Bitcoin Wiki as the source.
Created [artifacts/answer.json](/home/imd1/.identitymd/work/bbf46d62-d748-446e-9f94-86f711dc1fb6/38677dde-0db9-4aa1-84be-a80adbee9658/artifacts/answer.json) with the answer **2010**, sourced to the Bitcoin Wiki’s value overflow incident page. The required checker printed `ok`.
Check passed with `ok`. The answer (2010) is written to `artifacts/answer.json`, sourced from the Bitcoin Wiki's Value Overflow Incident page (block 74638, 15 August 2010), using the `panel` recipe as required for this off-chain historical question.
Created [artifacts/answer.json](/home/imd-worker/.identitymd/work/bbf46d62-d748-446e-9f94-86f711dc1fb6/38677dde-0db9-4aa1-84be-a80adbee9658/artifacts/answer.json) with the answer `2010`, based on the Bitcoin Wiki’s Value overflow incident page. The required checker printed `ok`.
I wrote `artifacts/answer.json` with the answer **2010**, and `check-answer.mjs` prints `ok` for it. It's left untracked, as the instructions require. - **Source:** I read the Bitcoin wiki's "Value overflow incident" page myself (https://en.bitcoin.it/wiki/Value_overflow_incident). It says that on August 15, 2010, block 74638 was found to contain a transaction that created about 184 billion bitcoins. This is tracked as CVE-2010-5139. - **Recipe:** The request pins this as a panel question, so the recipe is `panel` with that URL as its source. I didn't run a chain scan: the request says the Ethereum window only timestamps it and the answer must not come from Ethereum. - **Window:** The request id, chain and window are copied exactly from `oracle.json`. The checker also rejected my first version because the window fields were in a different order, so I changed the order to match.
The Bitcoin value overflow incident happened in 2010, and `artifacts/answer.json` records that. `check-answer.mjs` prints `ok` for the file. I read the Bitcoin Wiki page on the incident, which says it was discovered on August 15, 2010. Block 74638 contained a transaction that created over 184 billion bitcoins. The recipe is a `panel` recipe with that page as its source. This is a panel question about Bitcoin history, so I ran no chain scan. The pinned Ethereum window is copied from the brief and only timestamps the request. I pulled the year out of the page with a quick grep, rather than reading the page in full, so the block number and figures above come from that. The wiki page is the only source I used.
The check passes. I wrote `artifacts/answer.json` answering **2010** — the year of the Bitcoin "value overflow incident" (August 15, 2010, block 74638, where a transaction exploited an integer overflow to create ~184.47 billion BTC, fixed via a same-day soft fork). This is a panel-evidence question, so the recipe is `panel` citing the Bitcoin Wiki article as source; `check-answer.mjs` reports `ok`.
Check passed. Answer: 2010 (Bitcoin's value overflow incident, CVE-2010-5139, block 74638, 2010-08-15), written to `artifacts/answer.json` with a `panel` recipe citing the Bitcoin Wiki.
The Bitcoin value overflow incident occurred in **2010**. I wrote the typed answer and panel source to [artifacts/answer.json](/home/imd/.identitymd/work/bbf46d62-d748-446e-9f94-86f711dc1fb6/38677dde-0db9-4aa1-84be-a80adbee9658/artifacts/answer.json). The answer check printed `ok`.
The Bitcoin value overflow incident happened in 2010, and I've written `artifacts/answer.json` with that answer. `check-answer.mjs` prints `ok` for it. I fetched the Bitcoin Wiki "Value overflow incident" page and it says "August 15 2010, it was discovered that…". I only read that one line of the page with a grep. The rest of the incident description in the file's `notes` (a transaction creating roughly 184 billion BTC, CVE-2010-5139) comes from my own recollection, not the page. Since the brief marks this a panel question, I used the `panel` recipe with that URL as the source and did no chain scan. I copied the pinned request id, chain and window from `.imd/reads/oracle.json`.
I wrote `artifacts/answer.json` with the answer 2010, and `check-answer.mjs` prints `ok` for it. The Bitcoin Wiki's "Value overflow incident" page says that on August 15 2010, block 74638 was found to contain an overflowing output (CVE-2010-5139). I fetched that page with `curl` to confirm the date. The recipe is `panel`, with that page as its `source`. No chain scan was needed, since the question is about Bitcoin history and the pinned window only timestamps the request. The first version failed the check because the window keys were in a different order from `oracle.json`. I reordered them to match.
The answer is 2010. `artifacts/answer.json` is written and `check-answer.mjs` prints `ok`. The Bitcoin Wiki page "Value overflow incident" says block 74638 was found on August 15, 2010. That block contained a transaction that created 184,467,440,737.09551616 bitcoins. The page is categorised under "2010 events" and cites CVE-2010-5139. The recipe is `panel`, with that page as the source. I didn't run any chain scan, since this question is about Bitcoin history and the Ethereum window only timestamps the request.
I wrote `artifacts/answer.json` with the answer `"2010"`. `check-answer.mjs` prints `ok` for it. - **Source:** the Bitcoin wiki page https://en.bitcoin.it/wiki/Value_overflow_incident. I fetched it with curl, and it says that on August 15 2010 block 74638 was found to contain a transaction that overflowed output values. - **Recipe:** `panel` with that URL as its `source`. Nothing was scanned on chain, because the brief has `"evidence": "panel"` and the Ethereum window only timestamps the request. - **Definitions:** the answer is the four-digit UTC calendar year, as the brief defines it. My grep only confirmed the "August 15 2010" text on the page. The block number 74638 in the answer file is from my own knowledge, not from the fetch. I did not consult a second source. The first check failed because I had `fromBlock` and `toBlock` in a different order from `oracle.json`. I swapped them and it passed.
Check passes. `artifacts/answer.json` answers 2010 (the Bitcoin value overflow incident, block 74638, 2010-08-15 UTC) via a `panel` recipe citing the Bitcoin wiki, as required for this off-chain evidence question.
Check passes. `artifacts/answer.json` answers the panel question: the Bitcoin value overflow incident occurred in **2010** (2010-08-15, block 74638), sourced from the Bitcoin Wiki.
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.