Bitcoin Takeover / BIPs / BIP 116
BIP 116
MERKLEBRANCHVERIFY
Draft Draft Consensus (soft fork) Specification Assigned 2017-08-25
From the BIP’s abstract
A general approach to bitcoin contracts is to fully enumerate the possible spending conditions and then program verification of these conditions into a single script. At redemption, the spending condition used is explicitly selected, e.g. by pushing a value on the witness stack that cascades through a series of if/else constructs. This approach has significant downsides, such as requiring all program pathways to be visible in the scriptPubKey or redeem script, even those which are not used at validation. This wastes space on the block chain, restricts the size of possible scripts due to push limits, and impacts both privacy and fungibility as details of the contract can often be specific to…
Read BIP 116 on GitHubFind in explorer