Author: Jorge Timón 2021-02-22 16:48:55
Published on: 2021-02-22T16:48:55+00:00
In a recent email exchange on the bitcoin-dev mailing list, Jorge Timón proposed a solution to avoid forks in the event of consensus changes. He suggested that those opposing the change could run a client where the "must" is turned into a "must not." This would prevent the activation of the change when miners signal it. By doing this, both sides of the community can remain on the same chain without causing any forks. Matt Corallo agreed with the idea but pointed out that there is still some technical complexity involved in making such a change. In another part of the conversation, Anthony Towns discussed the potential risks involved in a UASF-style command line option that allows consensus rule changes in the short term. Despite these concerns, the conversation remained focused on finding ways to avoid forks caused by consensus changes.
Updated on: 2023-06-14T17:58:52.761993+00:00