mirror of
https://github.com/bitcoin/bips.git
synced 2026-05-11 16:51:51 +00:00
BIP-0322: clarify terminology used
Since the term "signature" can be pretty overloaded dependin on the context, we clarify what it actually means in this BIP.
This commit is contained in:
@@ -46,6 +46,15 @@ Finally, this BIP only addresses the use case where a signer shows they will be
|
||||
funds sent to the invoice address. Proving that a signer sent a prior transaction is not possible
|
||||
using this BIP.
|
||||
|
||||
== Terminology ==
|
||||
|
||||
In the context of this BIP, whenever the word "signature" or similar is used, it refers to the
|
||||
output of the signing process described below and, depending on the script type of the
|
||||
<code>message_challenge</code>, is either a full transaction input witness stack, a full
|
||||
transaction, or a PSBT packet that can be validated against a Bitcoin Script Interpreter. Such a
|
||||
"signature" may or may not contain an actual cryptographic (ECDSA or Schnorr) signature, depending
|
||||
on what is required to satisfy the script corresponding to the <code>message_challenge</code>.
|
||||
|
||||
== Types of Signatures ==
|
||||
|
||||
This BIP specifies three formats for signing messages: ''legacy'', ''simple'' and ''full''.
|
||||
|
||||
Reference in New Issue
Block a user