opened
GlenDC
username_0
When reverting blocks, we go essentially back in time and block height. Meaning that an output that was unlocked, could be locked once again. This is for now not tracked however.

In practice this is probably an issue not very noticeable as we usually revert just in small jumps backwards, making it already that not all TimeLockedConditions outputs will suffer from this. Even if they do, it would just be for one or a couple of blocks, and thus not really noticeable. As the result the reporting is not 100% correct, but will correct itself quick enough and we know for sure the consensus module does check the rules correctly, so the later auto-correction is for sure trustworthy.

Still, it would be good that this auto-locking is done as well, so that the reporting becomes accurate at all times.
TimeLockConditioned outputs aren't locked again while reversing blocks
issue