mirror of
https://github.com/bitcoin/bips.git
synced 2025-12-22 14:45:19 +00:00
BIP-322: fix proof-of-funds inputs wording
This commit is contained in:
parent
6ce21f4eae
commit
80b4b2a6bd
@ -128,7 +128,7 @@ Signers who control an address ''A'' who wish to sign a message ''m'' act as fol
|
|||||||
|
|
||||||
# They construct <code>to_spend</code> and <code>to_sign</code> as specified above, using the scriptPubKey of ''A'' for <code>message_challenge</code> and tagged hash of ''m'' as <code>message_hash</code>.
|
# They construct <code>to_spend</code> and <code>to_sign</code> as specified above, using the scriptPubKey of ''A'' for <code>message_challenge</code> and tagged hash of ''m'' as <code>message_hash</code>.
|
||||||
# Optionally, they may set nLockTime of <code>to_sign</code> or nSequence of its first input.
|
# Optionally, they may set nLockTime of <code>to_sign</code> or nSequence of its first input.
|
||||||
# Optionally, they may add any additional outputs to <code>to_sign</code> that they wish to prove control of.
|
# Optionally, they may add any additional inputs to <code>to_sign</code> that they wish to prove control of.
|
||||||
# They satisfy <code>to_sign</code> as they would any other transaction.
|
# They satisfy <code>to_sign</code> as they would any other transaction.
|
||||||
|
|
||||||
They then encode their signature, choosing either ''simple'' or ''full'' as follows:
|
They then encode their signature, choosing either ''simple'' or ''full'' as follows:
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user