mirror of
https://github.com/bitcoinbook/bitcoinbook
synced 2024-12-23 23:18:42 +00:00
Edited ch07_authorization-authentication.adoc with Atlas code editor
This commit is contained in:
parent
3a25a2d7da
commit
9aea2edc75
@ -754,7 +754,7 @@ transaction((("scripts", "OP_RETURN", startref="script-op-return")))((("OP_RETUR
|
||||
[[lock_time_limitations]]
|
||||
==== Transaction Lock Time Limitations
|
||||
|
||||
Use of the ((("transactions", "timelocks", "limitations of")))((("timelocks", "limitations of")))((("lock time", "limitations of")))lock time allows a spender to restrict a transaction from
|
||||
Use of the ((("transactions", "timelocks", "limitations of")))((("timelocks", "limitations of")))((("lock time", "limitations of")))((("scripts", "timelocks", "limitations of")))lock time allows a spender to restrict a transaction from
|
||||
being included in a block until a specific block height, but it does not
|
||||
prevent spending the funds in another transaction earlier than that.
|
||||
Let's explain that with the following example.
|
||||
@ -773,7 +773,7 @@ It is important to understand the limitations of transaction lock time. The only
|
||||
|
||||
==== Check Lock Time Verify (OP_CLTV)
|
||||
|
||||
In ((("transactions", "timelocks", "verifying", id="transaction-timelock-op-cltv")))((("timelocks", "verifying", id="timelock-op-cltv")))((("lock time", "verifying", id="lock-time-op-cltv")))((("OP_CLTV script operator", id="op-cltv")))((("verifying", "lock time", id="verify-lock-time")))December 2015, a new form of
|
||||
In ((("transactions", "timelocks", "verifying", id="transaction-timelock-op-cltv")))((("timelocks", "verifying", id="timelock-op-cltv")))((("lock time", "verifying", id="lock-time-op-cltv")))((("OP_CLTV script operator", id="op-cltv")))((("verifying", "lock time", id="verify-lock-time")))((("scripts", "timelocks", "verifying", id="script-timelock-verify")))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.
|
||||
@ -880,7 +880,7 @@ By introducing timelock functionality directly into the scripting
|
||||
language, +OP_CLTV+ allows us to develop some very interesting complex
|
||||
scripts.
|
||||
|
||||
The standard((("transactions", "timelocks", "verifying", startref="transaction-timelock-op-cltv")))((("timelocks", "verifying", startref="timelock-op-cltv")))((("lock time", "verifying", startref="lock-time-op-cltv")))((("OP_CLTV script operator", startref="op-cltv")))((("verifying", "lock time", startref="verify-lock-time"))) is defined in
|
||||
The standard((("transactions", "timelocks", "verifying", startref="transaction-timelock-op-cltv")))((("timelocks", "verifying", startref="timelock-op-cltv")))((("lock time", "verifying", startref="lock-time-op-cltv")))((("OP_CLTV script operator", startref="op-cltv")))((("verifying", "lock time", startref="verify-lock-time")))((("scripts", "timelocks", "verifying", startref="script-timelock-verify"))) is defined in
|
||||
https://oreil.ly/YmJGD[BIP65
|
||||
(OP_CHECKLOCKTIMEVERIFY)].
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user