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

Revert "Merge pull #793: Dev Docs: New Glossary & JS Search Box"

Browse source 
This reverts commit e3dcf0ce1f, reversing
changes made to c71e9fdf2d.

Once again we had a broken new plugin that Travis CI and local building
didn't catch.
This commit is contained in:
David A. Harding 2015-04-10 19:33:17 -04:00
parent e3dcf0ce1f
commit 961d6c988f
No known key found for this signature in database
GPG key ID: 4B29C30FF29EC4B7
126 changed files with 470 additions and 3827 deletions
Download patch file Download diff file Expand all files Collapse all files

12
_includes/guide_payment_processing.md
View file

@ -257,7 +257,7 @@ displayed on high-resolution screens.
{% autocrossref %}
Bitcoin Core 0.9 supports the new [payment protocol][/en/glossary/payment-protocol]{:#term-payment-protocol}{:.term}. The payment protocol
Bitcoin Core 0.9 supports the new [payment protocol][]{:#term-payment-protocol}{:.term}. The payment protocol
adds many important features to payment requests:
- Supports X.509 certificates and SSL encryption to verify receivers' identity
@ -423,7 +423,7 @@ for more details.
{% autocrossref %}
As explained in the [Transactions][] and [Block Chain][section block chain] sections, broadcasting
As explained in the [Transactions][] and [Block Chain][] sections, broadcasting
a transaction to the network doesn't ensure that the receiver gets
paid. A malicious spender can create one transaction that pays the
receiver and a second one that pays the same input back to himself. Only
@ -431,20 +431,20 @@ one of these transactions will be added to the block chain, and nobody
can say for sure which one it will be.
Two or more transactions spending the same input are commonly referred
to as a [double spend][/en/glossary/double-spend]{:#term-double-spend}{:.term}.
to as a [double spend][]{:#term-double-spend}{:.term}.
Once the transaction is included in a block, double spends are
impossible without modifying block chain history to replace the
transaction, which is quite difficult. Using this system,
the Bitcoin protocol can give each of your transactions an updating confidence
score based on the number of blocks which would need to be modified to replace
a transaction. For each block, the transaction gains one [confirmation][/en/glossary/confirmation-score]{:#term-confirmation}{:.term}. Since
a transaction. For each block, the transaction gains one [confirmation][]{:#term-confirmation}{:.term}. Since
modifying blocks is quite difficult, higher confirmation scores indicate
greater protection.
**0 confirmations**: The transaction has been broadcast but is still not
included in any block. Zero confirmation transactions (unconfirmed
transactions) should generally not be
included in any block. Zero confirmation transactions ([unconfirmed
transactions][]{:#term-unconfirmed-transactions}{:.term}) should generally not be
trusted without risk analysis. Although miners usually confirm the first
transaction they receive, fraudsters may be able to manipulate the
network into including their version of a transaction.