43 KiB
{% comment %} This file is licensed under the MIT License (MIT) available on http://opensource.org/licenses/MIT. {% endcomment %} {% assign filename="_includes/devdoc/example_transactions.md" %}
Transactions
{% include helpers/subhead-links.md %}
Transaction Tutorial
{% include helpers/subhead-links.md %}
{% autocrossref %}
Creating transactions is something most Dash applications do. This section describes how to use Dash Core's RPC interface to create transactions with various attributes.
Your applications may use something besides Dash Core to create transactions, but in any system, you will need to provide the same kinds of data to create transactions with the same attributes as those described below.
In order to use this tutorial, you will need to setup [Dash Core][core executable] and create a regression test mode environment with 500 DASH in your test wallet.
{% endautocrossref %}
Simple Spending
{% include helpers/subhead-links.md %}
{% autocrossref %}
Dash Core provides several RPCs which handle all the details of spending, including creating change outputs and paying appropriate fees. Even advanced users should use these RPCs whenever possible to decrease the chance that duffs will be lost by mistake.
{% highlight bash %}
dash-cli -regtest getnewaddress yLp6ZJueuigiF4s9E1Pv8tEunDPEsjyQfd
NEW_ADDRESS=yLp6ZJueuigiF4s9E1Pv8tEunDPEsjyQfd {% endhighlight %}
Get a new Dash address and save it in the shell variable $NEW_ADDRESS.
{% highlight bash %}
dash-cli -regtest sendtoaddress $NEW_ADDRESS 10.00 c7e5ae1240fdd83bb94c94a93816ed2ab7bcb56ec3ff8a9725c5c1e0482684ea {% endhighlight %}
Send 10 dash to the address using the sendtoaddress RPC. The
returned hex string is the transaction identifier (txid).
The sendtoaddress RPC automatically selects an unspent transaction
output (UTXO) from which to spend the duffs. In this case, it
withdrew the duffs from our only available UTXO, the coinbase
transaction for block #1 which matured with the creation of block #101.
To spend a specific UTXO, you could use the sendfrom RPC instead.
{% highlight bash %}
dash-cli -regtest listunspent [ ] {% endhighlight %}
Use the listunspent RPC to display the UTXOs belonging to this wallet.
The list is empty because it defaults to only showing confirmed
UTXOs and we just spent our only confirmed UTXO.
Re-running the listunspent RPC with the argument "0" to also display
unconfirmed transactions shows that we have two UTXOs, both with the
same txid. The first UTXO shown is a change output that sendtoaddress
created using a new address from the key pool. The second UTXO shown is
the spend to the address we provided. If we had spent those duffs to
someone else, that second transaction would not be displayed in our
list of UTXOs.
{% highlight bash %}
dash-cli -regtest generate 1
unset NEW_ADDRESS {% endhighlight %}
Create a new block to confirm the transaction above (takes less than a second) and clear the shell variable.
{% endautocrossref %}
Simple Spending Script
Shell script to run the previous example:
Simple Raw Transaction
{% include helpers/subhead-links.md %}
{% autocrossref %}
The raw transaction RPCs allow users to create custom transactions and delay broadcasting those transactions. However, mistakes made in raw transactions may not be detected by Dash Core, and a number of raw transaction users have permanently lost large numbers of duffs, so please be careful using raw transactions on mainnet.
This subsection covers one of the simplest possible raw transactions.
{% endhighlight %} {% highlight bash %}
UTXO_TXID=9036265a8f577421e556cd4f729752d73469953deea759de11ef[...] UTXO_VOUT=0 {% endhighlight %}
Re-rerun listunspent. We now have three UTXOs: the two transactions we
created before plus the coinbase transaction from block #2. We save the
txid and output index number (vout) of that coinbase UTXO to shell
variables.
{% highlight bash %}
dash-cli -regtest getnewaddress yfV9Wirf5RkYHgNDttjpBz8Wdi8BavLHcP
NEW_ADDRESS=yfV9Wirf5RkYHgNDttjpBz8Wdi8BavLHcP {% endhighlight %}
Get a new address to use in the raw transaction.
{% highlight bash %}
Outputs - inputs = transaction fee, so always double-check your math!
dash-cli -regtest createrawtransaction ''' [ { "txid": "'$UTXO_TXID'", "vout": '$UTXO_VOUT' } ] ''' ''' { "'$NEW_ADDRESS'": 499.9999 }''' 0100000001a8364935baa9ef11de59a7ee3d956934d75297724fcd56e5217457
8f5a2636900000000000ffffffff01f04c3ba40b0000001976a914d240140859
744755d73e5967081c3bedceffc5db88ac00000000
RAW_TX=0100000001a8364935baa9ef11de59a7ee3d956934d75297724fcd5[...] {% endhighlight %}
Using two arguments to the createrawtransaction RPC, we create a new
raw format transaction. The first argument (a JSON array) references
the txid of the coinbase transaction from block #2 and the index
number (0) of the output from that transaction we want to spend. The
second argument (a JSON object) creates the output with the address
(public key hash) and number of dash we want to transfer.
We save the resulting raw format transaction to a shell variable.
Warning: createrawtransaction does not automatically create change
outputs, so you can easily accidentally pay a large transaction fee. In
this example, our input had 500.0000 dash and our output
($NEW_ADDRESS) is being paid 499.9999 dash, so the transaction will
include a fee of 0.0001 dash. If we had paid $NEW_ADDRESS only 100
dash with no other changes to this transaction, the transaction fee
would be a whopping 400 dash. See the Complex Raw Transaction
subsection below for how to create a transaction with multiple outputs so you
can send the change back to yourself.
Use the decoderawtransaction RPC to see exactly what the transaction
we just created does.
SIGNED_RAW_TX=0100000001a8364935baa9ef11de59a7ee3d956934d75297[...] {% endhighlight %}
Use the signrawtransaction RPC to sign the transaction created by
createrawtransaction and save the returned "hex" raw format signed
transaction to a shell variable.
Even though the transaction is now complete, the Dash Core node we're
connected to doesn't know anything about the transaction, nor does any
other part of the network. We've created a spend, but we haven't
actually spent anything because we could simply unset the
$SIGNED_RAW_TX variable to eliminate the transaction.
{% highlight bash %}
dash-cli -regtest sendrawtransaction $SIGNED_RAW_TX fa0f4105b0a2b2706d65581c5e6411d3970253c7f231944fa2f978b4a3d9010d {% endhighlight %}
Send the signed transaction to the connected node using the
sendrawtransaction RPC. After accepting the transaction, the node
would usually then broadcast it to other peers, but we're not currently
connected to other peers because we started in regtest mode.
{% highlight bash %}
dash-cli -regtest generate 1
unset UTXO_TXID UTXO_VOUT NEW_ADDRESS RAW_TX SIGNED_RAW_TX {% endhighlight %}
Generate a block to confirm the transaction and clear our shell variables.
{% endautocrossref %}
Complex Raw Transaction
{% include helpers/subhead-links.md %}
{% autocrossref %}
In this example, we'll create a transaction with two inputs and two outputs. We'll sign each of the inputs separately, as might happen if the two inputs belonged to different people who agreed to create a transaction together (such as a CoinJoin transaction).
UTXO1_TXID=ea6d596da55a137846f8b08bfd414b4667ce456f9e3b3182e6f05810e8613d84 UTXO1_VOUT=0 UTXO1_ADDRESS=yWtgzKSckhedxtJ8NXhShWGjfBivkvBGgG
UTXO2_TXID=f84ca4ad33ec7889d3c6ac670152137a3ee1603c4096230a10562976f700d130 UTXO2_VOUT=0 UTXO2_ADDRESS=yRdk89fwSW1mUBxQo5fCmEfTva7b4wh2H5 {% endhighlight %}
For our two inputs, we select two UTXOs by placing the txid and output index numbers (vouts) in shell variables. We also save the addresses corresponding to the public keys (hashed or unhashed) used in those transactions. We need the addresses so we can get the corresponding private keys from our wallet.
{% highlight bash %}
dash-cli -regtest dumpprivkey $UTXO1_ADDRESS cNL522MEQUnQxsZJo4ryPH8sPd2uVZaFKjKnZivo9DyVjpAGU7qP
dash-cli -regtest dumpprivkey $UTXO2_ADDRESS cPtZ9nagmjQ5bRKMuqoDz8xni6hRPfZ1zp3TSrqH3j3RyUThTYGN
UTXO1_PRIVATE_KEY=cNL522MEQUnQxsZJo4ryPH8sPd2uVZaFKjKnZivo9DyVjpAGU7qP
UTXO2_PRIVATE_KEY=cPtZ9nagmjQ5bRKMuqoDz8xni6hRPfZ1zp3TSrqH3j3RyUThTYGN {% endhighlight %}
Use the dumpprivkey RPC to get the private keys corresponding to the
public keys used in the two UTXOs out inputs we will be spending. We need
the private keys so we can sign each of the inputs separately.
Warning: Users should never manually manage private keys on mainnet.
As dangerous as raw transactions are (see warnings above), making a
mistake with a private key can be much worse---as in the case of a HD
wallet [cross-generational key compromise][devguide hardened keys].
These examples are to help you learn, not for you to emulate on
mainnet.
{% highlight bash %}
dash-cli -regtest getnewaddress yhshGrdbh3rWt9EPaSi7xSGRFMvFdzTZ8n dash-cli -regtest getnewaddress yesLaP5XFTaLZiWAo2zK8mFfUCtV8rRhKw
NEW_ADDRESS1=yhshGrdbh3rWt9EPaSi7xSGRFMvFdzTZ8n NEW_ADDRESS2=yesLaP5XFTaLZiWAo2zK8mFfUCtV8rRhKw {% endhighlight %}
For our two outputs, get two new addresses.
{% highlight bash %}
Outputs - inputs = transaction fee, so always double-check your math!
dash-cli -regtest createrawtransaction ''' [ { "txid": "'$UTXO1_TXID'", "vout": '$UTXO1_VOUT' }, { "txid": "'$UTXO2_TXID'", "vout": '$UTXO2_VOUT' } ] ''' ''' { "'$NEW_ADDRESS1'": 499.9999, "'$NEW_ADDRESS2'": 10 }''' 0100000002843d61e81058f0e682313b9e6f45ce67464b41fd8bb0f84678135a
a56d596dea0000000000ffffffff30d100f7762956100a2396403c60e13e7a13
520167acc6d38978ec33ada44cf80000000000ffffffff02f04c3ba40b000000
1976a914ec73fe6129b249617bb5f20c8760708055fb6fdb88ac00ca9a3b0000
00001976a914cb7a56b046479f8c247875d672d3e1aed18c33f488ac00000000
RAW_TX=0100000002843d61e81058f0e682313b9e6f45ce67464b41fd8bb0f[...] {% endhighlight %}
Create the raw transaction using createrawtransaction much the same as
before, except now we have two inputs and two outputs.
PARTLY_SIGNED_RAW_TX=0100000002843d61e81058f0e682313b9e6f45ce6[...] {% endhighlight %}
Signing the raw transaction with signrawtransaction gets more
complicated as we now have three arguments:
-
The unsigned raw transaction.
-
An empty array. We don't do anything with this argument in this operation, but some valid JSON must be provided to get access to the later positional arguments.
-
The private key we want to use to sign one of the inputs.
The result is a raw transaction with only one input signed; the fact
that the transaction isn't fully signed is indicated by value of the
complete JSON field. We save the incomplete, partly-signed raw
transaction hex to a shell variable.
To sign the second input, we repeat the process we used to sign the
first input using the second private key. Now that both inputs are
signed, the complete result is true.
{% highlight bash %}
unset PARTLY_SIGNED_RAW_TX RAW_TX NEW_ADDRESS1 [...] {% endhighlight %}
Clean up the shell variables used. Unlike previous subsections, we're
not going to send this transaction to the connected node with
sendrawtransaction. This will allow us to illustrate in the Offline
Signing subsection below how to spend a transaction which is not yet in
the block chain or memory pool.
{% endautocrossref %}
Offline Signing
{% include helpers/subhead-links.md %}
{% autocrossref %}
We will now spend the transaction created in the Complex Raw Transaction subsection above without sending it to the local node first. This is the same basic process used by wallet programs for offline signing---which generally means signing a transaction without access to the current UTXO set.
Offline signing is safe. However, in this example we will also be spending an output which is not part of the block chain because the transaction containing it has never been broadcast. That can be unsafe:
Warning: Transactions which spend outputs from unconfirmed
transactions are vulnerable to transaction malleability. Be sure to read
about transaction malleability and adopt good practices before spending
unconfirmed transactions on mainnet.
{% highlight bash %}
OLD_SIGNED_RAW_TX=0100000002843d61e81058f0e682313b9e6f45ce67464b41fd8bb0
f84678135aa56d596dea00000000494830450221009f7f356c0cc2d3337b5f76dfc6
de9f9be7c8c5ac2074cbeeba4815b90329602002207790f23361480e2a5a2d1fa6e2
93ccd5cd01279ad301176f091b84d6dd8e8f6501ffffffff30d100f7762956100a23
96403c60e13e7a13520167acc6d38978ec33ada44cf8000000006a47304402207867
e88e3fe2c926df29376d77eba81daf9f4a557344d4f02e9c7dcee96a51e402207627
4c2365dc069e7ef797c95c75ab6e01ca3757342f3e6f21a3d9d01086efb7012102ff
9005f79aa4c22ac48fa93d9b7f40f321db1c13cd70cf08bdab3e23c8d19620ffffff
ff02f04c3ba40b0000001976a914ec73fe6129b249617bb5f20c8760708055fb6fdb
88ac00ca9a3b000000001976a914cb7a56b046479f8c247875d672d3e1aed18c33f4
88ac00000000 {% endhighlight %}
Put the previously signed (but not sent) transaction into a shell variable.
UTXO_TXID=5efd61cf24c9644d79646627c4d1e192e9b2a760a5c720db8f4a9f76cb781077 UTXO_VOUT=1 UTXO_OUTPUT_SCRIPT=76a914cb7a56b046479f8c247875d672d3e1aed18c33f488ac {% endhighlight %}
Decode the signed raw transaction so we can get its txid. Also, choose a specific one of its UTXOs to spend and save that UTXO's output index number (vout) and hex pubkey script (scriptPubKey) into shell variables.
{% highlight bash %}
dash-cli -regtest getnewaddress yfijhy7gYY34J2U77xFKdMwfA8k5mVnSRa
NEW_ADDRESS=yfijhy7gYY34J2U77xFKdMwfA8k5mVnSRa {% endhighlight %}
Get a new address to spend the duffs to.
{% highlight bash %}
Outputs - inputs = transaction fee, so always double-check your math!
dash-cli -regtest createrawtransaction ''' [ { "txid": "'$UTXO_TXID'", "vout": '$UTXO_VOUT' } ] ''' ''' { "'$NEW_ADDRESS'": 9.9999 }''' 0100000001771078cb769f4a8fdb20c7a560a7b2e992e1d1c4276664794d64c9
24cf61fd5e0100000000ffffffff01f0a29a3b000000001976a914d4d2078580
a9eea0ca9368d1c99c097279b8081f88ac00000000
RAW_TX=0100000001771078cb769f4a8fdb20c7a560a7b2e992e1d1c427666[...] {% endhighlight %}
Create the raw transaction the same way we've done in the previous subsections.
Attempt to sign the raw transaction without any special arguments, the way we successfully signed the the raw transaction in the Simple Raw Transaction subsection. If you've read the [Transaction section][transaction] of the guide, you may know why the call fails and leaves the raw transaction hex unchanged.
As illustrated above, the data that gets signed includes the txid and
vout from the previous transaction. That information is included in the
createrawtransaction raw transaction. But the data that gets signed
also includes the pubkey script from the previous transaction, even
though it doesn't appear in either the unsigned or signed transaction.
In the other raw transaction subsections above, the previous output was part of the UTXO set known to the wallet, so the wallet was able to use the txid and output index number to find the previous pubkey script and insert it automatically.
In this case, you're spending an output which is unknown to the wallet, so it can't automatically insert the previous pubkey script.
SIGNED_RAW_TX=0100000001771078cb769f4a8fdb20c7a560a7b2e992e1d1[...] {% endhighlight %}
Successfully sign the transaction by providing the previous pubkey script and other required input data.
This specific operation is typically what offline signing wallets do. The online wallet creates the raw transaction and gets the previous pubkey scripts for all the inputs. The user brings this information to the offline wallet. After displaying the transaction details to the user, the offline wallet signs the transaction as we did above. The user takes the signed transaction back to the online wallet, which broadcasts it.
error: {"code":-22,"message":"TX rejected"} {% endhighlight %}
Attempt to broadcast the second transaction before we've broadcast the first transaction. The node rejects this attempt because the second transaction spends an output which is not a UTXO the node knows about.
{% highlight bash %}
dash-cli -regtest sendrawtransaction $OLD_SIGNED_RAW_TX 5efd61cf24c9644d79646627c4d1e192e9b2a760a5c720db8f4a9f76cb781077 dash-cli -regtest sendrawtransaction $SIGNED_RAW_TX f89deefb927fbd03c5acab194de2ba8f98ab160b9c4b3f57bde63073c4b5f060 {% endhighlight %}
Broadcast the first transaction, which succeeds, and then broadcast the second transaction---which also now succeeds because the node now sees the UTXO.
We have once again not generated an additional block, so the transactions above have not yet become part of the regtest block chain. However, they are part of the local node's memory pool.
{% highlight bash %}
unset OLD_SIGNED_RAW_TX SIGNED_RAW_TX RAW_TX [...] {% endhighlight %}
Remove old shell variables.
{% endautocrossref %}
P2SH Multisig
{% include helpers/subhead-links.md %}
{% autocrossref %}
In this subsection, we will create a P2SH multisig address, spend duffs to it, and then spend those duffs from it to another address.
Creating a multisig address is easy. Multisig outputs have two parameters, the minimum number of signatures required (m) and the number of public keys to use to validate those signatures. This is called m-of-n, and in this case we'll be using 2-of-3.
{% highlight bash %} > dash-cli -regtest getnewaddress yYtWtpW7akCc2a5En8NsXeTGENyYbNgv9q > dash-cli -regtest getnewaddress yarm2x9eDFd9dKCycyPigwwj1vfJcYFxsH > dash-cli -regtest getnewaddress yLknHbtnjJRVWQr78aTfCPfNB42jfNkDWK
> NEW_ADDRESS1=yYtWtpW7akCc2a5En8NsXeTGENyYbNgv9q
> NEW_ADDRESS2=yarm2x9eDFd9dKCycyPigwwj1vfJcYFxsH
> NEW_ADDRESS3=yLknHbtnjJRVWQr78aTfCPfNB42jfNkDWK
{% endhighlight %}
Generate three new P2PKH addresses. P2PKH addresses cannot be used with the multisig redeem script created below. (Hashing each public key is unnecessary anyway---all the public keys are protected by a hash when the redeem script is hashed.) However, Dash Core uses addresses as a way to reference the underlying full (unhashed) public keys it knows about, so we get the three new addresses above in order to use their public keys.
Recall from the Guide that the hashed public keys used in addresses obfuscate the full public key, so you cannot give an address to another person or device as part of creating a typical multisig output or P2SH multisig redeem script. You must give them a full public key.
{% endhighlight %} {% highlight bash %}
NEW_ADDRESS3_PUBLIC_KEY=038007ef6fd812d73da054271b68a42dae0667[...] {% endhighlight %}
Use the validateaddress RPC to display the full (unhashed) public key
for one of the addresses. This is the information which will
actually be included in the multisig redeem script. This is also the
information you would give another person or device as part of creating
a multisig output or P2SH multisig redeem script.
We save the address returned to a shell variable.
P2SH_ADDRESS=8meEZF54K7GxhHhdLCCeNwFQjHENv4CK86 P2SH_REDEEM_SCRIPT=522103fa8866cccae3c975a72884443a351801a0ea9[...] {% endhighlight %}
Use the createmultisig RPC with two arguments, the number (n) of
signatures required and a list of addresses or public keys. Because
P2PKH addresses can't be used in the multisig redeem script created by this
RPC, the only addresses which can be provided are those belonging to a
public key in the wallet. In this case, we provide two addresses and
one public key---all of which will be converted to public keys in the
redeem script.
The P2SH address is returned along with the redeem script which must be provided when we spend duffs sent to the P2SH address.
Warning: You must not lose the redeem script, especially if you
don't have a record of which public keys you used to create the P2SH
multisig address. You need the redeem script to spend any dash sent
to the P2SH address. If you lose the redeem script, you can recreate it
by running the same command above, with the public keys listed in the
same order. However, if you lose both the redeem script and even one of
the public keys, you will never be able to spend duffs sent to that
P2SH address.
Neither the address nor the redeem script are stored in the wallet when
you use createmultisig. To store them in the wallet, use the
addmultisigaddress RPC instead. If you add an address to the wallet,
you should also make a new backup.
{% highlight bash %}
dash-cli -regtest sendtoaddress $P2SH_ADDRESS 10.00 ddb2a2eb2402a9ae61d7db93a9a48c0747859d899e704b10f5b72145779f9c52
UTXO_TXID=ddb2a2eb2402a9ae61d7db93a9a48c0747859d899e704b10f5b7[...] {% endhighlight %}
Paying the P2SH multisig address with Dash Core is as simple as paying a more common P2PKH address. Here we use the same command (but different variable) we used in the Simple Spending subsection. As before, this command automatically selects an UTXO, creates a change output to a new one of our P2PKH addresses if necessary, and pays a transaction fee if necessary.
We save that txid to a shell variable as the txid of the UTXO we plan to spend next.
UTXO_VOUT=0 UTXO_OUTPUT_SCRIPT=a9144f334f26e350c8903c92ff25b733670902cfad5a87 {% endhighlight %}
We use the getrawtransaction RPC with the optional second argument
(true) to get the decoded transaction we just created with
sendtoaddress. We choose one of the outputs to be our UTXO and get
its output index number (vout) and pubkey script (scriptPubKey).
{% highlight bash %}
dash-cli -regtest getnewaddress yZSxAakpoWGG3vcsvpk9qNtsYREhump4Cr
NEW_ADDRESS4=yZSxAakpoWGG3vcsvpk9qNtsYREhump4Cr {% endhighlight %}
We generate a new P2PKH address to use in the output we're about to create.
{% highlight bash %}
Outputs - inputs = transaction fee, so always double-check your math!
dash-cli -regtest createrawtransaction ''' [ { "txid": "'$UTXO_TXID'", "vout": '$UTXO_VOUT' } ] ''' ''' { "'$NEW_ADDRESS4'": 9.998 }'''
0100000001529c9f774521b7f5104b709e899d8547078ca4a993dbd761aea902
24eba2b2dd0000000000ffffffff01c0bc973b000000001976a914900504f96c
55d6ebe1c33581ba9430ca05b12a1488ac00000000
010000000175e1769813db8418fea17576694af1ff31cb2b512b7333e6eb42f0
30d0d778720000000000ffffffff01c0bc973b000000001976a914b6f64f5bf3
e38f25ead28817df7929c06fe847ee88ac00000000
RAW_TX=0100000001529c9f774521b7f5104b709e899d8547078ca4a993dbd[...] {% endhighlight %}
We generate the raw transaction the same way we did in the Simple Raw Transaction subsection.
{% highlight bash %}
dash-cli -regtest dumpprivkey $NEW_ADDRESS1 cThhxbQUtBDzHZbZrW6XAR4XkXfaQf4Abo7BQaTK2zVp7sVrHdmv dash-cli -regtest dumpprivkey $NEW_ADDRESS3 cUbYymPeHhRszTn64Xg7dzYKez8YC83M39ZTPJDiBDu8dRD3EjzF
NEW_ADDRESS1_PRIVATE_KEY=cThhxbQUtBDzHZbZrW6XAR4XkXfaQf4Abo7BQ[...] NEW_ADDRESS3_PRIVATE_KEY=cUbYymPeHhRszTn64Xg7dzYKez8YC83M39ZTP[...] {% endhighlight %}
We get the private keys for two of the public keys we used to create the transaction, the same way we got private keys in the Complex Raw Transaction subsection. Recall that we created a 2-of-3 multisig pubkey script, so signatures from two private keys are needed.
Reminder: Users should never manually manage private keys on
mainnet. See the warning in the [complex raw transaction section][devex
complex raw transaction].
PARTLY_SIGNED_RAW_TX=010000000175e1769813db8418fea17576694af1f[...] {% endhighlight %}
We make the first signature. The input argument (JSON object) takes the additional redeem script parameter so that it can append the redeem script to the signature script after the two signatures.
SIGNED_RAW_TX=0100000001529c9f774521b7f5104b709e899d8547078ca4[...] {% endhighlight %}
The signrawtransaction call used here is nearly identical to the one
used above. The only difference is the private key used. Now that the
two required signatures have been provided, the transaction is marked as
complete.
{% highlight bash %}
dash-cli -regtest sendrawtransaction $SIGNED_RAW_TX 483061b32894aacf6c4050291252a480c2a4c869eb85bd45082fb87d6b175ae8 {% endhighlight %}
We send the transaction spending the P2SH multisig output to the local node, which accepts it.
{% endautocrossref %}