mirrors/bitcoin-bips
1
0
Fork 0
mirror of https://github.com/bitcoin/bips.git synced 2025-01-19 05:45:07 +01:00
Code Issues Projects Releases Wiki Activity

Merge pull request #616 from dcousens/patch-1

Browse Source 
BIP174: refactor responsibilities for simplicity and clarity
This commit is contained in:
Luke Dashjr 2017-12-13 01:06:02 +00:00 committed by GitHub
commit 2e1813abdc
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 24 additions and 35 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

59
bip-0174.mediawiki
View File

@ -341,52 +341,41 @@ will still need to handle events where keys are duplicated, either duplicated in
itself or when combining transactions with duplicated fields. If duplicated keys are itself or when combining transactions with duplicated fields. If duplicated keys are
encountered, the software may choose to use any of the values corresponding to that key. encountered, the software may choose to use any of the values corresponding to that key.
==Usage== ==Responsibilities==
Using the transaction format involves many different roles. The roles may be combined Using the transaction format involves many different responsibilities. These responsibilities can be handled by a single entity, but each responsibility is specialized in what it should be capable of doing.
into one entity, but each role has a specific set of things that it must be able to do.
===Transaction Creator=== ===Creator===
The transaction creator must be able to accept either a network serialized transaction or a PSBT The Creator must be capable of accepting either a network serialized transaction, or a PSBT.
and either produce a PSBT or update the provided PSBT. For all scriptSigs which are not finalized, it must make the The Creator can either produce a new PSBT, or update the provided PSBT.
scriptSig empty and fill in the input fields with information from the scriptSig, if any. For any scriptSigs which are non-final, the Creator will provide an empty scriptSig and input fields with information from the scriptSig, if any.
If it is able to, it should also look for any required redeemScripts and witnesScripts If possible, the Creator should also look for any required redeemScripts and witnesScripts and add those to the global data section of the PSBT.
and add those to the global data section of the PSBT. The transaction creator The Creator should also provide any related UTXOs that it knows about.
should also fill in UTXOs that it knows about.
===Transaction Signer=== ===Signer===
The transaction signer must accept a PSBT. It should use the UTXOs provided in the PSBT The Signer must only accept a PSBT.
to produce signatures for the inputs that it can sign for. The signer should not need The Signer must only use the UTXOs provided in the PSBT to produce signatures for inputs.
access to the UTXO set as all necessary information is provided in the PSBT itself. The Signer should not need require any additional data sources, as all necessary information is provided in the PSBT format.
Any and all signatures created should be added as a Partial Signature key-value pair Any signatures created by the Signer must be added as a "Partial Signature" key-value pair for the respective input it relates to.
to the input for which it corresponds to.
The signer should also be able to compute the amount being spent, the amount being The Signer can additionally compute the addresses and values being sent, and the transaction fee, optionally showing this data to the user as a confirmation of intent and the consequences of signing the PSBT.
transacted, the inputs being spent, the transaction fee, and the addresses being
paid. It can be interactive and ask the user for confirmation of all of the above things.
===Transaction Combiner=== ===Combiner===
The transaction combiner must be able to accept multiple PSBTs. It should parse each The Combiner can accept 1 or many PSBTs.
PSBT and merge them into one transaction if possible. If the PSBTs correspond to the The Combiner must merge them into one PSBT (if possible), or fail.
same transaction, then the combiner should create one PSBT which contains all of the The resulting PSBT must contains all of the key-value pairs from each of the PSBTs.
key-value pairs from the PSBTs. It should also handle duplicated keys and remove the The Combined must remove any duplicate key-value pairs, in accordance with the specification.
duplication according to the specification.
===Transaction Finalizer=== ===Finalizer===
The transaction finalizer must take a PSBT and build the finalized scriptSigs for each The Finalizer must only accept a PSBT.
input. If an input contains enough signatures for that input to have a complete set of The Finalizer transforms a PSBT into a network serialized transaction.
signatures, the finalizer should take those signatures, any necessary redeemScripts
and witnessScripts, and build the complete scriptSig. The scriptSig should then be
included in the transaction and the input should have all key-value pairs removed.
The finalizer may remove any global data which is not needed for any other inputs.
===Transaction Broadcaster=== For any inputs which are not complete, the Finalizer will emplace an empty scriptSig in the network serialized transaction.
The transaction broadcaster takes a finalized PSBT. It takes the transaction out of the For any input which has a complete set of signatures, the Finalizer must attempt to build the complete scriptSig and encode it into the network serialized transaction.
PSBT, ensures that the transaction is valid, and broadcasts it to the Bitcoin network.
==Extensibility== ==Extensibility==