==== BIP 0091 - Reduced threshold Segwit MASF (soft fork) ====
[[dido:public:ra:xapend:xapend.b_stds:defact:bitcoin:bips| return to the Bitcoin Improvement Proposals ]]
Data sheet for Reduced threshold Segwit MASF
| Title | Reduced threshold Segwit MASF |
| Layer | Consensus (soft fork) |
| Author | James Hilliard |
| Comments-Summary | No comments yet. |
| Comments-URI | [[https://github.com/bitcoin/bips/wiki/Comments:BIP-0091]] |
| Status | Final |
| Type | Standards Track |
| Created | 2017-05-22 |
| Post History | |
| Description | [[https://github.com/bitcoin/bips/blob/master/bip-0091.mediawiki]] |
| License | BSD-3-Clause, CC0-1.0|
: **Note**: The following is an excerpt from the official [[dido:public:ra:xapend:xapend.a_glossary:b:bitcoin|Bitcoin]] site. It is provided here as a convenience and is not authoritative. Refer to the original document(s) as the authoritative reference.
=== Abstract ===
: //This document specifies a method to activate the existing BIP9 segwit deployment with a majority hashpower less than 95%.//
=== Motivation ===
: //Segwit increases the blocksize, fixes transaction malleability, and makes scripting easier to upgrade as well as bringing many other [[dido:public:apdx.stds:defact:bitcoin:start| 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 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.//