Skip to content

Commit 5ae2238

Browse files
committed
Use SegWit instead of Bitcoin
Fix typo, this is meant to read 'so how do you send a SegWit transaction' ... I think.
1 parent 10d22f6 commit 5ae2238

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

04_6_Creating_a_Segwit_Transaction.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -111,7 +111,7 @@ $ bitcoin-cli listaddressgroupings
111111

112112
## Send a SegWit Transaction The Easy Way
113113

114-
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.)
114+
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.)
115115

116116
Here's an example of sending to a SegWit address, the easy way:
117117
```

0 commit comments

Comments
 (0)