Author: ZmnSCPxj 2021-02-20 02:55:16
Published on: 2021-02-20T02:55:16+00:00
The discussion about the practicality of a LOT=false option for Bitcoin Core has been deemed moot due to software complexity. However, it can be worked around by running two clients, an "external" client running an LOT=X and an "internal" client that is at most 0.21.0, which will not impose any LOT rules. The internal client then uses `connect=` directive to connect locally to the external client and connects only to that client, using it as a firewall. The user can select LOT=C or LOT=!C on the external client based on their preferences. If Taproot is not MASF-activated and LOT=!U is what dominates later, the user can destroy the external node and connect the internal node directly to the network as a way to "change their mind in view of the economy". Bitcoin Core's policy is not to ship options that shoot users in the foot, and shipping a separate chain with its own datadir is the only practical way to implement such an option. While some developers may disapprove of LOT=false, Bitcoin Core maintainers and developers recommend courses of action they believe have reasonable levels of consensus and are technically sound. It is up to users to decide whether or not to run such software themselves.
Updated on: 2023-06-14T18:02:10.333755+00:00