diff options
| author | James Hilliard <james.hilliard1@gmail.com> | 2017-05-23 20:34:50 -0400 |
|---|---|---|
| committer | James Hilliard <james.hilliard1@gmail.com> | 2017-05-23 20:34:50 -0400 |
| commit | 152fd5a62ff31cf7e9caee81428c1371c3020960 (patch) | |
| tree | 911dca019b066f80e35a7464371151b1042062cb /bip-0091.mediawiki | |
| parent | 98bfcee1b44142abf29872948d01f0d7354d7455 (diff) | |
Fix BIP91 typo
Diffstat (limited to 'bip-0091.mediawiki')
| -rw-r--r-- | bip-0091.mediawiki | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/bip-0091.mediawiki b/bip-0091.mediawiki index 2a4d489..bf71882 100644 --- a/bip-0091.mediawiki +++ b/bip-0091.mediawiki @@ -24,7 +24,7 @@ This document specifies a method to activate the existing BIP9 segwit deployment Segwit increases the blocksize, fixes transaction malleability, and makes scripting easier to upgrade as well as bringing many other [https://bitcoincore.org/en/2016/01/26/segwit-benefits/ benefits]. -This BIP provides a way for a simple majority of miners to coordinate activation of the existing segwit deployment with less than 95% hashpower. For a number of reasons a complete redeployment of segwit is difficulty to do until the existing deployment expires. This is due to 0.13.1+ having many segwit related features active already, including all the P2P components, the new network service flag, the witness-tx and block messages, compact blocks v2 and preferential peering. A redeployment of segwit will need to redefine all these things and doing so before expiry would greatly complicate testing. +This BIP provides a way for a simple majority of miners to coordinate activation of the existing segwit deployment with less than 95% hashpower. For a number of reasons a complete redeployment of segwit is difficult to do until the existing deployment expires. This is due to 0.13.1+ having many segwit related features active already, including all the P2P components, the new network service flag, the witness-tx and block messages, compact blocks v2 and preferential peering. A redeployment of segwit will need to redefine all these things and doing so before expiry would greatly complicate testing. ==Specification== |