diff --git a/_includes/guide_payment_processing.md b/_includes/guide_payment_processing.md index 9ebce56b..76aa932a 100644 --- a/_includes/guide_payment_processing.md +++ b/_includes/guide_payment_processing.md @@ -488,7 +488,8 @@ estimate the amount of time until they're added to a block. Another example could be to detect a fork when multiple peers report differing block header hashes at the same block height. Your program can go into a safe mode if the fork extends for more than two blocks, indicating a possible problem with the -block chain. +block chain. For more details, see the [Detecting Forks +subsection][section detecting forks]. Another good source of double-spend protection can be human intelligence. For example, fraudsters may act differently from legitimate customers, letting diff --git a/_includes/references.md b/_includes/references.md index cb9faa75..73713547 100644 --- a/_includes/references.md +++ b/_includes/references.md @@ -292,6 +292,7 @@ [secp256k1]: http://perso.univ-rennes1.fr/sylvain.duquesne/master/standards/sec2_final.pdf [section verifying payment]: /en/developer-guide#verifying-payment +[section detecting forks]: /en/developer-guide#detecting-forks [bitcoin URI subsection]: /en/developer-guide#bitcoin-uri [SHA256]: https://en.wikipedia.org/wiki/SHA-2 [Stratum mining protocol]: http://mining.bitcoin.cz/stratum-mining