diff options
| author | Alexander Cyon <alex.cyon@gmail.com> | 2024-05-28 19:25:46 +0200 |
|---|---|---|
| committer | Alexander Cyon <alex.cyon@gmail.com> | 2024-05-28 19:25:46 +0200 |
| commit | 1eefea0456d661b4c51f3a40b7262d6a99161edd (patch) | |
| tree | 4f84740d22e4220a8c0488e1932d6ee8b3841547 /bip-0137.mediawiki | |
| parent | e2f7481a132e1c5863f5ffcbff009964d7c2af20 (diff) | |
Fix typos on 17 files.
Diffstat (limited to 'bip-0137.mediawiki')
| -rw-r--r-- | bip-0137.mediawiki | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/bip-0137.mediawiki b/bip-0137.mediawiki index 575440b..ccba17f 100644 --- a/bip-0137.mediawiki +++ b/bip-0137.mediawiki @@ -15,7 +15,7 @@ This document describes a signature format for signing messages with Bitcoin private keys. -The specification is intended to describe the standard for signatures of messages that can be signed and verfied between different clients that exist in the field today. Note: that a new signature format has been defined which has a number of advantages over this BIP, but to be backwards compatible with existing implementations this BIP will be useful. See BIP 322 [1] for full details on the new signature scheme. +The specification is intended to describe the standard for signatures of messages that can be signed and verified between different clients that exist in the field today. Note: that a new signature format has been defined which has a number of advantages over this BIP, but to be backwards compatible with existing implementations this BIP will be useful. See BIP 322 [1] for full details on the new signature scheme. One of the key problems in this area is that there are several different types of Bitcoin addresses and without introducing specific standards it is unclear which type of address format is being used. See [2]. This BIP will attempt to address these issues and define a clear and concise format for Bitcoin signatures. |