Segregated Witness: Difference between revisions
→See Also: link dev guide |
m →History and Activation: Changed the link to archived version because the original was deleted |
||
| (10 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
{{ | {{infobox |title=SegWit|image=<hr style="background-color: #f9f9f9;"/>[[File:Segwit.png|256px]]<hr style="background-color: #f9f9f9;"/> | ||
|fulltitle=Segregated Witness (Consensus layer) | |||
|bipnumber=[[BIP_0141|BIP 141]] | |||
|purpose=Prevent unintended [[transaction malleability]] | |||
|bit=Bit 1 "segwit" | |||
|starttime=2016-11-15 00:00:00 | |||
|timeout=2017-11-15 00:00:00 | |||
|supermajority=95% of last 2016 block period | |||
|lockin=Block #479708<br/>2017-08-08 19:05:58 | |||
|activated=Block #481824<br/>2017-08-24 01:57:37 | |||
}}'''Segregated Witness''' (abbreviated as '''SegWit''') is an implemented protocol upgrade intended to provide protection from [[transaction malleability]] and [[Block size limit controversy|increase block capacity]]. SegWit separates the ''witness'' from the list of inputs. The witness contains data required to check transaction validity but is not required to determine transaction effects. | |||
Additionally, a new ''weight'' parameter is defined, and blocks are allowed to have at most 4 million [[weight units]] (WU). Non-witness and pre-segwit witness bytes weigh 4 WU, but each byte of Segwit witness data only weighs 1 WU, allowing blocks that are larger than 1 MB without a hardforking change. | |||
After the successful activations of OP_CLTV and OP_CSV, SegWit was the last protocol change needed to make the [[Lightning Network]] safe to deploy on the Bitcoin network. | |||
Because the new witness field contains [[Script]] versioning, it is also possible to make changes to or introduce new opcodes to SegWit scripts that would have originally required additional complexity to function without SegWit. | |||
=== History and Activation === | |||
During 2016 and 2017 activation of segregated witness was blocked by miners for political reasons by exploiting a flaw in the [[BIP 9]] activation mechanism. | |||
On a technical level, the consensus rules of bitcoin are controlled by the [[economic majority]] not the [[Bitcoin is not ruled by miners|miners]], so the deadlock was possible to solve by creating a [[user activated soft fork]] [[BIP 148]] where the [[economic majority]] would bypass the blocking miners and activate segregated witness on their own. | |||
This required some coordination amongst the economic majority, but was ultimately successful, activating Segwit on Bitcoin soon after 1st August 2017.<ref>[https://web.archive.org/web/20210224032019/https://bitcoinmagazine.com/articles/long-road-segwit-how-bitcoins-biggest-protocol-upgrade-became-reality// BitcoinMagazine: The Long Road to SegWit: How Bitcoin’s Biggest Protocol Upgrade Became Reality (Archived February 2021)]</ref> | |||
==See Also== | ==See Also== | ||
| Line 13: | Line 32: | ||
* [https://bitcoincore.org/en/2016/01/26/segwit-benefits/ Segregated Witness Benefits] | * [https://bitcoincore.org/en/2016/01/26/segwit-benefits/ Segregated Witness Benefits] | ||
* [https://bitcoincore.org/en/segwit_wallet_dev/ Segregated Witness Wallet Developer Guide] | * [https://bitcoincore.org/en/segwit_wallet_dev/ Segregated Witness Wallet Developer Guide] | ||
* [[Wikipedia:SegWit|Wikipedia: SegWit]] | |||
{{stub}} | |||
Latest revision as of 06:16, 14 March 2021
Segregated Witness (abbreviated as SegWit) is an implemented protocol upgrade intended to provide protection from transaction malleability and increase block capacity. SegWit separates the witness from the list of inputs. The witness contains data required to check transaction validity but is not required to determine transaction effects. Additionally, a new weight parameter is defined, and blocks are allowed to have at most 4 million weight units (WU). Non-witness and pre-segwit witness bytes weigh 4 WU, but each byte of Segwit witness data only weighs 1 WU, allowing blocks that are larger than 1 MB without a hardforking change.
After the successful activations of OP_CLTV and OP_CSV, SegWit was the last protocol change needed to make the Lightning Network safe to deploy on the Bitcoin network.
Because the new witness field contains Script versioning, it is also possible to make changes to or introduce new opcodes to SegWit scripts that would have originally required additional complexity to function without SegWit.
History and Activation
During 2016 and 2017 activation of segregated witness was blocked by miners for political reasons by exploiting a flaw in the BIP 9 activation mechanism. On a technical level, the consensus rules of bitcoin are controlled by the economic majority not the miners, so the deadlock was possible to solve by creating a user activated soft fork BIP 148 where the economic majority would bypass the blocking miners and activate segregated witness on their own. This required some coordination amongst the economic majority, but was ultimately successful, activating Segwit on Bitcoin soon after 1st August 2017.[1]
See Also
- BIP 141 Segregated Witness (Consensus layer)
- BIP 143 Transaction Signature Verification for Version 0 Witness Program
- BIP 144 Segregated Witness (Peer Services)
- BIP 145 getblocktemplate Updates for Segregated Witness
- BIP 147 Dealing with dummy stack element malleability
- BIP 173 Base32 address format for native v0-16 witness outputs
- Segregated Witness Benefits
- Segregated Witness Wallet Developer Guide
- Wikipedia: SegWit
This page is a stub. Help by expanding it.