diff options
| author | MeshCollider <dobsonsa68@gmail.com> | 2017-08-24 23:50:20 +1200 |
|---|---|---|
| committer | Luke Dashjr <luke-jr+git@utopios.org> | 2017-09-16 03:12:13 +0000 |
| commit | 6295c1a095a1fa33f38d334227fa4222d8e0a523 (patch) | |
| tree | f59b8d69f3865b383526ac42ee61cf8d8b3146d2 /bip-0065.mediawiki | |
| parent | b501de4d2cb5fd7d813780cbebfd1be027ba2acd (diff) | |
| download | bips-6295c1a095a1fa33f38d334227fa4222d8e0a523.tar.xz | |
Fixing spelling in multiple BIPs
Diffstat (limited to 'bip-0065.mediawiki')
| -rw-r--r-- | bip-0065.mediawiki | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/bip-0065.mediawiki b/bip-0065.mediawiki index 904dc16..065eb15 100644 --- a/bip-0065.mediawiki +++ b/bip-0065.mediawiki @@ -94,7 +94,7 @@ There exist a number of protocols where a transaction output is created that 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 +need to be created interactively, and additionally, are currently vulnerable to transaction malleability. CHECKLOCKTIMEVERIFY can be used in these protocols, replacing the interactive setup with a non-interactive setup, and additionally, making transaction malleability a non-issue. |