bitcoin/bips
1
0
Fork 0
mirror of https://github.com/bitcoin/bips.git synced 2025-05-12 12:03:29 +00:00
Code Issues Releases Wiki Activity

BIP65 assigned for CHECKLOCKTIMEVERIFY

Browse Source
This commit is contained in:
Peter Todd 2014-11-10 04:43:09 -05:00
parent 5f6cb04d9c
commit b05bc1ef53
No known key found for this signature in database
GPG Key ID: 2481403DA5F091FB
2 changed files with 23 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.mediawiki
View File

@ -236,6 +236,12 @@ Those proposing changes should consider that ultimately consent may rest with th
| Standard | Standard
| Draft | Draft
|- |-
| [[bip-0065.mediawiki|65]]
| OP_CHECKLOCKTIMEVERIFY
| Peter Todd
| Standard
| Draft
|-
| [[bip-0070.mediawiki|70]] | [[bip-0070.mediawiki|70]]
| Payment protocol | Payment protocol
| Gavin Andresen | Gavin Andresen

16
bip-checklocktimeverify.mediawiki → bip-0065.mediawiki
View File

@ -1,5 +1,5 @@
<pre> <pre>
BIP: BIP: 65
Title: OP_CHECKLOCKTIMEVERIFY Title: OP_CHECKLOCKTIMEVERIFY
Author: Peter Todd <pete@petertodd.org> Author: Peter Todd <pete@petertodd.org>
Status: Draft Status: Draft
@ -85,13 +85,13 @@ funds with the following scriptSig:
===Non-interactive time-locked refunds=== ===Non-interactive time-locked refunds===
There exist a number of protocols where a transaction output is created that 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 requires the co-operation of both parties to spend the output. To ensure the
one party does not result in the funds becoming lost refund transactions are failure of one party does not result in the funds becoming lost refund
setup in advance using nLockTime. These refund transactions need to be created transactions are setup in advance using nLockTime. These refund transactions
interactively, and additionaly, are currently vulnerable to transaction need to be created interactively, and additionaly, are currently vulnerable to
mutability. CHECKLOCKTIMEVERIFY can be used in these protocols, replacing the transaction mutability. CHECKLOCKTIMEVERIFY can be used in these protocols,
interactive setup with a non-interactive setup, and additionally, making replacing the interactive setup with a non-interactive setup, and additionally,
transaction mutability a non-issue. making transaction mutability a non-issue.
====Two-factor wallets==== ====Two-factor wallets====