BIP 0148 - Mandatory activation of segwit deployment (soft fork)

return to the Bitcoin Standards

Data sheet for Mandatory activation of segwit deployment

Title	Mandatory activation of segwit deployment
Layer	Consensus (soft fork)
Author	Shaolin Fry
Comments-Summary	No comments yet.
Comments-URI	https://github.com/bitcoin/bips/wiki/Comments:BIP-0148
Staus	Final
Type	Standards Track
Created	2017-03-12
Post History
Description	https://github.com/bitcoin/bips/blob/master/bip-0148.mediawiki
License	BSD-3-Clause, CC0-1.0

Note: The following is an excerpt from the official Bitcoin site. It is provided here as a connivence and is not authoritative. Refer to the original document(s) as the authoritative reference.

Abstract

This document specifies a BIP16 like soft fork flag day activation of the segregated witness BIP9 deployment known as “segwit”1) “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 activating segwit early, before this BIP takes effect. Otherwise this BIP will cause the mandatory activation of the existing segwit deployment before the end of midnight November 15th 2017.