diff --git a/_includes/example_transactions.md b/_includes/example_transactions.md
new file mode 100644
index 00000000..55117ecd
--- /dev/null
+++ b/_includes/example_transactions.md
@@ -0,0 +1,1258 @@
+## Transactions
+
+### Transaction Tutorial
+
+{% autocrossref %}
+
+Creating transactions is something most Bitcoin applications do.
+This section describes how to use Bitcoin Core's RPC interface to
+create transactions with various attributes.
+
+Your applications may use something besides Bitcoin 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.
+
+You are encouraged to try the following examples on your own using the
+regtest mode described below.
+
+Note: as in other parts of the documentation, we wrap long strings with
+"\\" and indicate omissions with "[...]".
+
+{% endautocrossref %}
+
+#### Regtest Mode
+
+{% autocrossref %}
+
+Bitcoin's testnet provides an excellent way to test Bitcoin
+functionality without risking real satoshis. However, for situations
+where interaction with random peers and blocks is unnecessary or
+unwanted, Bitcoin Core's regression test (regtest) mode lets you
+instantly create a brand-new private block chain with the same basic
+rules as testnet---but one major difference: you choose when to create
+new blocks, so you have complete control over the environment.
+
+Many developers consider regtest mode the preferred way to develop new
+applications, and this tutorial will use it exclusively.
+
+{% highlight bash %}
+> bitcoind -regtest -daemon
+Bitcoin server starting
+{% endhighlight %}
+
+Start `bitcoind` in regtest mode to create a private block chain.
+
+{% highlight bash %}
+> bitcoin-cli -regtest getbalance
+0.00000000
+{% endhighlight %}
+
+Check our starting balance with the `getbalance` RPC. Regtest wallets
+and block chain state (chainstate) are saved in the `regtest`
+subdirectory of the Bitcoin Core configuration directory. You can safely
+delete the `regtest` subdirectory and restart Bitcoin Core to start a
+new regtest. (See the [Guide Introduction][devguide] for default configuration
+directory locations on various operating systems. Always back up mainnet
+wallets before performing dangerous operations such as deleting.)
+
+~~~
+bitcoin-cli -regtest setgenerate true 101
+~~~
+
+Generate 101 blocks using a special version of the `setgenerate` RPC
+which is only available in regtest mode. This takes about 30 seconds on
+a generic PC. Because this is a new block chain using Bitcoin's default
+rules, the first 210,000 blocks pay a block reward of 50 bitcoins.
+However, a block must have 100 confirmations before that reward can be
+spent, so we generate 101 blocks to get access to the coinbase
+transaction from block #1.
+
+{% highlight bash %}
+bitcoin-cli -regtest getbalance
+50.00000000
+{% endhighlight %}
+
+Verify that we now have 50 bitcoins available to spend.
+
+{% endautocrossref %}
+
+
+
+
+
+
+#### Simple Spending
+
+{% autocrossref %}
+
+Bitcoin 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 satoshis will be lost to mistakes.
+
+{% highlight bash %}
+> bitcoin-cli -regtest getnewaddress
+mvbnrCX3bg1cDRUu8pkecrvP6vQkSLDSou
+
+> NEW_ADDRESS=mvbnrCX3bg1cDRUu8pkecrvP6vQkSLDSou
+{% endhighlight %}
+
+Get a new Bitcoin address and save it in the shell variable `$NEW_ADDRESS`.
+
+{% highlight bash %}
+> bitcoin-cli -regtest sendtoaddress $NEW_ADDRESS 10.00
+263c018582731ff54dc72c7d67e858c002ae298835501d80200f05753de0edf0
+{% endhighlight %}
+
+Send 10 bitcoins 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 satoshis. In this case, it
+withdrew the satoshis 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 %}
+> bitcoin-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.
+
+
+{% highlight bash %}
+> bitcoin-cli -regtest listunspent 0
+{% endhighlight %}
+{% highlight json %}
+[
+ {
+ "txid" : "263c018582731ff54dc72c7d67e858c002ae298835501d\
+ 80200f05753de0edf0",
+ "vout" : 0,
+ "address" : "muhtvdmsnbQEPFuEmxcChX58fGvXaaUoVt",
+ "scriptPubKey" : "76a9149ba386253ea698158b6d34802bb9b550\
+ f5ce36dd88ac",
+ "amount" : 40.00000000,
+ "confirmations" : 0
+ },
+ {
+ "txid" : "263c018582731ff54dc72c7d67e858c002ae298835501d\
+ 80200f05753de0edf0",
+ "vout" : 1,
+ "address" : "mvbnrCX3bg1cDRUu8pkecrvP6vQkSLDSou",
+ "account" : "",
+ "scriptPubKey" : "76a914a57414e5ffae9ef5074bacbe10a320bb\
+ 2614e1f388ac",
+ "amount" : 10.00000000,
+ "confirmations" : 0
+ }
+]
+{% endhighlight %}
+
+
+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 satoshis to
+someone else, that second transaction would not be displayed in our
+list of UTXOs.
+
+~~~
+> bitcoin-cli -regtest setgenerate true 1
+
+> unset NEW_ADDRESS
+~~~
+
+Create a new block to confirm the transaction above (takes less than a
+second) and clear the shell variable.
+
+{% endautocrossref %}
+
+
+
+
+
+
+#### Simple Raw Transaction
+
+{% 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 Bitcoin Core, and a number of raw
+transaction users have permanently lost large numbers of satoshis, so
+please be careful using raw transactions on mainnet.
+
+This subsection covers one of the simplest possible raw transactions.
+
+
+{% highlight bash %}
+> bitcoin-cli -regtest listunspent
+{% endhighlight %}
+{% highlight json %}
+[
+ {
+ "txid" : "263c018582731ff54dc72c7d67e858c002ae298835501d\
+ 80200f05753de0edf0",
+ "vout" : 0,
+ "address" : "muhtvdmsnbQEPFuEmxcChX58fGvXaaUoVt",
+ "scriptPubKey" : "76a9149ba386253ea698158b6d34802bb9b550\
+ f5ce36dd88ac",
+ "amount" : 40.00000000,
+ "confirmations" : 1
+ },
+ {
+ "txid" : "263c018582731ff54dc72c7d67e858c002ae298835501d\
+ 80200f05753de0edf0",
+ "vout" : 1,
+ "address" : "mvbnrCX3bg1cDRUu8pkecrvP6vQkSLDSou",
+ "account" : "",
+ "scriptPubKey" : "76a914a57414e5ffae9ef5074bacbe10a320bb\
+ 2614e1f388ac",
+ "amount" : 10.00000000,
+ "confirmations" : 1
+ },
+ {
+ "txid" : "3f4fa19803dec4d6a84fae3821da7ac7577080ef754512\
+ 94e71f9b20e0ab1e7b",
+ "vout" : 0,
+ "address" : "mwJTL1dZG8BAP6X7Be3CNNcuVKi7Qqt7Gk",
+ "scriptPubKey" : "210260a275cccf0f4b106220725be516adba27\
+ 52db1bec8c5b7174c89c4c07891f88ac",
+ "amount" : 50.00000000,
+ "confirmations" : 101
+ }
+]
+{% endhighlight %}
+{% highlight bash %}
+
+> UTXO_TXID=3f4fa19803dec4d6a84fae3821da7ac7577080ef75451294e71f[...]
+> 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 %}
+> bitcoin-cli -regtest getnewaddress
+mz6KvC4aoUeo6wSxtiVQTo7FDwPnkp6URG
+
+> NEW_ADDRESS=mz6KvC4aoUeo6wSxtiVQTo7FDwPnkp6URG
+{% endhighlight %}
+
+Get a new address to use in the raw transaction.
+
+{% highlight bash %}
+> bitcoin-cli -regtest createrawtransaction '''
+ [
+ {
+ "txid": "'$UTXO_TXID'",
+ "vout": '$UTXO_VOUT'
+ }
+ ]
+ ''' '''
+ {
+ "'$NEW_ADDRESS'": 49.9999
+ }'''
+01000000017b1eabe0209b1fe794124575ef807057c77ada2138ae4fa8d6c4de\
+0398a14f3f0000000000ffffffff01f0ca052a010000001976a914cbc20a7664\
+f2f69e5355aa427045bc15e7c6c77288ac00000000
+
+> RAW_TX=01000000017b1eabe0209b1fe794124575ef807057c77ada2138ae4[...]
+{% 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 bitcoins 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 50.0000 bitcoins and our output
+(`$NEW_ADDRESS`) is being paid 49.9999 bitcoins, so the transaction will
+include a fee of 0.0001 bitcoins. If we had paid `$NEW_ADDRESS` only 10
+bitcoins with no other changes to this transaction, the transaction fee
+would be a whopping 40 bitcoins. 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.
+
+
+
+{% highlight bash %}
+> bitcoin-cli -regtest decoderawtransaction $RAW_TX
+{% endhighlight %}
+{% highlight json %}
+{
+ "txid" : "c80b343d2ce2b5d829c2de9854c7c8d423c0e33bda264c4013\
+ 8d834aab4c0638",
+ "version" : 1,
+ "locktime" : 0,
+ "vin" : [
+ {
+ "txid" : "3f4fa19803dec4d6a84fae3821da7ac7577080ef75\
+ 451294e71f9b20e0ab1e7b",
+ "vout" : 0,
+ "scriptSig" : {
+ "asm" : "",
+ "hex" : ""
+ },
+ "sequence" : 4294967295
+ }
+ ],
+ "vout" : [
+ {
+ "value" : 49.99990000,
+ "n" : 0,
+ "scriptPubKey" : {
+ "asm" : "OP_DUP OP_HASH160 cbc20a7664f2f69e5355a\
+ a427045bc15e7c6c772 OP_EQUALVERIFY OP_CHECKSIG",
+ "hex" : "76a914cbc20a7664f2f69e5355aa427045bc15e\
+ 7c6c77288ac",
+ "reqSigs" : 1,
+ "type" : "pubkeyhash",
+ "addresses" : [
+ "mz6KvC4aoUeo6wSxtiVQTo7FDwPnkp6URG"
+ ]
+ }
+ }
+ ]
+}
+{% endhighlight %}
+
+
+Use the `decoderawtransaction` RPC to see exactly what the transaction
+we just created does.
+
+
+{% highlight bash %}
+> bitcoin-cli -regtest signrawtransaction $RAW_TX
+{% endhighlight %}
+{% highlight json %}
+{
+ "hex" : "01000000017b1eabe0209b1fe794124575ef807057c77ada213\
+ 8ae4fa8d6c4de0398a14f3f00000000494830450221008949f0\
+ cb400094ad2b5eb399d59d01c14d73d8fe6e96df1a7150deb38\
+ 8ab8935022079656090d7f6bac4c9a94e0aad311a4268e082a7\
+ 25f8aeae0573fb12ff866a5f01ffffffff01f0ca052a0100000\
+ 01976a914cbc20a7664f2f69e5355aa427045bc15e7c6c77288\
+ ac00000000",
+ "complete" : true
+}
+{% endhighlight %}
+{% highlight bash %}
+
+> SIGNED_RAW_TX=01000000017b1eabe0209b1fe794124575ef807057c77ada[...]
+{% 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 Bitcoin 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 %}
+> bitcoin-cli -regtest sendrawtransaction $SIGNED_RAW_TX
+c7736a0a0046d5a8cc61c8c3c2821d4d7517f5de2bc66a966011aaa79965ffba
+{% 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.
+
+~~~
+> bitcoin-cli -regtest setgenerate true 1
+
+> unset UTXO_TXID UTXO_VOUT NEW_ADDRESS RAW_TX SIGNED_RAW_TX
+~~~
+
+Generate a block to confirm the transaction and clear our shell
+variables.
+
+{% endautocrossref %}
+
+
+
+
+
+#### Complex Raw Transaction
+
+{% 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).
+
+
+{% highlight bash %}
+> bitcoin-cli -regtest listunspent
+{% endhighlight %}
+{% highlight json %}
+[
+ {
+ "txid" : "263c018582731ff54dc72c7d67e858c002ae298835501d\
+ 80200f05753de0edf0",
+ "vout" : 0,
+ "address" : "muhtvdmsnbQEPFuEmxcChX58fGvXaaUoVt",
+ "scriptPubKey" : "76a9149ba386253ea698158b6d34802bb9b550\
+ f5ce36dd88ac",
+ "amount" : 40.00000000,
+ "confirmations" : 2
+ },
+ {
+ "txid" : "263c018582731ff54dc72c7d67e858c002ae298835501d\
+ 80200f05753de0edf0",
+ "vout" : 1,
+ "address" : "mvbnrCX3bg1cDRUu8pkecrvP6vQkSLDSou",
+ "account" : "",
+ "scriptPubKey" : "76a914a57414e5ffae9ef5074bacbe10a320bb\
+ 2614e1f388ac",
+ "amount" : 10.00000000,
+ "confirmations" : 2
+ },
+ {
+ "txid" : "78203a8f6b529693759e1917a1b9f05670d036fbb12911\
+ 0ed26be6a36de827f3",
+ "vout" : 0,
+ "address" : "n2KprMQm4z2vmZnPMENfbp2P1LLdAEFRjS",
+ "scriptPubKey" : "210229688a74abd0d5ad3b06ddff36fa9cd8ed\
+ d181d97b9489a6adc40431fb56e1d8ac",
+ "amount" : 50.00000000,
+ "confirmations" : 101
+ },
+ {
+ "txid" : "c7736a0a0046d5a8cc61c8c3c2821d4d7517f5de2bc66a\
+ 966011aaa79965ffba",
+ "vout" : 0,
+ "address" : "mz6KvC4aoUeo6wSxtiVQTo7FDwPnkp6URG",
+ "account" : "",
+ "scriptPubKey" : "76a914cbc20a7664f2f69e5355aa427045bc15\
+ e7c6c77288ac",
+ "amount" : 49.99990000,
+ "confirmations" : 1
+ }
+]
+{% endhighlight %}
+{% highlight bash %}
+
+> UTXO1_TXID=78203a8f6b529693759e1917a1b9f05670d036fbb129110ed26[...]
+> UTXO1_VOUT=0
+> UTXO1_ADDRESS=n2KprMQm4z2vmZnPMENfbp2P1LLdAEFRjS
+
+> UTXO2_TXID=263c018582731ff54dc72c7d67e858c002ae298835501d80200[...]
+> UTXO2_VOUT=0
+> UTXO2_ADDRESS=muhtvdmsnbQEPFuEmxcChX58fGvXaaUoVt
+{% 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 %}
+> bitcoin-cli -regtest dumpprivkey $UTXO1_ADDRESS
+cSp57iWuu5APuzrPGyGc4PGUeCg23PjenZPBPoUs24HtJawccHPm
+
+> bitcoin-cli -regtest dumpprivkey $UTXO2_ADDRESS
+cT26DX6Ctco7pxaUptJujRfbMS2PJvdqiSMaGaoSktHyon8kQUSg
+
+> UTXO1_PRIVATE_KEY=cSp57iWuu5APuzrPGyGc4PGUeCg23PjenZPBPoUs24Ht[...]
+
+> UTXO2_PRIVATE_KEY=cT26DX6Ctco7pxaUptJujRfbMS2PJvdqiSMaGaoSktHy[...]
+{% 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.
+
+{% highlight bash %}
+> bitcoin-cli -regtest getnewaddress
+n4puhBEeEWD2VvjdRC9kQuX2abKxSCMNqN
+> bitcoin-cli -regtest getnewaddress
+n4LWXU59yM5MzQev7Jx7VNeq1BqZ85ZbLj
+
+> NEW_ADDRESS1=n4puhBEeEWD2VvjdRC9kQuX2abKxSCMNqN
+> NEW_ADDRESS2=n4LWXU59yM5MzQev7Jx7VNeq1BqZ85ZbLj
+{% endhighlight %}
+
+For our two outputs, get two new addresses.
+
+{% highlight bash %}
+> bitcoin-cli -regtest createrawtransaction '''
+ [
+ {
+ "txid": "'$UTXO1_TXID'",
+ "vout": '$UTXO1_VOUT'
+ },
+ {
+ "txid": "'$UTXO2_TXID'",
+ "vout": '$UTXO2_VOUT'
+ }
+ ]
+ ''' '''
+ {
+ "'$NEW_ADDRESS1'": 79.9999,
+ "'$NEW_ADDRESS2'": 10
+ }'''
+0100000002f327e86da3e66bd20e1129b1fb36d07056f0b9a117199e75939652\
+6b8f3a20780000000000fffffffff0ede03d75050f20801d50358829ae02c058\
+e8677d2cc74df51f738285013c260000000000ffffffff02f028d6dc01000000\
+1976a914ffb035781c3c69e076d48b60c3d38592e7ce06a788ac00ca9a3b0000\
+00001976a914fa5139067622fd7e1e722a05c17c2bb7d5fd6df088ac00000000
+
+> RAW_TX=0100000002f327e86da3e66bd20e1129b1fb36d07056f0b9a117199[...]
+{% endhighlight %}
+
+Create the raw transaction using `createrawtransaction` much the same as
+before, except now we have two inputs and two outputs.
+
+
+
+{% highlight bash %}
+> bitcoin-cli -regtest signrawtransaction $RAW_TX '[]' '''
+ [
+ "'$UTXO1_PRIVATE_KEY'"
+ ]'''
+{% endhighlight %}
+{% highlight json %}
+{
+ "hex" : "0100000002f327e86da3e66bd20e1129b1fb36d07056f0b9a11\
+ 7199e759396526b8f3a20780000000049483045022100fce442\
+ ec52aa2792efc27fd3ad0eaf7fa69f097fdcefab017ea56d179\
+ 9b10b2102207a6ae3eb61e11ffaba0453f173d1792f1b7bb8e7\
+ 422ea945101d68535c4b474801fffffffff0ede03d75050f208\
+ 01d50358829ae02c058e8677d2cc74df51f738285013c260000\
+ 000000ffffffff02f028d6dc010000001976a914ffb035781c3\
+ c69e076d48b60c3d38592e7ce06a788ac00ca9a3b0000000019\
+ 76a914fa5139067622fd7e1e722a05c17c2bb7d5fd6df088ac0\
+ 0000000",
+ "complete" : false
+}
+{% endhighlight %}
+{% highlight bash %}
+
+> PARTLY_SIGNED_RAW_TX=0100000002f327e86da3e66bd20e1129b1fb36d07[...]
+{% endhighlight %}
+
+
+Signing the raw transaction with `signrawtransaction` gets more
+complicated as we now have three arguments:
+
+1. The unsigned raw transaction.
+
+2. 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.
+
+3. 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.
+
+
+{% highlight bash %}
+> bitcoin-cli -regtest signrawtransaction $PARTLY_SIGNED_RAW_TX '[]' '''
+ [
+ "'$UTXO2_PRIVATE_KEY'"
+ ]'''
+{% endhighlight %}
+{% highlight json %}
+{
+ "hex" : "0100000002f327e86da3e66bd20e1129b1fb36d07056f0b9a11\
+ 7199e759396526b8f3a20780000000049483045022100fce442\
+ ec52aa2792efc27fd3ad0eaf7fa69f097fdcefab017ea56d179\
+ 9b10b2102207a6ae3eb61e11ffaba0453f173d1792f1b7bb8e7\
+ 422ea945101d68535c4b474801fffffffff0ede03d75050f208\
+ 01d50358829ae02c058e8677d2cc74df51f738285013c260000\
+ 00006b483045022100b77f935ff366a6f3c2fdeb83589c79026\
+ 5d43b3d2cf5e5f0047da56c36de75f40220707ceda75d8dcf2c\
+ caebc506f7293c3dcb910554560763d7659fb202f8ec324b012\
+ 102240d7d3c7aad57b68aa0178f4c56f997d1bfab2ded3c2f94\
+ 27686017c603a6d6ffffffff02f028d6dc010000001976a914f\
+ fb035781c3c69e076d48b60c3d38592e7ce06a788ac00ca9a3b\
+ 000000001976a914fa5139067622fd7e1e722a05c17c2bb7d5f\
+ d6df088ac00000000",
+ "complete" : true
+}
+{% endhighlight %}
+
+
+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
+
+{% 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.
+
+{% highlight bash %}
+> OLD_SIGNED_RAW_TX=0100000002f327e86da3e66bd20e1129b1fb36d07056\
+ f0b9a117199e759396526b8f3a20780000000049483045022100fce442\
+ ec52aa2792efc27fd3ad0eaf7fa69f097fdcefab017ea56d1799b10b21\
+ 02207a6ae3eb61e11ffaba0453f173d1792f1b7bb8e7422ea945101d68\
+ 535c4b474801fffffffff0ede03d75050f20801d50358829ae02c058e8\
+ 677d2cc74df51f738285013c26000000006b483045022100b77f935ff3\
+ 66a6f3c2fdeb83589c790265d43b3d2cf5e5f0047da56c36de75f40220\
+ 707ceda75d8dcf2ccaebc506f7293c3dcb910554560763d7659fb202f8\
+ ec324b012102240d7d3c7aad57b68aa0178f4c56f997d1bfab2ded3c2f\
+ 9427686017c603a6d6ffffffff02f028d6dc010000001976a914ffb035\
+ 781c3c69e076d48b60c3d38592e7ce06a788ac00ca9a3b000000001976\
+ a914fa5139067622fd7e1e722a05c17c2bb7d5fd6df088ac00000000
+{% endhighlight %}
+
+Put the previously signed (but not sent) transaction into a shell
+variable.
+
+
+{% highlight bash %}
+> bitcoin-cli -regtest decoderawtransaction $OLD_SIGNED_RAW_TX
+{% endhighlight %}
+{% highlight json %}
+{
+ "txid" : "682cad881df69cb9df8f0c996ce96ecad758357ded2da03bad\
+ 40cf18ffbb8e09",
+ "version" : 1,
+ "locktime" : 0,
+ "vin" : [
+ {
+ "txid" : "78203a8f6b529693759e1917a1b9f05670d036fbb1\
+ 29110ed26be6a36de827f3",
+ "vout" : 0,
+ "scriptSig" : {
+ "asm" : "3045022100fce442ec52aa2792efc27fd3ad0ea\
+ f7fa69f097fdcefab017ea56d1799b10b210220\
+ 7a6ae3eb61e11ffaba0453f173d1792f1b7bb8e\
+ 7422ea945101d68535c4b474801",
+ "hex" : "483045022100FCE442ec52aa2792efc27fd3ad0\
+ eaf7fa69f097fdcefab017ea56d1799b10b2102\
+ 207a6ae3eb61e11ffaba0453f173d1792f1b7bb\
+ 8e7422ea945101d68535c4b474801"
+ },
+ "sequence" : 4294967295
+ },
+ {
+ "txid" : "263c018582731ff54dc72c7d67e858c002ae298835\
+ 501d80200f05753de0edf0",
+ "vout" : 0,
+ "scriptSig" : {
+ "asm" : "3045022100b77f935ff366a6f3c2fdeb83589c7\
+ 90265d43b3d2cf5e5f0047da56c36de75f40220\
+ 707ceda75d8dcf2ccaebc506f7293c3dcb91055\
+ 4560763d7659fb202f8ec324b01
+ 02240d7d3c7aad57b68aa0178f4c56f997d1bfa\
+ b2ded3c2f9427686017c603a6d6",
+ "hex" : "483045022100b77f935ff366a6f3c2fdeb83589\
+ c790265d43b3d2cf5e5f0047da56c36de75f402\
+ 20707ceda75d8dcf2ccaebc506f7293c3dcb910\
+ 554560763d7659fb202f8ec324b012102240d7d\
+ 3c7aad57b68aa0178f4c56f997d1bfab2ded3c2\
+ f9427686017c603a6d6"
+ },
+ "sequence" : 4294967295
+ }
+ ],
+ "vout" : [
+ {
+ "value" : 79.99990000,
+ "n" : 0,
+ "scriptPubKey" : {
+ "asm" : "OP_DUP OP_HASH160 ffb035781c3c69e076d48\
+ b60c3d38592e7ce06a7 OP_EQUALVERIFY OP_CHECKSIG",
+ "hex" : "76a914ffb035781c3c69e076d48b60c3d38592e\
+ 7ce06a788ac",
+ "reqSigs" : 1,
+ "type" : "pubkeyhash",
+ "addresses" : [
+ "n4puhBEeEWD2VvjdRC9kQuX2abKxSCMNqN"
+ ]
+ }
+ },
+ {
+ "value" : 10.00000000,
+ "n" : 1,
+ "scriptPubKey" : {
+ "asm" : "OP_DUP OP_HASH160 fa5139067622fd7e1e722\
+ a05c17c2bb7d5fd6df0 OP_EQUALVERIFY OP_CHECKSIG",
+ "hex" : "76a914fa5139067622fd7e1e722a05c17c2bb7d\
+ 5fd6df088ac",
+ "reqSigs" : 1,
+ "type" : "pubkeyhash",
+ "addresses" : [
+ "n4LWXU59yM5MzQev7Jx7VNeq1BqZ85ZbLj"
+ ]
+ }
+ }
+ ]
+}
+{% endhighlight %}
+{% highlight bash %}
+
+> UTXO_TXID=682cad881df69cb9df8f0c996ce96ecad758357ded2da03bad40[...]
+> UTXO_VOUT=1
+> UTXO_OUTPUT_SCRIPT=76a914fa5139067622fd7e1e722a05c17c2bb7d5fd6[...]
+{% 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 output script (scriptPubKey) into shell variables.
+
+{% highlight bash %}
+> bitcoin-cli -regtest getnewaddress
+mfdCHEFL2tW9eEUpizk7XLZJcnFM4hrp78
+
+> NEW_ADDRESS=mfdCHEFL2tW9eEUpizk7XLZJcnFM4hrp78
+{% endhighlight %}
+
+Get a new address to spend the satoshis to.
+
+{% highlight bash %}
+> bitcoin-cli -regtest createrawtransaction '''
+ [
+ {
+ "txid": "'$UTXO_TXID'",
+ "vout": '$UTXO_VOUT'
+ }
+ ]
+ ''' '''
+ {
+ "'$NEW_ADDRESS'": 9.9999
+ }'''
+0100000001098ebbff18cf40ad3ba02ded7d3558d7ca6ee96c990c8fdfb99cf6\
+1d88ad2c680100000000ffffffff01f0a29a3b000000001976a914012e2ba6a0\
+51c033b03d712ca2ea00a35eac1e7988ac00000000
+
+> RAW_TX=0100000001098ebbff18cf40ad3ba02ded7d3558d7ca6ee96c990c8[...]
+{% endhighlight %}
+
+Create the raw transaction the same way we've done in the previous
+subsections.
+
+
+{% highlight bash %}
+ > bitcoin-cli -regtest signrawtransaction $RAW_TX
+{% endhighlight %}
+{% highlight json %}
+ {
+ "hex" : "0100000001098ebbff18cf40ad3ba02ded7d3558d7ca6ee\
+ 96c990c8fdfb99cf61d88ad2c680100000000ffffffff01\
+ f0a29a3b000000001976a914012e2ba6a051c033b03d712\
+ ca2ea00a35eac1e7988ac00000000",
+ "complete" : false
+ }
+{% endhighlight %}
+
+
+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 output 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 output 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 output script.
+
+
+{% highlight bash %}
+> bitcoin-cli -regtest signrawtransaction $RAW_TX '''
+ [
+ {
+ "txid": "'$UTXO_TXID'",
+ "vout": '$UTXO_VOUT',
+ "scriptPubKey": "'$UTXO_OUTPUT_SCRIPT'"
+ }
+ ]'''
+{% endhighlight %}
+{% highlight json %}
+{
+ "hex" : "0100000001098ebbff18cf40ad3ba02ded7d3558d7ca6ee96c9\
+ 90c8fdfb99cf61d88ad2c68010000006b483045022100c3f92f\
+ b74bfa687d76ebe75a654510bb291b8aab6f89ded4fe26777c2\
+ eb233ad02207f779ce2a181cc4055cb0362aba7fd7a6f72d5db\
+ b9bd863f4faaf47d8d6c4b500121028e4e62d25760709806131\
+ b014e2572f7590e70be01f0ef16bfbd51ea5f389d4dffffffff\
+ 01f0a29a3b000000001976a914012e2ba6a051c033b03d712ca\
+ 2ea00a35eac1e7988ac00000000",
+ "complete" : true
+}
+{% endhighlight %}
+{% highlight bash %}
+
+> SIGNED_RAW_TX=0100000001098ebbff18cf40ad3ba02ded7d3558d7ca6ee9[...]
+{% endhighlight %}
+
+
+Successfully sign the transaction by providing the previous output
+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
+output 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.
+
+
+{% highlight bash %}
+> bitcoin-cli -regtest sendrawtransaction $SIGNED_RAW_TX
+{% endhighlight %}
+{% highlight json %}
+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 %}
+> bitcoin-cli -regtest sendrawtransaction $OLD_SIGNED_RAW_TX
+682cad881df69cb9df8f0c996ce96ecad758357ded2da03bad40cf18ffbb8e09
+> bitcoin-cli -regtest sendrawtransaction $SIGNED_RAW_TX
+67d53afa1a8167ca093d30be7fb9dcb8a64a5fdecacec9d93396330c47052c57
+{% endhighlight %}
+
+Broadcast the first transaction, which succeeds, and then broadcast the
+second transaction---which also now succeeds because the node now sees
+the UTXO.
+
+
+{% highlight bash %}
+> bitcoin-cli -regtest getrawmempool
+{% endhighlight %}
+{% highlight json %}
+[
+ "67d53afa1a8167ca093d30be7fb9dcb8a64a5fdecacec9d93396330c47052c57",
+ "682cad881df69cb9df8f0c996ce96ecad758357ded2da03bad40cf18ffbb8e09"
+]
+{% endhighlight %}
+
+
+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
+
+{% autocrossref %}
+
+In this subsection, we will create a P2SH multisig address, spend
+satoshis to it, and then spend those satoshis 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 %}
+ > bitcoin-cli -regtest getnewaddress
+ mhAXF4Eq7iRyvbYk1mpDVBiGdLP3YbY6Dm
+ > bitcoin-cli -regtest getnewaddress
+ moaCrnRfP5zzyhW8k65f6Rf2z5QpvJzSKe
+ > bitcoin-cli -regtest getnewaddress
+ mk2QpYatsKicvFVuTAQLBryyccRXMUaGHP
+
+ > NEW_ADDRESS1=mhAXF4Eq7iRyvbYk1mpDVBiGdLP3YbY6Dm
+ > NEW_ADDRESS2=moaCrnRfP5zzyhW8k65f6Rf2z5QpvJzSKe
+ > NEW_ADDRESS3=mk2QpYatsKicvFVuTAQLBryyccRXMUaGHP
+{% endhighlight %}
+
+Generate three new P2PKH addresses. P2PKH addresses cannot be used with
+the multisig redeemScript created below. (Hashing each public key is
+unnecessary anyway---all the public keys are protected by a hash when
+the redeemScript is hashed.) However, Bitcoin 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][address] 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
+redeemScript. You must give them a full public key.
+
+
+{% highlight bash %}
+> bitcoin-cli -regtest validateaddress $NEW_ADDRESS3
+{% endhighlight %}
+{% highlight json %}
+{
+ "isvalid" : true,
+ "address" : "mk2QpYatsKicvFVuTAQLBryyccRXMUaGHP",
+ "ismine" : true,
+ "isscript" : false,
+ "pubkey" : "029e03a901b85534ff1e92c43c74431f7ce72046060fcf7a\
+ 95c37e148f78c77255",
+ "iscompressed" : true,
+ "account" : ""
+}
+{% endhighlight %}
+{% highlight bash %}
+
+> NEW_ADDRESS3_PUBLIC_KEY=029e03a901b85534ff1e92c43c74431f7ce720[...]
+{% 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 redeemScript. This is also the
+information you would give another person or device as part of creating
+a multisig output or P2SH multisig redeemScript.
+
+We save the address returned to a shell variable.
+
+
+{% highlight bash %}
+> bitcoin-cli -regtest createmultisig 2 '''
+ [
+ "'$NEW_ADDRESS1'",
+ "'$NEW_ADDRESS2'",
+ "'$NEW_ADDRESS3_PUBLIC_KEY'"
+ ]'''
+{% endhighlight %}
+{% highlight json %}
+{
+ "address" : "2N7NaqSKYQUeM8VNgBy8D9xQQbiA8yiJayk",
+ "redeemScript" : "522103310188e911026cf18c3ce274e0ebb5f95b00\
+ 7f230d8cb7d09879d96dbeab1aff210243930746e6ed6552e03359db521b\
+ 088134652905bd2d1541fa9124303a41e95621029e03a901b85534ff1e92\
+ c43c74431f7ce72046060fcf7a95c37e148f78c7725553ae"
+}
+{% endhighlight %}
+{% highlight bash %}
+
+> P2SH_ADDRESS=2N7NaqSKYQUeM8VNgBy8D9xQQbiA8yiJayk
+> P2SH_REDEEM_SCRIPT=522103310188e911026cf18c3ce274e0ebb5f95b007[...]
+{% 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 redeemScript 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
+redeemScript.
+
+The P2SH address is returned along with the redeemScript which must be
+provided when we spend satoshis sent to the P2SH address.
+
+**Warning:** You must not lose the redeemScript, especially if you
+don't have a record of which public keys you used to create the P2SH
+multisig address. You need the redeemScript to spend any bitcoins sent
+to the P2SH address. If you lose the redeemScript, 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 redeemScript and even one of
+the public keys, you will never be able to spend satoshis sent to that
+P2SH address.
+
+Neither the address nor the redeemScript 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 %}
+> bitcoin-cli -regtest sendtoaddress $P2SH_ADDRESS 10.00
+7278d7d030f042ebe633732b512bcb31fff14a697675a1fe1884db139876e175
+
+> UTXO_TXID=7278d7d030f042ebe633732b512bcb31fff14a697675a1fe1884[...]
+{% endhighlight %}
+
+Paying the P2SH multisig address with Bitcoin 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.
+
+
+{% highlight bash %}
+> bitcoin-cli -regtest getrawtransaction $UTXO_TXID 1
+{% endhighlight %}
+{% highlight json %}
+{
+ "hex" : "0100000001f0ede03d75050f20801d50358829ae02c058e8677\
+ d2cc74df51f738285013c26010000006a47304402203c375959\
+ 2bf608ab79c01596c4a417f3110dd6eb776270337e575cdafc6\
+ 99af20220317ef140d596cc255a4067df8125db7f349ad94521\
+ 2e9264a87fa8d777151937012102a92913b70f9fb15a7ea5c42\
+ df44637f0de26e2dad97d6d54957690b94cf2cd05ffffffff01\
+ 00ca9a3b0000000017a9149af61346ce0aa2dffcf697352b4b7\
+ 04c84dcbaff8700000000",
+ "txid" : "7278d7d030f042ebe633732b512bcb31fff14a697675a1fe18\
+ 84db139876e175",
+ "version" : 1,
+ "locktime" : 0,
+ "vin" : [
+ {
+ "txid" : "263c018582731ff54dc72c7d67e858c002ae298835\
+ 501d80200f05753de0edf0",
+ "vout" : 1,
+ "scriptSig" : {
+ "asm" : "304402203c3759592bf608ab79c01596c4a417f\
+ 3110dd6eb776270337e575cdafc699af2022031\
+ 7ef140d596cc255a4067df8125db7f349ad9452\
+ 12e9264a87fa8d77715193701
+ 02a92913b70f9fb15a7ea5c42df44637f0de26e\
+ 2dad97d6d54957690b94cf2cd05",
+ "hex" : "47304402203c3759592bf608ab79c01596c4a41\
+ 7f3110dd6eb776270337e575cdafc699af20220\
+ 317ef140d596cc255a4067df8125db7f349ad94\
+ 5212e9264a87fa8d777151937012102a92913b7\
+ 0f9fb15a7ea5c42df44637f0de26e2dad97d6d5\
+ 4957690b94cf2cd05"
+ },
+ "sequence" : 4294967295
+ }
+ ],
+ "vout" : [
+ {
+ "value" : 10.00000000,
+ "n" : 0,
+ "scriptPubKey" : {
+ "asm" : "OP_HASH160 9af61346ce0aa2dffcf697352b4b\
+ 704c84dcbaff OP_EQUAL",
+ "hex" : "a9149af61346ce0aa2dffcf697352b4b704c84d\
+ cbaff87",
+ "reqSigs" : 1,
+ "type" : "scripthash",
+ "addresses" : [
+ "2N7NaqSKYQUeM8VNgBy8D9xQQbiA8yiJayk"
+ ]
+ }
+ }
+ ]
+}
+{% endhighlight %}
+{% highlight bash %}
+
+> UTXO_VOUT=0
+> UTXO_OUTPUT_SCRIPT=a9149af61346ce0aa2dffcf697352b4b704c84dcbaff87
+{% endhighlight %}
+
+
+We use the `getrawtransaction` RPC with the optional second argument
+(*true*) to get the decoded transaction we just created with
+`spendtoaddress`. We choose one of the outputs to be our UTXO and get
+its output index number (vout) and output script (scriptPubKey).
+
+{% highlight bash %}
+> bitcoin-cli -regtest getnewaddress
+mxCNLtKxzgjg8yyNHeuFSXvxCvagkWdfGU
+
+> NEW_ADDRESS4=mxCNLtKxzgjg8yyNHeuFSXvxCvagkWdfGU
+{% endhighlight %}
+
+We generate a new P2PKH address to use in the output we're about to
+create.
+
+{% highlight bash %}
+> bitcoin-cli -regtest createrawtransaction '''
+ [
+ {
+ "txid": "'$UTXO_TXID'",
+ "vout": '$UTXO_VOUT'
+ }
+ ]
+ ''' '''
+ {
+ "'$NEW_ADDRESS4'": 9.998
+ }'''
+
+010000000175e1769813db8418fea17576694af1ff31cb2b512b7333e6eb42f0\
+30d0d778720000000000ffffffff01c0bc973b000000001976a914b6f64f5bf3\
+e38f25ead28817df7929c06fe847ee88ac00000000
+
+> RAW_TX=010000000175e1769813db8418fea17576694af1ff31cb2b512b733[...]
+{% endhighlight %}
+
+We generate the raw transaction the same way we did in the Simple Raw
+Transaction subsection.
+
+{% highlight bash %}
+> bitcoin-cli -regtest dumpprivkey $NEW_ADDRESS1
+cVinshabsALz5Wg4tGDiBuqEGq4i6WCKWXRQdM8RFxLbALvNSHw7
+> bitcoin-cli -regtest dumpprivkey $NEW_ADDRESS3
+cNmbnwwGzEghMMe1vBwH34DFHShEj5bcXD1QpFRPHgG9Mj1xc5hq
+
+> NEW_ADDRESS1_PRIVATE_KEY=cVinshabsALz5Wg4tGDiBuqEGq4i6WCKWXRQd[...]
+> NEW_ADDRESS3_PRIVATE_KEY=cNmbnwwGzEghMMe1vBwH34DFHShEj5bcXD1Qp[...]
+{% 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 script,
+so signatures from two private keys are needed.
+
+
+{% highlight bash %}
+> bitcoin-cli -regtest signrawtransaction $RAW_TX '''
+ [
+ {
+ "txid": "'$UTXO_TXID'",
+ "vout": '$UTXO_VOUT',
+ "scriptPubKey": "'$UTXO_OUTPUT_SCRIPT'",
+ "redeemScript": "'$P2SH_REDEEM_SCRIPT'"
+ }
+ ]
+ ''' '''
+ [
+ "'$NEW_ADDRESS1_PRIVATE_KEY'"
+ ]'''
+{% endhighlight %}
+{% highlight json %}
+{
+ "hex" : "010000000175e1769813db8418fea17576694af1ff31cb2b512\
+ b7333e6eb42f030d0d7787200000000b5004830450221008d5e\
+ c57d362ff6ef6602e4e756ef1bdeee12bd5c5c72697ef1455b3\
+ 79c90531002202ef3ea04dfbeda043395e5bc701e4878c15baa\
+ b9c6ba5808eb3d04c91f641a0c014c69522103310188e911026\
+ cf18c3ce274e0ebb5f95b007f230d8cb7d09879d96dbeab1aff\
+ 210243930746e6ed6552e03359db521b088134652905bd2d154\
+ 1fa9124303a41e95621029e03a901b85534ff1e92c43c74431f\
+ 7ce72046060fcf7a95c37e148f78c7725553aeffffffff01c0b\
+ c973b000000001976a914b6f64f5bf3e38f25ead28817df7929\
+ c06fe847ee88ac00000000",
+ "complete" : false
+}
+{% endhighlight %}
+{% highlight bash %}
+
+> PARTLY_SIGNED_RAW_TX=010000000175e1769813db8418fea17576694af1f[...]
+{% endhighlight %}
+
+
+We make the first signature. The input argument (JSON object) takes the
+additional redeemScript parameter so that it can append the redeemScript
+to the scriptSig after the two signatures.
+
+
+{% highlight bash %}
+> bitcoin-cli -regtest signrawtransaction $PARTLY_SIGNED_RAW_TX '''
+ [
+ {
+ "txid": "'$UTXO_TXID'",
+ "vout": '$UTXO_VOUT',
+ "scriptPubKey": "'$UTXO_OUTPUT_SCRIPT'",
+ "redeemScript": "'$P2SH_REDEEM_SCRIPT'"
+ }
+ ]
+ ''' '''
+ [
+ "'$NEW_ADDRESS3_PRIVATE_KEY'"
+ ]'''
+{% endhighlight %}
+{% highlight json %}
+{
+ "hex" : "010000000175e1769813db8418fea17576694af1ff31cb2b512\
+ b7333e6eb42f030d0d7787200000000fdfd0000483045022100\
+ 8d5ec57d362ff6ef6602e4e756ef1bdeee12bd5c5c72697ef14\
+ 55b379c90531002202ef3ea04dfbeda043395e5bc701e4878c1\
+ 5baab9c6ba5808eb3d04c91f641a0c0147304402200bd8c62b9\
+ 38e02094021e481b149fd5e366a212cb823187149799a68cfa7\
+ 652002203b52120c5cf25ceab5f0a6b5cdb8eca0fd2f386316c\
+ 9721177b75ddca82a4ae8014c69522103310188e911026cf18c\
+ 3ce274e0ebb5f95b007f230d8cb7d09879d96dbeab1aff21024\
+ 3930746e6ed6552e03359db521b088134652905bd2d1541fa91\
+ 24303a41e95621029e03a901b85534ff1e92c43c74431f7ce72\
+ 046060fcf7a95c37e148f78c7725553aeffffffff01c0bc973b\
+ 000000001976a914b6f64f5bf3e38f25ead28817df7929c06fe\
+ 847ee88ac00000000",
+ "complete" : true
+}
+{% endhighlight %}
+{% highlight bash %}
+
+> SIGNED_RAW_TX=010000000175e1769813db8418fea17576694af1ff31cb2b[...]
+{% 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 %}
+> bitcoin-cli -regtest sendrawtransaction $SIGNED_RAW_TX
+430a4cee3a55efb04cbb8718713cab18dea7f2521039aa660ffb5aae14ff3f50
+{% endhighlight %}
+
+We send the transaction spending the P2SH multisig output to the local
+node, which accepts it.
+
+{% endautocrossref %}
diff --git a/_includes/references.md b/_includes/references.md
index 1300a004..a925f4cd 100644
--- a/_includes/references.md
+++ b/_includes/references.md
@@ -181,6 +181,7 @@
[core paymentrequest.proto]: https://github.com/bitcoin/bitcoin/blob/master/src/qt/paymentrequest.proto
[core script.h]: https://github.com/bitcoin/bitcoin/blob/master/src/script.h
[DER]: https://en.wikipedia.org/wiki/Abstract_Syntax_Notation_One
+[devguide]: /en/developer-guide
[devguide wallets]: /en/developer-guide#wallets
[devref wallets]: /en/developer-reference#wallets
[docs issue]: https://github.com/bitcoin/bitcoin.org/issues
diff --git a/_less/screen.less b/_less/screen.less
index fd348e8b..f84ca7ab 100644
--- a/_less/screen.less
+++ b/_less/screen.less
@@ -769,6 +769,21 @@ table td,table th{
color:#646464;
}
+.toccontent .multicode {
+ background-color:#f5f5f5;
+ border:1px solid #ccc;
+ overflow-y:auto;
+ padding-bottom: 17px;
+}
+
+.toccontent .multicode pre {
+ border: 0px none;
+ padding: 0px;
+ overflow-y: visible;
+ margin-bottom: -17px;
+}
+
+
.highlight { background: #ffffff; }
.highlight .c { color: #999988; font-style: italic } /* Comment */
.highlight .err { color: #a61717; background-color: #e3d2d2 } /* Error */
diff --git a/_plugins/autocrossref.rb b/_plugins/autocrossref.rb
index 5ddaa792..f479ec8e 100644
--- a/_plugins/autocrossref.rb
+++ b/_plugins/autocrossref.rb
@@ -63,6 +63,8 @@ require 'yaml'
(?![^\[]*\]) ## No subst if key inside [brackets]
(?![^\{]*\}) ## No subst if key inside {braces}
(?![^\s]*) ## No subst if after key
+ (?![\S ]*<\/span>) ## No subst on a line with a close span. This
+ ## prevents matching in highlight blocks
(?![^\(]*(\.svg|\.png)) ## No subst if key inside an image name. This
## simple regex has the side effect that we can't
## use .svg or .png in non-image base text; if that
diff --git a/en/developer-documentation.md b/en/developer-documentation.md
index f3480801..dee2afb7 100644
--- a/en/developer-documentation.md
+++ b/en/developer-documentation.md
@@ -12,6 +12,7 @@ title: "Developer Documentation - Bitcoin"
diff --git a/en/developer-reference.md b/en/developer-reference.md
index 83e250fa..c93aa32c 100644
--- a/en/developer-reference.md
+++ b/en/developer-reference.md
@@ -22,7 +22,6 @@ title: "Developer Reference - Bitcoin"
{% include ref_block_chain.md %}
{% include ref_transactions.md %}
{% include ref_wallets.md %}
-{% include ref_payment_processing.md %}
## Bitcoin Core APIs
Developer Guide(How Bitcoin works)