mirror of
https://github.com/bitcoin/bips.git
synced 2025-05-12 12:03:29 +00:00
BIP65 assigned for CHECKLOCKTIMEVERIFY
This commit is contained in:
parent
5f6cb04d9c
commit
b05bc1ef53
@ -236,6 +236,12 @@ Those proposing changes should consider that ultimately consent may rest with th
|
||||
| Standard
|
||||
| Draft
|
||||
|-
|
||||
| [[bip-0065.mediawiki|65]]
|
||||
| OP_CHECKLOCKTIMEVERIFY
|
||||
| Peter Todd
|
||||
| Standard
|
||||
| Draft
|
||||
|-
|
||||
| [[bip-0070.mediawiki|70]]
|
||||
| Payment protocol
|
||||
| Gavin Andresen
|
||||
|
@ -1,5 +1,5 @@
|
||||
<pre>
|
||||
BIP:
|
||||
BIP: 65
|
||||
Title: OP_CHECKLOCKTIMEVERIFY
|
||||
Author: Peter Todd <pete@petertodd.org>
|
||||
Status: Draft
|
||||
@ -85,13 +85,13 @@ funds with the following scriptSig:
|
||||
===Non-interactive time-locked refunds===
|
||||
|
||||
There exist a number of protocols where a transaction output is created that
|
||||
the co-operation of both parties to spend the output. To ensure the failure of
|
||||
one party does not result in the funds becoming lost refund transactions are
|
||||
setup in advance using nLockTime. These refund transactions need to be created
|
||||
interactively, and additionaly, are currently vulnerable to transaction
|
||||
mutability. CHECKLOCKTIMEVERIFY can be used in these protocols, replacing the
|
||||
interactive setup with a non-interactive setup, and additionally, making
|
||||
transaction mutability a non-issue.
|
||||
requires the co-operation of both parties to spend the output. To ensure the
|
||||
failure of one party does not result in the funds becoming lost refund
|
||||
transactions are setup in advance using nLockTime. These refund transactions
|
||||
need to be created interactively, and additionaly, are currently vulnerable to
|
||||
transaction mutability. CHECKLOCKTIMEVERIFY can be used in these protocols,
|
||||
replacing the interactive setup with a non-interactive setup, and additionally,
|
||||
making transaction mutability a non-issue.
|
||||
|
||||
|
||||
====Two-factor wallets====
|
Loading…
x
Reference in New Issue
Block a user