diff options
| author | Stacie <staciewaleyko@gmail.com> | 2023-04-10 15:13:32 -0400 |
|---|---|---|
| committer | Stacie <staciewaleyko@gmail.com> | 2023-04-10 15:13:32 -0400 |
| commit | 3ffc3573d9b59d4e52c6c4d4ec8b33e8316c9f97 (patch) | |
| tree | 6fb62de02c275b7c5981a9b1b4128bc7638a04c3 | |
| parent | 156e8aabe24c1253b38d61459791a939550a4b60 (diff) | |
| download | bips-3ffc3573d9b59d4e52c6c4d4ec8b33e8316c9f97.tar.xz | |
BIP-137: Fix typo
| -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 19dd536..43addba 100644 --- a/bip-0137.mediawiki +++ b/bip-0137.mediawiki @@ -25,7 +25,7 @@ This BIP is licensed under the 2-clause BSD license. ==Motivation== -Since Bitcoin private keys can not only be used to sign Bitcoin transactions, but also any other message, it has become customary to use them to sign various messages for differing purposes. Some applications of signing messages with a Bitcoin private key are as follows: proof of funds for collateral, credit worthiness, enterence to events, airdrops, audits as well as other applications. While there was no BIP written for how to digitally sign messages with Bitcoin private keys with P2PKH addresses it is a fairly well understood process, however with the introduction of Segwit (both in the form of P2SH and bech32) addresses, it is unclear how to distinguish a P2PKH, P2SH, or bech32 address from one another. This BIP proposes a standard signature format that will allow clients to distinguish between the different address formats. +Since Bitcoin private keys can not only be used to sign Bitcoin transactions, but also any other message, it has become customary to use them to sign various messages for differing purposes. Some applications of signing messages with a Bitcoin private key are as follows: proof of funds for collateral, credit worthiness, entrance to events, airdrops, audits as well as other applications. While there was no BIP written for how to digitally sign messages with Bitcoin private keys with P2PKH addresses it is a fairly well understood process, however with the introduction of Segwit (both in the form of P2SH and bech32) addresses, it is unclear how to distinguish a P2PKH, P2SH, or bech32 address from one another. This BIP proposes a standard signature format that will allow clients to distinguish between the different address formats. ==Specification== |