Difference between revisions of "Segregated Witness"

From Bitcoin Wiki
Jump to: navigation, search
(Creating Segregated_Witness)
 
m (See Also: Adding BIP 173)
Line 10: Line 10:
 
* [[BIP_0145|BIP 145]] getblocktemplate Updates for Segregated Witness
 
* [[BIP_0145|BIP 145]] getblocktemplate Updates for Segregated Witness
 
* [[BIP_0147|BIP 147]] Dealing with dummy stack element malleability
 
* [[BIP_0147|BIP 147]] Dealing with dummy stack element malleability
 +
* [[BIP_0173|BIP 173]] Base32 address format for native v0-16 witness outputs
 
* [https://bitcoincore.org/en/2016/01/26/segwit-benefits/ Segregated Witness Benefits]
 
* [https://bitcoincore.org/en/2016/01/26/segwit-benefits/ Segregated Witness Benefits]

Revision as of 17:22, 14 May 2017

Hashbtc.jpgThis page is a stub. Help by expanding it.

Segregated Witness (aka "SegWit") defines a new structure called a "witness" that is committed to blocks separately from the transaction merkle tree. This structure contains data required to check transaction validity but not required to determine transaction effects. In particular, scripts and signatures are moved into this new structure.

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