bitcoin/bips
1
0
Fork 0
mirror of https://github.com/bitcoin/bips.git synced 2025-05-12 12:03:29 +00:00
Code Issues Releases Wiki Activity

Merge pull request #1028 from kallewoof/202010-signmsg2

Browse Source 
BIP-322: minor clarification
This commit is contained in:
Luke Dashjr 2021-02-03 22:04:31 +00:00 committed by GitHub
commit e78a64fc97
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
bip-0322.mediawiki
View File

@ -25,7 +25,7 @@ More importantly, it does not prove ownership nor access to any funds, even if t
== Specification == == Specification ==
This BIP follows the specification of BIP-325 challenges and solutions (see Signet comparison below). This BIP follows the specification of BIP-325 challenges and solutions.
Let there be two virtual transactions to_spend and to_sign. Let there be two virtual transactions to_spend and to_sign.
@ -63,7 +63,7 @@ When a proof of funds is being created, additional inputs should be included for
Proofs of funds are the base64-encoding of the to_spend and to_sign transactions concatenated in standard network serialisation, and proofs without additional inputs or time locks (simple proofs) are the base64-encoding of the to_sign script witness. Proofs of funds are the base64-encoding of the to_spend and to_sign transactions concatenated in standard network serialisation, and proofs without additional inputs or time locks (simple proofs) are the base64-encoding of the to_sign script witness.
A validator must verify it is valid and meets the description of virtual transactions as specified above. See "Validation" below. A validator must verify the proof is valid and meets the description of virtual transactions as specified above. See "Validation" below.
=== Validation === === Validation ===