bitcoin/bips
1
0
Fork 0
mirror of https://github.com/bitcoin/bips.git synced 2026-05-11 16:51:51 +00:00
Code Issues Releases Wiki Activity

BIP-0322: clarify terminology used

Browse Source 
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:
Oli
2026-04-15 14:38:14 +02:00
parent 0a20483c65
commit 8a46a5bfa5
1 changed files with 9 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
bip-0322.mediawiki
View File

@@ -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 funds sent to the invoice address. Proving that a signer sent a prior transaction is not possible
using this BIP. 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 == == Types of Signatures ==
This BIP specifies three formats for signing messages: ''legacy'', ''simple'' and ''full''. This BIP specifies three formats for signing messages: ''legacy'', ''simple'' and ''full''.