From 445da880a83f074ef83a6906a8096400aee19c46 Mon Sep 17 00:00:00 2001 From: clenser Date: Tue, 17 Oct 2023 22:17:41 +0000 Subject: [PATCH] Edited ch12_mining.adoc with Atlas code editor --- ch12_mining.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ch12_mining.adoc b/ch12_mining.adoc index 21344025..f719dbff 100644 --- a/ch12_mining.adoc +++ b/ch12_mining.adoc @@ -1416,7 +1416,7 @@ using their own full ((("managed pools", startref="manage-pool")))node. ===== Peer-to-peer mining pool (P2Pool) -Managed pools using Stratum v1 create the possibility of cheating by +Managed pools ((("P2Pool (peer-to-peer mining pool)", id="p2pool")))using Stratum v1 create the possibility of cheating by the pool operator, who might direct the pool effort to double-spend transactions or invalidate blocks (see <>). Furthermore, centralized pool servers represent a @@ -1461,7 +1461,7 @@ attack problem for Bitcoin itself. Rather, P2Pool makes Bitcoin more robust overall, as part of a diversified mining ecosystem. As of this writing, P2Pool has fallen into disuse, but new protocols such as Stratum v2 can allow individual miners to choose the transactions they -include in their((("bitcoins", "mining", "competitiveness of", startref="bitcoin-mining-competition")))((("mining", "competitiveness of", startref="mining-competitive")))((("bitcoins", "mining", "mining pools", startref="bitcoin-mining-pools")))((("mining", "mining pools", startref="mining-mining-pools")))((("mining pools", startref="mining-pools"))) blocks. +include in their((("bitcoins", "mining", "competitiveness of", startref="bitcoin-mining-competition")))((("mining", "competitiveness of", startref="mining-competitive")))((("bitcoins", "mining", "mining pools", startref="bitcoin-mining-pools")))((("mining", "mining pools", startref="mining-mining-pools")))((("mining pools", startref="mining-pools")))((("P2Pool (peer-to-peer mining pool)", startref="p2pool"))) blocks. [[consensus_attacks]] === Hashrate Attacks