36792

Error messages can also end up with the first half coming from an old error and the second half from a new one. Bitcoin Core Draft #36792 aims to clarify two validation paths: when a possibly corrupted block is detected, first record the original Invalid information, then replace it with a clear corruption error; when a disk flush has triggered a fatal error, preserve the original error afterward and avoid sending duplicate notifications. My view is that troubleshooting quality depends on whether an error points to the same failure; retaining more text does not always make things clearer. The original text also notes that one type of disk failure requires fault injection to test. This is an error-handling change pending review by the $BTC client; it should not be taken as evidence that a user's device has been found to be damaged.