<p>If you alter the consensus rules in the software running your node, there are two options:</p>

<ul>
<li><p>You apply rules less restrict than before, accepting some transactions that were previously invalid: every block you mine will be displaced by blocks from longer chains mined by the miners that didn't change anything and have more hashpower than you. Because they'll never accept your blocks but you're still accepting theirs.</p></li>
<li><p>You apply rules more restrict than before, rejecting some transactions that were previously valid: you are on your own, and will have to mine every single block. Depending on your current hashpower, it could take weeks until the next one. Unless you also change the rules concerning minimum difficulty. But the blocks you mine still will be accepted only by your node.</p></li>
</ul>

CC BY-SA 3.0
2018-03-19T03:04:35.670Z
2018-03-19T03:04:35.670Z
Osias Jota
<blockquote>
<p>Is it possible for someone to change the consensus rules for his own software and then remain in the previous network?</p>
</blockquote>
<p>It is theoretically possible to do this and still remain on the previous network especially if you are imposing an additional restriction (an effective soft fork) rather than a relaxation (an effective hard fork). However I would strongly recommend against doing so on mainnet if any funds with real world monetary value are at stake. The reason for this is even with soft forks you can be forked off the network following a different blockchain if you reject a block due to a transaction in this block not meeting your additional restriction. An example of this was demonstrated prior to the Taproot soft fork when there was one user running a full node who claimed to have been forked off the network for applying the Taproot rules too early when 0xB10C <a href="https://b10c.me/blog/007-spending-p2tr-pre-activation/" rel="nofollow noreferrer">spent</a> an anyone-can-spend Pay-to-Taproot output prior to activation.</p>
<p>When it comes to consensus rules the punishment for diverging from the rules being enforced by the rest of the network is significant. You risk being forked off the network, following a different blockchain and verifying transactions and blocks that aren't representing the actual Bitcoin blockchain (effectively a different currency or asset). So by all means experiment on testnet, signet with different consensus rules but when verifying mainnet transactions and blocks do not do this.</p>

CC BY-SA 4.0
2022-08-07T13:48:38.647Z
2022-08-07T13:48:38.647Z
Michael Folkson
<p>How nodes agree to consensus rules? Is it possible for someone to change the consensus rules for his own software and then remain in the previous network? If not, then why?</p>

<blockchain-fork><consensus><soft-fork>
Altering Consensus Rules
Monmoy Sarker
# Altering Consensus Rules

(Asked by: username_0 on 2018-03-19)

How nodes agree to consensus rules? Is it possible for someone to change the consensus rules for his own software and then remain in the previous network? If not, then why?

**Tags:** blockchain-fork, consensus, soft-fork


---

## 2 answers

### Answer by username_1 on 2018-03-19. Score: 1

If you alter the consensus rules in the software running your node, there are two options:

* You apply rules less restrict than before, accepting some transactions that were previously invalid: every block you mine will be displaced by blocks from longer chains mined by the miners that didn't change anything and have more hashpower than you. Because they'll never accept your blocks but you're still accepting theirs.
* You apply rules more restrict than before, rejecting some transactions that were previously valid: you are on your own, and will have to mine every single block. Depending on your current hashpower, it could take weeks until the next one. Unless you also change the rules concerning minimum difficulty. But the blocks you mine still will be accepted only by your node.


---

### Answer by username_2 on 2022-08-07. Score: 0

> Is it possible for someone to change the consensus rules for his own software and then remain in the previous network?

It is theoretically possible to do this and still remain on the previous network especially if you are imposing an additional restriction (an effective soft fork) rather than a relaxation (an effective hard fork). However I would strongly recommend against doing so on mainnet if any funds with real world monetary value are at stake. The reason for this is even with soft forks you can be forked off the network following a different blockchain if you reject a block due to a transaction in this block not meeting your additional restriction. An example of this was demonstrated prior to the Taproot soft fork when there was one user running a full node who claimed to have been forked off the network for applying the Taproot rules too early when 0xB10C [spent](https://b10c.me/blog/007-spending-p2tr-pre-activation/) an anyone-can-spend Pay-to-Taproot output prior to activation.

When it comes to consensus rules the punishment for diverging from the rules being enforced by the rest of the network is significant. You risk being forked off the network, following a different blockchain and verifying transactions and blocks that aren't representing the actual Bitcoin blockchain (effectively a different currency or asset). So by all means experiment on testnet, signet with different consensus rules but when verifying mainnet transactions and blocks do not do this.


---

