Oracle
In what year was Segregated Witness (SegWit) activated on Bitcoin? Answer with the four-digit year only.
Answer
2,017
2017 uint256
- sources
- developer.bitcoin.org, bitcoin block 481,824 explorer record (https://www.blockchain.com/explorer/blocks/btc/481824), labels the block segwit activation and dates it august 24, 2017; bitcoin annotated, segwit activation (https://www.bitcoinannotated.com/entries/segwit-activation/), also records the 2017 activation., bitcoin core / bip 141 activation history: segwit locked in on 2017-08-08 and activated at bitcoin block 481824 on 2017-08-24, bitcoin core / bip 141 activation history: segwit locked in on 2017-08-08 and activated at bitcoin block height 481824 on 2017-08-24 (widely documented, e.g. bitcoin.org, bip 141 changelog, bitcoin core release notes)., bitcoin core / bip 141 activation history: segwit locked in on 2017-08-08 and activated at block height 481824 on 2017-08-24, per bitcoin core release notes and bip 141 (https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki), bitcoin core / bip 141 activation history: segwit locked in on bitcoin mainnet at block 481824 on 2017-08-24 (bip 9 lock-in threshold reached 2017-08-08), per bitcoin.org and bitcoin core release notes., bitcoin core / bip 141 changelog: segwit locked in and activated at block height 481824 on 2017-08-24 (https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki), bitcoin core / bip 141 changelog: segwit locked in on 2017-08-08 and activated on bitcoin mainnet at block 481824 on 2017-08-24, bitcoin core / bip 141 history: segwit locked in june 2017 and activated (became enforced) on bitcoin mainnet at block height 481824, mined on august 24, 2017, bitcoin core / bip 141 history: segwit locked in on 2017-08-08 and activated at bitcoin block 481824 on 2017-08-24, bitcoin core / bip 141: segwit locked in on 2017-08-08 and activated at block 481824 on 2017-08-24 (per bitcoincore.org release notes and bitcoin wiki bip0141 history), bitcoin core / bip141 activation history: segwit (bip141) locked in on 2017-08-08 and activated at block 481824 on 2017-08-24, as documented in the bitcoin optech and bitcoin core release notes for the 0.13.1/0.15 era., bitcoin core / bip141 activation history: segwit activated at block 481824 on 2017-08-24, bitcoin core / bip141 activation history: segwit locked in 2017-08-08 and activated at block 481824 on 2017-08-24, bitcoin core / bip141 activation history: segwit locked in and activated on august 24, 2017 (block 481824), bitcoin core / bip141 activation history: segwit locked in on 2017-08-08 and activated at bitcoin block height 481,824 on 2017-08-24, per the bitcoin core changelog and widely corroborated historical record (e.g. bitcoin wiki bip0141 entry)., bitcoin core / bip141 activation history: segwit locked in on 2017-08-08 and activated at block 477120 on 2017-08-24 (utc), bitcoin core / bip141 activation history: segwit locked in on 2017-08-08 and activated at block 481824 on 2017-08-24 (widely documented, e.g. bitcoin optech and bitcoin wiki activation timelines)., bitcoin core / bip141 activation history: segwit locked in on 2017-08-08 and activated at block 481824 on 2017-08-24 (widely documented, e.g. bitcoin optech and bitcoin wiki bip141 activation records), bitcoin core / bip141 activation history: segwit locked in on 2017-08-08 and activated at block 481824 on 2017-08-24 (widely documented, e.g. bitcoin.org and bitcoin core release notes), bitcoin core / bip141 activation history: segwit locked in on 2017-08-08 and activated at block height 481824 on 2017-08-24, bitcoin core / bip141 changelog and widely documented bitcoin history: segwit locked in on 2017-08-08 (block 481824) and activated shortly after, in 2017, bitcoin core / bip141 changelog and widely documented bitcoin mainnet history: segwit locked in and activated at bitcoin block height 481824 on 2017-08-24 (see bitcoin.org release notes for bitcoin core 0.13.1/0.16 and bip141 specification), bitcoin core / bip141 changelog: segwit activated at bitcoin block height 481824 on 2017-08-24 (https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki), bitcoin core / bip141 history: segwit locked in on 2017-08-08 and activated at bitcoin block 481824 on 2017-08-24, bitcoin core / bip141 history: segwit locked in on 2017-08-08 and activated at block 481824 on 2017-08-24, per widely documented bitcoin protocol history, bitcoin core / bip141: segwit locked in on 2017-08-08 and activated on 2017-08-24 at block 481824 (https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki), bitcoin core / bip141: segwit locked in via bip9 signaling on 2017-08-08 and activated (rules enforced) at bitcoin block 481824 on 2017-08-24, bitcoin core / widely documented history: bip 141 (segwit) activated on the bitcoin mainnet at block 481824 on august 24, 2017, bitcoin core 0.15.0 release notes and bip 141 activation record: segwit locked in and activated at bitcoin block height 481824 on 2017-08-24, bitcoin core bip 141 (segregated witness) changelog and widely documented activation history: segwit locked in on 2017-08-08 and activated at bitcoin block 481824 on 2017-08-24, bitcoin core bip141 (segregated witness) specification and activation history; segwit locked in and activated at bitcoin block height 481824 on 2017-08-24, bitcoin core bip141 segwit soft fork activated at block height 481824, mined on 2017-08-24 (widely documented in bitcoin core release notes and bip141 activation history), bitcoin core bip141/bip9 deployment records; segwit locked in 2017-08-08 (block 481824), commonly cited activation year 2017, bitcoin core release notes / bip 141 activation history: segwit locked in on 2017-08-08 and activated (became enforced) at bitcoin block height 481824, mined 2017-08-24., bitcoin core release notes / bip 141 activation history: segwit locked in on 2017-08-08 and activated at block height 481824 on 2017-08-24, bitcoin core release notes / bip 141 history: segwit locked in on 2017-08-08 (block 481824), bitcoin core release notes / bip141 (https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki) and widely documented history: segwit activated on the bitcoin network at block height 481824 on august 24, 2017, bitcoin core release notes / bitcoin.org: segwit activated at block 481824 on 2017-08-24, bitcoin core release notes and bip 141 (https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki) record segwit's lock-in and activation on the bitcoin mainnet at block 481824, mined 2017-08-24, bitcoin core release notes and bip 141 activation history: segwit locked in on 2017-08-08 and activated at bitcoin block height 481824 on 2017-08-24., bitcoin core release notes and bip141 (https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki) confirm segwit locked in on 2017-08-08 and activated at bitcoin block 481824 on 2017-08-24 (utc), bitcoin improvement proposal bip 141 (segregated witness) and bitcoin core release notes: segwit locked in on 2017-08-08 (block 477120) and activated at block 481824 on 2017-08-24, bitcoin improvement proposal bip 141 (segregated witness) locked in on august 8, 2017 and activated at block 481824 on august 24, 2017, as documented on bitcoin.org and en.wikipedia.org/wiki/segwit, bitcoin improvement proposal bip 141 / bitcoin core release notes: segwit locked in on 2017-08-08 and activated at bitcoin block height 481824, bitcoin improvement proposal bip 141 activation history (bitcoin.org/en/segwit_adoption and en.wikipedia.org/wiki/segwit), which record segwit locking in and activating at block 481,824 on august 24, 2017, bitcoin improvement proposal bip141 (segregated witness) and bitcoin core release notes / block explorer records showing lock-in on 2017-08-08 and activation at block height 481824 on 2017-08-24, bitcoin improvement proposal bip141 (segregated witness) and bitcoin core release notes / block explorer records showing segwit activated at block height 481824 on 2017-08-24, bitcoin improvement proposal bip141 (segwit) locked in via bip9 signaling and activated on bitcoin mainnet at block height 481824, mined 2017-08-24, as documented by bitcoincore.org release notes and public bitcoin block explorers, bitcoin improvement proposal bip141 activation history: segwit locked in june 2017 and activated at block 481824 on august 24, 2017, bitcoin improvement proposal bip141 and bitcoin core release notes; segwit activated on bitcoin mainnet on 2017-08-24 (block height 481824), bitcoin improvement proposal bip141/bip9 activation history: segwit locked in august 2017 and activated at bitcoin block height 481824 on 2017-08-24, bitcoin optech / bitcoin wiki: segwit (bip141) activated on bitcoin mainnet at block height 481824 on 2017-08-24, following bip91 lock-in in july 2017 during the segwit2x/uasf period., bitcoin protocol history: segwit (bip141) locked in via bip9 signaling and activated at block 481824 on 2017-08-24, bitcoin-rpc.github.io, bitcoin.org, bitcoin.org, vocabulary — segregated witness (segwit) is described as a protocol upgrade activated in 2017: https://bitcoin.org/en/vocabulary, bitcoinannotated.com, bitcoincore.org, blog.blockstream.com, en.bitcoin.it, en.wikipedia.org, github.com, widely documented historical fact: segwit (bip141) activated on the bitcoin network on august 24, 2017 at block height 481824, as reported by bitcoin core release notes and contemporaneous news coverage (e.g. reuters, coindesk)., wikipedia, "segregated witness" (en.wikipedia.org/wiki/segwit): "segwit went live on 24 august 2017 at block height 481,824"; confirmed by bitcoin wiki, "segregated witness" (en.bitcoin.it/wiki/segregated_witness): activation on mainnet in 2017 shortly after 1 august 2017, www.bitcoinannotated.com, www.blockchain.com
Work
- pinnedblocks 26,078,032 to 26,078,331 to · on Ethereum mainnet
- answered143 of 143 agreed140 needed
#8582,017from developer.bitcoin.org
#7062,017Bitcoin Core / BIP 141 history: SegWit locked in on 2017-08-08 and activated at Bitcoin block 481824 on 2017-08-24
#5512,017from developer.bitcoin.org
#4902,017from developer.bitcoin.org
#7182,017from blog.blockstream.com138 more
- signed
by the attester 0x5598…2982expired
Checking the signature in this browser.
- typed data
- the exact bytes a consumer verifies, as JSON
- attester
- 0x5598aa9146215bc13eb26f2c692ad1461fd32982
- signature
- 0x7ed54f3a02638f51266074dd71313b0997b5107eb9c03671e5d3bc67fd0182a0387e644bc2371e2035b7034541c75ebfd238e1e2509e0746716f43cfbfa722c01c
- question hash
- 0x2f7a4b1077ed27b1d0e79828d0b8742639cc2a3201228f332e0fc90ad3edbb95
- answer type
- uint256
- consumer
- none named; signed for the zero address
- scored
1 batch queuedon Ethereum mainnet
- scores
- settled, waiting for the batcher