joshua/dash-docs
1
0
Fork 0
mirror of https://github.com/seigler/dash-docs synced 2025-07-27 09:46:12 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Set license files and headers for bitcoin.org's content

Browse source
This commit is contained in:
Saivann 2014-11-21 17:13:43 -05:00
parent 27f1da3ba8
commit 2a139a51a1
276 changed files with 524 additions and 171 deletions
Download patch file Download diff file Expand all files Collapse all files

15
_includes/example_transactions.md
View file

@ -1,3 +1,8 @@
{% comment %}
This file is licensed under the MIT License (MIT) available on
http://opensource.org/licenses/MIT.
{% endcomment %}
## Transactions
### Transaction Tutorial
@ -221,7 +226,7 @@ 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 icon](/img/icon_warning.svg)
![Warning icon](/img/icons/icon_warning.svg)
**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
@ -429,7 +434,7 @@ 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 icon](/img/icon_warning.svg)
![Warning icon](/img/icons/icon_warning.svg)
**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
@ -586,7 +591,7 @@ 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 icon](/img/icon_warning.svg)
![Warning icon](/img/icons/icon_warning.svg)
**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
@ -973,7 +978,7 @@ redeem script.
The P2SH address is returned along with the redeem script which must be
provided when we spend satoshis sent to the P2SH address.
![Warning icon](/img/icon_warning.svg)
![Warning icon](/img/icons/icon_warning.svg)
**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 bitcoins sent
@ -1124,7 +1129,7 @@ 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.
![Warning icon](/img/icon_warning.svg)
![Warning icon](/img/icons/icon_warning.svg)
**Reminder:** Users should never manually manage private keys on
mainnet. See the warning in the [complex raw transaction section][devex
complex raw transaction].