I think the "temporary" nature of #BIP110 is actually it's what leads to the reasoning of nostr:nprofile1qyxhwumn8ghj7mn0wvhxcmmvqyv8wumn8ghj7urjv4kkjatd9ec8y6tdv9kzumn9wsqzqpxfzhdwlm3cx9l6wdzyft8w8y9...
The temporary aproach of BIP 110 is very humble and smart approach. It gives us the opportunity to analyze the BIP, it gives us time to consider all different use cases and if something can be improved - improve it and the make it permament.
There is no risk for BIP 110 being temporary because it is a soft fork.
To understand this you need the definition of the soft and hard fork which I will paste at then end.
The idea is to think in terms of the nodes versions.
Soft fork narrows the consensus rules for a block meaning they are accepted under current consensus rules meaning all older versions of nodes accept them.
If BIP 110 activates all blocks will be with tighter rules - accepted by all node versions. When it expires rules get back to what they were and all nodes again accept all blocks. I hope that helps. I am running BIP 110 too.
Soft Fork
A soft fork is a backward-compatible upgrade or change to the rules of a blockchain protocol. In a soft fork:
Compatibility: Nodes that do not upgrade to the new version can still participate in the network and form valid blocks. This is because the new rules are a subset of the old rules.
Examples: Soft forks can be used to introduce new features or improve functionalities without requiring all participants to update their software immediately.
Scenario: If a new rule is implemented that allows for a smaller block size, older nodes will still accept blocks that comply with the original size.
Hard Fork
A hard fork is a significant change to a blockchain protocol that is not backward-compatible. In a hard fork:
Incompatibility: Nodes that do not upgrade to the new version will be unable to validate or participate in the updated blockchain, leading to a divergence.
Example: A hard fork can be used to implement radical changes or introduce new features that completely alter the blockchain rules.
Scenario: If a new rule is created that changes the consensus mechanism, nodes that do not upgrade will fall behind on the new blockchain, resulting in two separate chains.
There is no risk for BIP 110 being temporary because it is a soft fork.
To understand this you need the definition of the soft and hard fork which I will paste at then end.
The idea is to think in terms of the nodes versions.
Soft fork narrows the consensus rules for a block meaning they are accepted under current consensus rules meaning all older versions of nodes accept them.
If BIP 110 activates all blocks will be with tighter rules - accepted by all node versions. When it expires rules get back to what they were and all nodes again accept all blocks. I hope that helps. I am running BIP 110 too.
Soft Fork
A soft fork is a backward-compatible upgrade or change to the rules of a blockchain protocol. In a soft fork:
Compatibility: Nodes that do not upgrade to the new version can still participate in the network and form valid blocks. This is because the new rules are a subset of the old rules.
Examples: Soft forks can be used to introduce new features or improve functionalities without requiring all participants to update their software immediately.
Scenario: If a new rule is implemented that allows for a smaller block size, older nodes will still accept blocks that comply with the original size.
Hard Fork
A hard fork is a significant change to a blockchain protocol that is not backward-compatible. In a hard fork:
Incompatibility: Nodes that do not upgrade to the new version will be unable to validate or participate in the updated blockchain, leading to a divergence.
Example: A hard fork can be used to implement radical changes or introduce new features that completely alter the blockchain rules.
Scenario: If a new rule is created that changes the consensus mechanism, nodes that do not upgrade will fall behind on the new blockchain, resulting in two separate chains.
3❤️1🤙1