|
|
|
@ -311,8 +311,7 @@ image::images/mbc2_0606.png["Tx_Script_P2PubKeyHash_2"]
|
|
|
|
|
[[multisig]]
|
|
|
|
|
=== Scripted multisignatures
|
|
|
|
|
|
|
|
|
|
((("multisignature
|
|
|
|
|
scripts")))Multisignature scripts set a condition where _k_ public keys
|
|
|
|
|
Multisignature scripts set a condition where _k_ public keys
|
|
|
|
|
are recorded in the script and at least _t_ of those must provide
|
|
|
|
|
signatures to spend the funds, called t-of-k.
|
|
|
|
|
For example, a 2-of-3 multisignature is one
|
|
|
|
@ -676,8 +675,7 @@ spent.
|
|
|
|
|
[[op_return]]
|
|
|
|
|
=== Data Recording Output (OP_RETURN)
|
|
|
|
|
|
|
|
|
|
((("blockchain (the)",
|
|
|
|
|
"nonpayment data recording")))Bitcoin's
|
|
|
|
|
Bitcoin's
|
|
|
|
|
distributed and timestamped blockchain has potential uses
|
|
|
|
|
beyond payments. Many developers have tried to use the transaction
|
|
|
|
|
scripting language to take advantage of the security and resilience of
|
|
|
|
@ -766,8 +764,7 @@ It is important to understand the limitations of transaction lock time. The only
|
|
|
|
|
|
|
|
|
|
==== Check Lock Time Verify (OP_CLTV)
|
|
|
|
|
|
|
|
|
|
((("bitcoin improvement proposals",
|
|
|
|
|
"OP_CHECKLOCKTIMEVERIFY (BIP65)")))In December 2015, a new form of
|
|
|
|
|
In December 2015, a new form of
|
|
|
|
|
timelock was introduced to Bitcoin as a soft fork upgrade. Based on a
|
|
|
|
|
specification in BIP65, a new script operator called
|
|
|
|
|
_OP_CHECKLOCKTIMEVERIFY_ (_CLTV_) was added to the scripting language.
|
|
|
|
|