You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are reported cases (#8028) where a noderunner had invalid values in his height hint cache leading to lnd not recognizing already spent outputs as spent. Using the config setting --height-hint-cache-query-disable in lnd, these situation were resolved. Maybe the historical recan logic has a race condition where it misses a spend somehow which eventually updates the height hint cache and therefore never recovering the monitored outputs because the height hint cache will be queried for any other historical rescan if we do not actively disable it.
I was not able to reproduce this issue so far.
The text was updated successfully, but these errors were encountered:
Yes the case I referenced had this setting on (rpcserialversion=0), but I am not sure how this could impact the monitoring because we are checking for outputs only ? Moreover after he set the --height-hint-cache-query-disable the historical rescan did work and lead to the situation where the preimage witness check happend (leading us to his problem of the rpcserialversion setting).
There are reported cases (#8028) where a noderunner had invalid values in his height hint cache leading to lnd not recognizing already spent outputs as spent. Using the config setting
--height-hint-cache-query-disable
in lnd, these situation were resolved. Maybe the historical recan logic has a race condition where it misses a spend somehow which eventually updates the height hint cache and therefore never recovering the monitored outputs because the height hint cache will be queried for any other historical rescan if we do not actively disable it.I was not able to reproduce this issue so far.
The text was updated successfully, but these errors were encountered: