From 5ae223897fc3116ae2f4dc5724f7f23e6d80788d Mon Sep 17 00:00:00 2001 From: Tobin Harding Date: Tue, 30 Mar 2021 18:45:33 +1100 Subject: [PATCH] Use SegWit instead of Bitcoin Fix typo, this is meant to read 'so how do you send a SegWit transaction' ... I think. --- 04_6_Creating_a_Segwit_Transaction.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/04_6_Creating_a_Segwit_Transaction.md b/04_6_Creating_a_Segwit_Transaction.md index 943bc64..742347c 100644 --- a/04_6_Creating_a_Segwit_Transaction.md +++ b/04_6_Creating_a_Segwit_Transaction.md @@ -111,7 +111,7 @@ $ bitcoin-cli listaddressgroupings ## Send a SegWit Transaction The Easy Way -So how do you send a Bitcoin transaction? Exactly like any other transaction. It doesn't matter if the UTXO is SegWit, the address is SegWit, or some combination thereof. You can expect `bitcoin-cli` to do the right thing. Though you can tell the differences via the addresses, they don't matter for interacting with things at the `bitcoin-cli` or RPC level. (And this is one of the advantages of using the command line and the RPC interface, as suggested in this tutorial: experts have already done the hard work for you, including things like how to send to both legacy and Bech32 addresses. You just get to use that functionality to your own advantage.) +So how do you send a Segwit transaction? Exactly like any other transaction. It doesn't matter if the UTXO is SegWit, the address is SegWit, or some combination thereof. You can expect `bitcoin-cli` to do the right thing. Though you can tell the differences via the addresses, they don't matter for interacting with things at the `bitcoin-cli` or RPC level. (And this is one of the advantages of using the command line and the RPC interface, as suggested in this tutorial: experts have already done the hard work for you, including things like how to send to both legacy and Bech32 addresses. You just get to use that functionality to your own advantage.) Here's an example of sending to a SegWit address, the easy way: ```