diff options
| author | Ryan Shea <ryan@shea.io> | 2014-11-12 09:15:29 -0500 |
|---|---|---|
| committer | Ryan Shea <ryan@shea.io> | 2014-11-12 09:15:29 -0500 |
| commit | 481f288f9e8891c58230bb6f8cd9bae71dc3bf19 (patch) | |
| tree | 0bf46497f5371e7f458749996a6970a4c96606a6 | |
| parent | a3715c2de5a3df3b94c3335e6ea6924a566d9d58 (diff) | |
Fix a few minor typos in bip 0065
| -rw-r--r-- | bip-0065.mediawiki | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/bip-0065.mediawiki b/bip-0065.mediawiki index 9574374..fb22ace 100644 --- a/bip-0065.mediawiki +++ b/bip-0065.mediawiki @@ -16,9 +16,9 @@ some point in the future. ==Summary== -CHECKLOCKTIMEVERIFY re-defines the existing NOP2 opcode. When executed it +CHECKLOCKTIMEVERIFY redefines the existing NOP2 opcode. When executed it compares the top item on the stack to the nLockTime field of the transaction -containing the scriptSig. If that top stack item is greater than the transation +containing the scriptSig. If that top stack item is greater than the transaction nLockTime the script fails immediately, otherwise script evaluation continues as though a NOP was executed. @@ -41,8 +41,8 @@ nLockTime field proves that should the receiver vanish the sender is guaranteed to get all their escrowed funds back when the nLockTime is reached. However the nLockTime field is insufficient if you wish to prove that -transaction output ''can-not'' be spent until some time in the future, as there -is no way to prove that the secret keys corresponding to the pubkeys controling +transaction output ''cannot'' be spent until some time in the future, as there +is no way to prove that the secret keys corresponding to the pubkeys controlling the funds have not been used to create a valid signature. |