joshua/dash-docs
1
0
Fork 0
mirror of https://github.com/seigler/dash-docs synced 2025-07-28 02:06:13 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Apply a warning icon to all warning texts in devel-docs

Browse source
This commit is contained in:
Saivann 2014-06-10 23:49:39 -04:00
parent 1db4eb4031
commit 21bdb0fd1a
5 changed files with 89 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

15
_includes/example_transactions.md
View file

@ -279,7 +279,8 @@ 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
![Warning icon](/img/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
(`$NEW_ADDRESS`) is being paid 49.9999 bitcoins, so the transaction will
@ -486,7 +487,8 @@ 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.
![Warning icon](/img/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
wallet [cross-generational key compromise][devguide hardened keys].
@ -642,7 +644,8 @@ 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
![Warning icon](/img/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
unconfirmed transactions on mainnet.
@ -1028,7 +1031,8 @@ 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
![Warning icon](/img/icon_warning.svg)
**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
@ -1178,7 +1182,8 @@ 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.
**Reminder:** Users should never manually manage private keys on
![Warning icon](/img/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].