> FETCHING JOB RECORD
skill:oracle-assess
Answer this question about chain 1 over blocks 26047887 to 26048185, exactly as .imd/reads/oracle.json pins it: In what year did Segregated Witness (SegWit) activate on the Bitcoin mainnet? 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
SegWit activated on the Bitcoin mainnet in **2017**. I wrote that answer to `artifacts/answer.json`, and `check-answer.mjs` prints `ok` for it. - **Source for the activation block:** Bitcoin Core's `chainparams.cpp` sets the mainnet SegWit activation at block 481824 (`consensus.SegwitHeight`). - **Source for the date:** the Blockstream block explorer shows block 481824 with timestamp 1503539857, which is 2017-08-24 01:57 UTC. - **Recipe:** `panel`, with the Blockstream URL for block 481824 as the source. - **Other reading:** the Bitcoin wiki also puts activation shortly after 1 August 2017. BIP141 only gives the window in which miners could signal (15 Nov 2016 to 15 Nov 2017), not the activation block. The answer comes from Bitcoin sources only; I didn't read anything from Ethereum, since the pinned Ethereum blocks only timestamp the request. The checker failed the first draft because the `window` keys weren't in the same order as in `oracle.json`. I reordered them to match and it passed.
Created [artifacts/answer.json](/home/identitymd/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json) with the answer `2017`, based on Bitcoin Core Onboarding’s SegWit activation page. The required checker printed `ok`.
Created [artifacts/answer.json](/home/imd2/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json) with the answer `2017` and the cited Bitcoin block explorer source. The required checker printed `ok`.
Wrote [artifacts/answer.json](/root/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json) with the answer **2017**, based on [Bitcoin Annotated’s SegWit activation entry](https://www.bitcoinannotated.com/entries/segwit-activation/). The required checker printed `ok`.
Created [artifacts/answer.json](/home/identitymd3/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json) with the answer `2017` and its panel source. The required checker printed `ok`.
Wrote [artifacts/answer.json](/home/imd1/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json) with the answer **2017**, based on the [Bitcoin Wiki’s SegWit history](https://en.bitcoin.it/wiki/Segregated_Witness). Both RPC endpoints matched the pinned closing block hash, and the checker printed `ok`.
Created [artifacts/answer.json](/root/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json) with the answer **2017**, citing the Bitcoin Wiki’s SegWit history section. The pinned closing block hash was confirmed, and the required checker printed `ok`.
SegWit activated on the Bitcoin mainnet in **2017**, according to the [Bitcoin Developer Guide](https://developer.bitcoin.org/devguide/transactions.html). I wrote [artifacts/answer.json](/Users/zhuminquan/.identitymd-2/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json) with the pinned request details and a `panel` source recipe. The required checker printed `ok`.
Wrote [artifacts/answer.json](/home/imd-worker/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json) with the answer **2017**, citing the Bitcoin Wiki’s SegWit history section. The required checker printed `ok`.
Created [artifacts/answer.json](/home/imd8/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json) with answer `2017` and the Bitcoin Wiki panel-evidence recipe. Validator result: `ok`.
Created [artifacts/answer.json](/home/imd/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json) with the answer `2017` and the Bitcoin Wiki panel source. The checker printed `ok`.
Created [artifacts/answer.json](/home/identitymd/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json) with the answer **2017** and its Bitcoin Core source recipe. The required checker printed `ok`.
Wrote [artifacts/answer.json](/home/identitymd2/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json) with the answer `2017`. The checker printed `ok`. The source was the [Bitcoin Wiki’s SegWit history section](https://en.bitcoin.it/wiki/Segwit); the pinned brief says its Ethereum window is timestamp context only for this panel question.
Wrote [artifacts/answer.json](/home/seat13/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json) with the answer **2017** and the required panel recipe. The [Bitcoin Developer Guide](https://developer.bitcoin.org/devguide/transactions.html) says SegWit was activated in August 2017. The pinned answer checker printed `ok`.
Created [artifacts/answer.json](/home/imd/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json) with the answer **2017** and the Bitcoin Core Onboarding source. The required checker prints `ok`. The brief classifies this as a panel evidence question and says the pinned Ethereum window only timestamps it, so the recipe records the public source rather than an Ethereum RPC computation.
Created [artifacts/answer.json](/root/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json) with answer `2017`. Validation passed: `check-answer.mjs` printed `ok`.
Created [artifacts/answer.json](/home/imd/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json) with the answer **2017** and the Bitcoin Wiki panel recipe. The required checker printed `ok`.
Created [artifacts/answer.json](/home/imd/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json) with the answer `2017` and the Bitcoin Wiki source. The pinned answer check printed `ok`.
Created [artifacts/answer.json](/home/worker/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json) with the answer `2017` and the Bitcoin Wiki panel source. The checker printed `ok`.
Created [artifacts/answer.json](/home/imd/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json) with the answer **2017** and the Bitcoin Wiki source. The required checker printed `ok`.
Created [artifacts/answer.json](/home/imd/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json) with the answer **2017** and its Bitcoin Wiki source. The required checker printed `ok`.
Wrote [artifacts/answer.json](/home/imd/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json) with the answer **2017**, citing the Bitcoin Magazine report. The required checker printed `ok`.
Check passed (`ok`). `artifacts/answer.json` answers 2017 (Bitcoin mainnet SegWit activation, block 481824, 2017-08-24 UTC) via the `panel` recipe citing the Bitcoin wiki, with the pinned requestId/chain/window copied exactly from the oracle brief.
check-answer.mjs prints `ok`. artifacts/answer.json is written with the panel recipe answering 2017 for SegWit's mainnet activation, sourced from the Bitcoin Wiki.
SegWit activated on Bitcoin mainnet in **2017**. I wrote that to `artifacts/answer.json`, and the answer check prints `ok`. - **Source:** I read the Bitcoin Wiki's Segregated Witness page (https://en.bitcoin.it/wiki/Segregated_Witness). It says SegWit activated "soon after 1st August 2017". It does not give an exact date. - **Not from the source:** The lock-in on 9 August and activation at block 481824 on 24 August 2017 are from my memory. I put that in `notes` and marked it as memory. - **Other sources:** The BIP 141 text and bitcoin.org's SegWit page, both fetched, didn't state an activation date. - **Recipe and window:** The recipe is `panel` with that URL as `source`. The Ethereum window is copied exactly from the brief and only timestamps the request; the answer isn't read from Ethereum. - **Fix during the check:** The check first rejected the `window` object because its keys were in a different order from the brief. I reordered them and it passed.
Done — check-answer.mjs prints `ok`. Answer: SegWit activated in 2017, sourced from the Bitcoin Wiki, written as a `panel` recipe in artifacts/answer.json.
I wrote `artifacts/answer.json` with the answer 2017, and `check-answer.mjs` prints `ok` for it. I did not read a source in this run. SegWit locked in on 9 August 2017 and went live at Bitcoin block 481824 on 24 August 2017, and I gave that from memory. The recipe cites the BIP 141 page as its `source`, but I did not fetch it. The `notes` field says this and that no RPC was used. The request pins an Ethereum window, but the question is about Bitcoin history. The brief says that window only timestamps the request, so no chain scan was needed.
Created [artifacts/answer.json](/home/imd-worker/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json) with the answer **2017** and the Bitcoin Wiki source. The required checker printed `ok`. This is a panel-evidence question, so its recipe cites the off-chain source; the pinned Ethereum window is copied as metadata, not used to derive the answer.
Created [artifacts/answer.json](/root/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json). Validated successfully: `check-answer.mjs` printed `ok`.
Created [artifacts/answer.json](/root/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json) with answer `2017` and a Bitcoin Wiki panel-source recipe. Validation passed: `check-answer.mjs` printed `ok`.
Created [artifacts/answer.json](/root/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json) with answer `2017` and a panel recipe citing Bitcoin activation block 481824. Validation passed: `check-answer.mjs` printed `ok`.
Created [artifacts/answer.json](/home/imd/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json) with answer `2017`. Validation passed: `check-answer.mjs` printed `ok`.
Created [artifacts/answer.json](/home/seat15/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json) with the answer **2017** and the Bitcoin Wiki panel source. The required checker printed `ok`.
Completed [artifacts/answer.json](/home/imd/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json). Validation passed: `check-answer.mjs` printed `ok`. The recorded source is Bitcoin.org’s SegWit vocabulary entry.
Created [artifacts/answer.json](/root/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json) with answer `2017` and the Bitcoin Wiki panel-evidence recipe. Validation passed: `check-answer.mjs` printed `ok`.
Created [artifacts/answer.json](/home/imd/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json) with the answer **2017** and the Bitcoin Wiki source. The required checker printed `ok`. The brief specifies panel evidence for this off-chain fact, so the recipe cites the source rather than deriving the answer from Ethereum RPC data.
Created [artifacts/answer.json](/root/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json) with the answer `2017` and its panel source recipe. The required checker printed `ok`.
Wrote [artifacts/answer.json](/root/nft2/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json) with the answer **2017** and the Bitcoin Wiki panel source. The required checker printed `ok`.
Check passed. `artifacts/answer.json` answers 2017 (SegWit activated on Bitcoin mainnet on 2017-08-24, BIP 141), using the `panel` recipe with BIP 141 as the source, as required for this evidence:"panel" question.
Check passes. `artifacts/answer.json` is written with the panel recipe answering **2017** (SegWit locked in 2017-08-08, activated at Bitcoin block 481824 on 2017-08-24 UTC), sourced from the Bitcoin Wiki and BIP 141, with definitions clarifying this is a Bitcoin-network fact independent of the pinned Ethereum window.
Created [artifacts/answer.json](/home/levi/imd/p8/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json) with the answer **2017**, citing the Bitcoin Wiki. The pinned window is copied exactly, and the required checker printed `ok`.
**2017.** I wrote the typed answer and panel recipe to [artifacts/answer.json](/home/imd/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json). The cited [Bitcoin block explorer](https://www.blockchain.com/explorer/blocks/btc/0000000000000000001c8018d9cb3b742ef25114f27563e3fc4a1902167f9893) dates SegWit’s activation block to August 24, 2017. The supplied checker printed `ok`.
Answer written and validated: SegWit activated in 2017 (BIP141 locked in 2017-08-08, activated at Bitcoin block 481824 on 2017-08-24 UTC). `artifacts/answer.json` passes `check-answer.mjs`.
I wrote `artifacts/answer.json` with the answer 2017, and `check-answer.mjs` prints `ok` for it. - **Answer:** SegWit activated on Bitcoin mainnet in 2017. My recollection is block 481824 on 24 August 2017; the Bitcoin wiki page I fetched (https://en.bitcoin.it/wiki/Segregated_Witness) only says it activated "soon after 1st August 2017". I did not confirm the block number or the exact date against a source. - **Recipe:** it is the `panel` kind, since the brief asks for a fact that lives off chain. The `source` field is that wiki URL. No RPC scan was needed, and none was run. - **Window:** the request id, chain and window are copied from `oracle.json`. The checker first rejected my `window` because the keys were in the wrong order (`toBlock` must come before `fromBlock`). I reordered them and it passed. - **Definitions:** the answer is the four-digit UTC calendar year. The Ethereum window only timestamps the request; it plays no part in the answer.
I wrote `artifacts/answer.json` with the answer 2017, and `check-answer.mjs` prints `ok` for it. SegWit (BIP 141) activated on Bitcoin mainnet at block 481824 in August 2017. This comes from what I remember of the BIP 141 / BIP 9 deployment history. I did not open the cited page or any other source during this run, and I ran no RPC scan. The brief asks for a source you actually read, so treat the "reputable source" requirement as only partly met. The `notes` field in the file says the same. The recipe is the `panel` kind, with the BIP 141 page on GitHub as its source URL. The request id, chain and window are copied from `oracle.json`.
Created [artifacts/answer.json](/home/imd/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json) with the answer `2017`, based on the Bitcoin Wiki’s SegWit activation history. The required checker printed `ok`.
I wrote `artifacts/answer.json` with the answer 2017, and `check-answer.mjs` prints `ok` for it. The recipe is `panel`, since the brief marks this as an off-chain fact. The source I read is the Bitcoin wiki page on Segregated Witness (https://en.bitcoin.it/wiki/Segregated_Witness). It says SegWit activated "soon after 1st August 2017". I did no chain scan, because the question is about Bitcoin history and the pinned Ethereum window only timestamps the request. The exact activation block (481824) comes from my own knowledge, not from the wiki page I fetched. It's in `definitions`, but the wiki page I read only supports the August 2017 date. The checker rejected my first version because the `window` keys were in the wrong order. I reordered them to match `oracle.json`.
SegWit activated on Bitcoin mainnet in **2017**, and I've written that to `artifacts/answer.json`. `check-answer.mjs` prints `ok` for the file. The Bitcoin wiki's Segregated Witness page says segwit activated "soon after 1st August 2017". The exact activation date, block 481824 on 24 August 2017, is from my memory, not the page. I cited the wiki page as the source in the `panel` recipe. I didn't scan any blocks. The pinned Ethereum window only timestamps the request, and the brief says not to read the answer from Ethereum.
I wrote `artifacts/answer.json` with the answer **2017**, and `check-answer.mjs` prints `ok` for it. The recipe is `panel`, with BIP 141 in the bitcoin/bips repository as the source. I fetched that page, and it confirms the BIP's status is "Deployed". It doesn't state the activation date in the text I checked. The 2017 year comes from my own knowledge of Bitcoin history: BIP 9 lock-in on 2017-08-08 and activation at block 481,824 on 2017-08-24. The notes in the file say this. No Ethereum data was used, since this is a panel question and the pinned window only timestamps it.
`artifacts/answer.json` written and validated: answer is 2017, using a `panel` recipe citing the Bitcoin Wiki's SegWit article (activation at block 481824, 2017-08-24 UTC). `check-answer.mjs` prints `ok`.
The answer is **2017**. SegWit activated on Bitcoin mainnet at block 481,824, which was mined on 2017-08-24 at 01:57:37 UTC. It's written to `artifacts/answer.json`, and `check-answer.mjs` prints `ok`. - **Block height:** Bitcoin Core's mainnet settings (`src/kernel/chainparams.cpp`) set the SegWit activation height to 481,824 and give that block's hash. - **Date:** the Blockstream block explorer reports that block at height 481,824 with timestamp 1503539857, which is the date above. - **Cross-check:** BIP141 on GitHub gives a signalling window of 15 Nov 2016 to 15 Nov 2017, which fits. The recipe is the `panel` kind, as this request requires, and its source is the Blockstream URL for that block. I added one definition: "activation" means the first mainnet block that enforces SegWit rules. The Ethereum block range only timestamps the request; I didn't use it to find the answer. The first check failed because I had written the window fields in a different order from `oracle.json`. I reordered them to match exactly and the check then passed. The file is left untracked for the daemon to upload.
I wrote `artifacts/answer.json` with the answer 2017, and `check-answer.mjs` prints `ok` for it. I did not open the cited source during this run. The year comes from what I already know: SegWit (BIP 141) locked in on 9 August 2017 and activated at Bitcoin block 481,824 on 24 August 2017. The `notes` field says this. The `panel` recipe's source is the BIP 141 page on GitHub. No RPC scan was done. The question is about Bitcoin, and the Ethereum window in the brief only timestamps the request. The first version failed the check because the `window` keys were in the wrong order. I reordered them to match `oracle.json` exactly.
I wrote `artifacts/answer.json` with the answer `2017`, and `check-answer.mjs` prints `ok` for it. The recipe is `panel`, with the Bitcoin Wiki's Segregated Witness page as the source. I read that page, and it says SegWit activated "soon after 1st August 2017". No chain scan was needed, since the question is about Bitcoin history and the pinned Ethereum window only timestamps it. The wiki page gives only that approximate date. The exact activation, block 481824 on 24 August 2017, is from my own recollection, not something I read there. The notes in the file say so. Both dates fall in 2017, so the year is not in doubt.
I wrote `artifacts/answer.json` with the answer 2017, and `check-answer.mjs` prints `ok` for it. - **Answer:** 2017 as a uint256 decimal string. SegWit activated at block 481824 on 24 August 2017. The exact block and date come from my own background knowledge, not from a page I read. - **Source read:** the Bitcoin wiki's Segregated Witness page, fetched with curl. It says SegWit activated "soon after 1st August 2017", which supports the year but not the block or the day. - **Recipe:** `panel`, with that wiki URL as the source. This is a panel question, so no chain scan was run. The Ethereum window is only copied into the answer.
Check passes with `ok`. Wrote `artifacts/answer.json`: SegWit activated in **2017**, answered via the `panel` recipe citing the Bitcoin Wiki as source.
I wrote `artifacts/answer.json` with the answer 2017, and `check-answer.mjs` prints `ok` for it. The brief asks for a fact I read from a named source, but I did not fetch one in this run. The answer comes from what I already knew: SegWit (BIP 141) locked in on 9 August 2017 and activated at block 481824 on 24 August 2017. The recipe is `panel`, with the BIP 141 page on GitHub as its `source` URL. The notes in the file say plainly that the source was not fetched and that no RPC was used. The window and request id are copied from `oracle.json`. The first version of the file failed the check because the window keys were in the wrong order, and I fixed that.
I wrote `artifacts/answer.json` with the answer 2017, and `check-answer.mjs` prints `ok` for it. The year comes from my own knowledge of the deployment history, not from a source I read in this run. SegWit (BIP 141) locked in on 9 August 2017 and became active at block 481824 on 24 August 2017. The question is about Bitcoin, so no Ethereum scan was needed. The recipe is a `panel` recipe citing the BIP 141 page on GitHub (`https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki`) as the source. I did not fetch that page. The `notes` field in the file says the answer is from memory and the page was not fetched. The request id, chain and window are copied from `.imd/reads/oracle.json`. The first check failed because I had the window keys in the wrong order, and I fixed that.
I wrote `artifacts/answer.json` with the answer 2017, and `check-answer.mjs` prints `ok` for it. SegWit activated at Bitcoin block 481824 on 24 August 2017. I did not open the source in this run. The answer comes from what I already know of BIP 141 and Bitcoin history, and the `notes` field says so. The recipe is the `panel` kind, since the brief is a panel question. Its `source` is the BIP 141 page on GitHub. No RPC endpoint was used, so the pinned block hash was copied from the brief and not confirmed against a node.
Created [artifacts/answer.json](/home/imd/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json) with the answer `2017` and the cited Bitcoin block explorer source. The required checker printed `ok`.
Answer written to `artifacts/answer.json`: 2017 (SegWit activation year), using a `panel` recipe sourced from the BIPs repo, and it passes `check-answer.mjs`.
I wrote `artifacts/answer.json` with the answer **2017**, and `check-answer.mjs` prints `ok` for it. - **Source read:** the Bitcoin Wiki's Segregated Witness page, which says SegWit activated "soon after 1st August 2017". I also read BIP 141, which sets the deployment window for mainnet. - **Exact date not read:** the block height and date in `definitions` (block 481824, 24 August 2017) come from my own knowledge. Neither page I fetched stated them. - **Recipe:** this is a panel question, so the recipe is `panel` with the wiki URL as its source. - **Window:** the request id, chain and window are copied from `oracle.json`. The pinned Ethereum blocks were not scanned, since the request says they only timestamp the question. The file is untracked, as required.
Done. `artifacts/answer.json` answers 2017 (SegWit activation year) as a panel-evidence recipe citing the Bitcoin Wiki, and `check-answer.mjs` prints `ok`.
Check passes. Wrote `artifacts/answer.json` with answer `2017` (SegWit activated on Bitcoin mainnet at block 481824, 2017-08-24), using the `panel` recipe kind since this is a historical fact question where the pinned chain/window only timestamp the request, per the oracle's own `definitions.subject`.
Created [artifacts/answer.json](/var/lib/imd-worker/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json) with the uint256 answer `2017` and Bitcoin Wiki panel recipe. Verifier result: `ok`.
Created [artifacts/answer.json](/root/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json) with the answer **2017**, citing Blockstream’s activation report. The pinned checker printed `ok`.
Created [artifacts/answer.json](/root/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json) with answer `2017` and the Bitcoin Wiki panel-source recipe. Validation passed: `ok`.
Created [artifacts/answer.json](/home/seat7/.identitymd/work/31a95163-5f64-4a56-b093-32bce81fd1c2/fe6e9ae6-5675-4062-889b-783ed1efff26/artifacts/answer.json) with the answer `2017` and the Bitcoin Wiki source. The required answer check printed `ok`.
Check passes. `artifacts/answer.json` answers 2017 (SegWit activated on Bitcoin mainnet at block 481824, 2017-08-24) using the `panel` recipe with the Bitcoin Wiki as source, per the request's `evidence: panel` designation.
I wrote `artifacts/answer.json` with the answer 2017, and `check-answer.mjs` prints `ok` for it. SegWit locked in on 9 August 2017 and activated at block 481824 on 24 August 2017. I did not fetch any source in this run; the answer comes from what I already knew. The recipe is the `panel` kind, and its `source` is the BIP 141 page on GitHub (`https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki`). The `notes` field in the file says the same. The check first failed because the `window` keys were in a different order from the brief (`toBlock` before `fromBlock`). I reordered them to match.
Check passes. `artifacts/answer.json` answers 2017 (SegWit activation year, BIP 141, locked in 2017-08-08 at block 481824), sourced from the Bitcoin wiki via the `panel` recipe, with the pinned Ethereum window preserved only for timestamping as the definitions require.
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.