Sep 19, 2018

<higher prio topic coming below :)) >

@evoskuil no you're missing my point - it is the responsibility of a storage device (e.g. SSD) to keep its data store in integrity. Indeed it may not keep integrity. A filesystem (e.g. ZFS) may add a checksumming layer to storage device access, so that reads will fail if its underlying disk data was corrupted. In case of unexpected shutdowns in particular, self-validation to identify anything broken and rewind all affected, would make all sense - rather than for instance terminate and require administrator intervention which is LibBitcoin's current behavior. I agree that it not is reasonable for software behavior to be coherent if persistent storage breaks, just like it not is reasonable for software behavior to be coherent if RAM or CPU break. However, unexpected shutdowns happen, and also a user may like to run self-checking logics - in particular given the fiat cost of SSD wear for rewriting the whole blockchain, and the time it takes to resync the blockchain from scratch, some self-validation would make sense. I don't follow LibBitcoin's database models very well yet so I don't understand yet what degree of complexity they are. </higher prio topic coming below :)) >