149 - Segregated Witness (second deployment)
BIP: 149 source Layer: Consensus (soft fork) Title: Segregated Witness (second deployment) Author: Shaolin Fry Comments-Summary: No comments yet. Comments-URI: https://github.com/bitcoin/bips/wiki/Comments:BIP-0149 Status: Withdrawn Type: Standards Track Created: 2017-04-14 License: BSD-3-Clause CC0-1.0 Table of ContentsAbstractMotivationReference implementationSpecificationDeploymentBackwards CompatibilityRationaleReferencesCopyright Abstract This document specifies a user activated soft fork for BIP141, BIP143 and BIP147 using versionbits with guaranteed lock-in. Motivation Miners have been reluctant to signal the BIP9 segwit deployment despite a large portion of the Bitcoin ecosystem who want the soft fork activated. This BIP specifies a user activated soft fork (UASF) that deploys segwit again using versionbits with guaranteed lock-in on timeout if the BIP is not already locked-in or activated by the timeout. This ensures users have sufficient time t...
148 - Mandatory activation of segwit deployment
BIP: 148 source Layer: Consensus (soft fork) Title: Mandatory activation of segwit deployment Author: Shaolin Fry Comments-Summary: No comments yet. Comments-URI: https://github.com/bitcoin/bips/wiki/Comments:BIP-0148 Status: Final Type: Standards Track Created: 2017-03-12 License: BSD-3-Clause CC0-1.0 Table of ContentsAbstractDefinitionsMotivationSpecificationReference implementationBackwards CompatibilityRationaleReferencesCopyright Abstract This document specifies a BIP16 like soft fork flag day activation of the segregated witness BIP9 deployment known as "segwit". Definitions "existing segwit deployment" refer to the BIP9 "segwit" deployment using bit 1, between November 15th 2016 and November 15th 2017 to activate BIP141, BIP143 and BIP147. Motivation Segwit increases the blocksize, fixes transaction malleability, and makes scripting easier to upgrade as well as bringing many other benefits. It is hoped that miners will respond to this BIP by activ...
8 - Version bits with lock-in by height
BIP: 8 source Title: Version bits with lock-in by height Author: Shaolin Fry Luke Dashjr Comments-Summary: No comments yet. Comments-URI: https://github.com/bitcoin/bips/wiki/Comments:BIP-0008 Status: Draft Type: Informational Created: 2017-02-01 License: BSD-3-Clause CC0-1.0 Table of ContentsAbstractMotivationSpecificationParametersSelection guidelinesStatesBit flagsNew consensus rulesState transitionsMandatory signallingWarning mechanismgetblocktemplate changesReference implementationContrasted with BIP 9Backwards compatibilityDeploymentsReferencesCopyright Abstract This document specifies an alternative to BIP9 that corrects for a number of perceived mistakes. Block heights are used for start and timeout rather than POSIX timestamps. It additionally introduces an activation parameter that can guarantee activation of backward-compatible changes (further called "soft forks"). The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SH...
343 - Mandatory activation of taproot deployment
BIP: 343 source Layer: Consensus (soft fork) Title: Mandatory activation of taproot deployment Author: Shinobius Michael Folkson Comments-Summary: No comments yet. Comments-URI: https://github.com/bitcoin/bips/wiki/Comments:BIP-0343 Status: Final Type: Standards Track Created: 2021-04-25 License: BSD-3-Clause CC0-1.0 Table of ContentsAbstractMotivationSpecificationReference implementationBackward CompatibilityCompatibility with later alternative activationsRationaleAcknowledgementsReferencesCopyright Abstract This document specifies a BIP8 (LOT=true) deployment to activate taproot. Motivation The Taproot soft fork upgrade has been assessed to have overwhelming community consensus and hence should attempt to be activated. Lessons have been learned from the BIP148 and BIP91 deployments in 2017 with regards to giving many months of advance warning before the mandatory signaling is attempted. The mandatory signaling is only required if miners have...