From 391b10382be1bcf15703b054104ddd080e1a2d14 Mon Sep 17 00:00:00 2001 From: Felipe Date: Fri, 23 Apr 2021 09:45:48 -0300 Subject: [PATCH] chore: Fix link Fix missing ref in link --- 07_1_Creating_a_Partially_Signed_Bitcoin_Transaction.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/07_1_Creating_a_Partially_Signed_Bitcoin_Transaction.md b/07_1_Creating_a_Partially_Signed_Bitcoin_Transaction.md index c1237ab..6134ff2 100644 --- a/07_1_Creating_a_Partially_Signed_Bitcoin_Transaction.md +++ b/07_1_Creating_a_Partially_Signed_Bitcoin_Transaction.md @@ -12,7 +12,7 @@ Multisignatures were great for the very specific case of jointly holding funds a > :book: ***What is a PSBT?*** As the name suggests, a PSBT is a transaction that has not been fully signed. That's important, because once a transaction is signed, its content is locked in. [BIP174](https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki) defined an abstracted methodology for putting PSBTs together that describes and standardizes roles in their collaborative creation. A *Creator* proposes a transaction; one or more *Updaters* supplement it; and one or more *Signers* authenticate it; before a *Finalizer* completes it; and an *Extracter* turn it into a transaction for the Bitcoin network. There may also be a *Combiner* who merges parallel PSBTs from different users. -PSBTs may initially look sort of the same as multi-sigs because they have a single overlapping bit of functionality: the ability to jointly sign a transaction. However, they were created for a totally different use case. PSBTs recognize the need for multiple programs to jointly create a transaction for a number of different reasons, and they provide a regularized format for doing so. They're especially useful for use cases involving hardware wallets (for which, see §7.3), which are protected from full access to the internet and tend to have minimal transaction history. +PSBTs may initially look sort of the same as multi-sigs because they have a single overlapping bit of functionality: the ability to jointly sign a transaction. However, they were created for a totally different use case. PSBTs recognize the need for multiple programs to jointly create a transaction for a number of different reasons, and they provide a regularized format for doing so. They're especially useful for use cases involving hardware wallets (for which, see [§7.3](https://github.com/BlockchainCommons/Learning-Bitcoin-from-the-Command-Line/blob/master/07_3_Integrating_with_Hardware_Wallets.md)), which are protected from full access to the internet and tend to have minimal transaction history. In general, PSBTs provide a number of functional elements that improve this use case: