diff --git a/_includes/example_transactions.md b/_includes/example_transactions.md index 2e4387ad..55715a28 100644 --- a/_includes/example_transactions.md +++ b/_includes/example_transactions.md @@ -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]. diff --git a/_includes/guide_payment_processing.md b/_includes/guide_payment_processing.md index 76799350..bed0ced0 100644 --- a/_includes/guide_payment_processing.md +++ b/_includes/guide_payment_processing.md @@ -116,7 +116,8 @@ payment requests is recommended. increased security, authentication of a receiver's identity using X.509 certificates, and other important features such as refunds. -**Warning:** special care must be taken to avoid the theft of incoming +![Warning icon](/img/icon_warning.svg) + **Warning:** Special care must be taken to avoid the theft of incoming payments. In particular, private keys should not be stored on web servers, and payment requests should be sent over HTTPS or other secure methods to prevent man-in-the-middle attacks from replacing your Bitcoin address diff --git a/_includes/guide_wallets.md b/_includes/guide_wallets.md index 74de211d..0abd6916 100644 --- a/_includes/guide_wallets.md +++ b/_includes/guide_wallets.md @@ -444,9 +444,10 @@ as 128 bits is the the only data the user needs to backup in order to derive every key created by a particular wallet program using particular settings. -(**Warning:** as of this writing, HD wallet programs are not expected to +![Warning icon](/img/icon_warning.svg) + **Warning:** As of this writing, HD wallet programs are not expected to be fully compatible, so users must only use the same HD wallet program -with the same HD-related settings for a particular root seed.) +with the same HD-related settings for a particular root seed. The root seed is hashed to create 512 bits of seemingly-random data, from which the master private key and master chain code are created diff --git a/img/icon_warning.png b/img/icon_warning.png new file mode 100644 index 00000000..ff25a453 Binary files /dev/null and b/img/icon_warning.png differ diff --git a/img/icon_warning.svg b/img/icon_warning.svg new file mode 100644 index 00000000..50d8336b --- /dev/null +++ b/img/icon_warning.svg @@ -0,0 +1,74 @@ + + + + + + + + + + image/svg+xml + + + + + + + + + + + +