<p>If there’s a case of a majority hashrate, human intervention of a single instance can not prevent something that continuous and ongoing. The amount of coordination required to keep the network in consensus would be impossible to obtain if this were a solution. </p>

<p>If Bitcoin fails, it’s time to move on rather than patching it up. </p>

CC BY-SA 4.0
2020-03-07T00:50:41.180Z
2020-03-07T00:50:41.180Z
Claris
<p>there is a 'invalidateblock' debugging command in the btc client. How can this command be used in a situation of majority attack threat and play a part of countering the attack? </p>

<p>I understand that this command lets nodes 'ignore' blocks generated by the attacking miners. But is that it? What happens with the blockchain, how can it continue to live on without the majority attackers?</p>

<bitcoin-core><client><bitcoin-core-development><majority-attack><invalidateblock>
the client's 'invalidateblock' debugging command - possible prevention against majority attack?
johnsmiththelird
# the client's 'invalidateblock' debugging command - possible prevention against majority attack?

(Asked by: username_0 on 2020-03-06)

there is a 'invalidateblock' debugging command in the btc client. How can this command be used in a situation of majority attack threat and play a part of countering the attack?

I understand that this command lets nodes 'ignore' blocks generated by the attacking miners. But is that it? What happens with the blockchain, how can it continue to live on without the majority attackers?

**Tags:** bitcoin-core, client, bitcoin-core-development, majority-attack, invalidateblock


---

## 1 answers

### Answer by username_1 on 2020-03-07. Score: 1

If there’s a case of a majority hashrate, human intervention of a single instance can not prevent something that continuous and ongoing. The amount of coordination required to keep the network in consensus would be impossible to obtain if this were a solution.

If Bitcoin fails, it’s time to move on rather than patching it up.


---

