Change Details

Enabling pruning by default on the intro screen, when the selected data directory does not have enough disk space available to store the entire blockchain, can cause accidental pruning. When the filesystem containing the data is not mounted when bitcoin-qt is started, the intro screen is shown with the usual data directory selected and the pruning option checked. If the file system is then mounted (e.g. external hard drive connected) and the user does not notice that pruning is selected, the blockchain is pruned after he clicks OK. See also https://github.com/bitcoin/bitcoin/issues/19291 This commit removes default pruning behavior introduced in D7956, not matter how much disk space is detected on the selected filesystem. Pruning can always be activated later if needed, from the menu.

Enabling pruning by default on the intro screen, when the selected data directory does not have enough disk space available to store the entire blockchain, can cause accidental pruning. When the filesystem containing the data is not mounted when bitcoin-qt is started, the intro screen is shown with the usual data directory selected and the pruning option checked. If the file system is then mounted (e.g. external hard drive connected) and the user does not notice that pruning is selected, the blockchain is pruned after he clicks OK. See also https://github.com/bitcoin/bitcoin/issues/19291 Besides that, if a user selects pruning and then changes the data directory, it should not unselect the option. This commit removes default pruning behavior introduced in D7956, no matter how much disk space is detected on the selected filesystem. Pruning can always be activated later if needed, from the menu.

Enabling pruning by default on the intro screen, when the selected data directory does not have enough disk space available to store the entire blockchain, can cause accidental pruning. When the filesystem containing the data is not mounted when bitcoin-qt is started, the intro screen is shown with the usual data directory selected and the pruning option checked. If the file system is then mounted (e.g. external hard drive connected) and the user does not notice that pruning is selected, the blockchain is pruned after he clicks OK. See also https://github.com/bitcoin/bitcoin/issues/19291 See also https://github.com/bitcoin/bitcoin/issues/19291Besides that, if a user selects pruning and then changes the data directory, it should not unselect the option. This commit removes default pruning behavior introduced in D7956, not matter how much disk space is detected on the selected filesystem. Pruning can always be activated later if needed, from the menu.