|
|
|
@ -1568,7 +1568,7 @@ majority of the mining power.
|
|
|
|
|
//TODO: update to not use 51% attack name (see other TODO in this
|
|
|
|
|
//chapter)
|
|
|
|
|
|
|
|
|
|
Despite its name, the 51% attack scenario doesn't actually require 51%
|
|
|
|
|
Despite its ((("majority attacks", startref="majority-attack")))((("51% attacks", startref="attack-51")))((("double-spend attacks", startref="double-spend")))name, the 51% attack scenario doesn't actually require 51%
|
|
|
|
|
of the hashing power. In fact, such an attack can be attempted with a
|
|
|
|
|
smaller percentage of the hashing power. The 51% threshold is simply the
|
|
|
|
|
level at which such an attack is almost guaranteed to succeed. A
|
|
|
|
@ -1607,7 +1607,7 @@ Undoubtedly, a serious hashrate attack would erode confidence in
|
|
|
|
|
Bitcoin in the short term, possibly causing a significant price decline.
|
|
|
|
|
However, the Bitcoin network and software are constantly evolving, so
|
|
|
|
|
attacks would be met with countermeasures by the
|
|
|
|
|
Bitcoin ((("decentralized consensus", "hashrate attacks", startref="decentral-consensus-hashrate")))((("bitcoins", "mining", "hashrate attacks", startref="bitcoin-mining-hashrate")))((("mining", "hashrate attacks", startref="mining-hashrate")))((("hashrate attacks", startref="hashrate")))((("forks", "hashrate attacks", startref="fork-hashrate")))((("majority attacks", startref="majority-attack")))((("51% attacks", startref="attack-51")))((("double-spend attacks", startref="double-spend")))community.
|
|
|
|
|
Bitcoin ((("decentralized consensus", "hashrate attacks", startref="decentral-consensus-hashrate")))((("bitcoins", "mining", "hashrate attacks", startref="bitcoin-mining-hashrate")))((("mining", "hashrate attacks", startref="mining-hashrate")))((("hashrate attacks", startref="hashrate")))((("forks", "hashrate attacks", startref="fork-hashrate")))community.
|
|
|
|
|
|
|
|
|
|
[[consensus_changes]]
|
|
|
|
|
=== Changing the Consensus Rules
|
|
|
|
|