In the past we had situations where a user made a deposit that did not get saved to the deposits table (but did have the associated data saved in the reveals table) and as a result was not passed to the tbtc bridge for further processing.
As tbtc bridge allows for revealing the deposits only for some specific time since depositing, if we solely relied on users support tickets, we may have missed the window for revealing, if user did not notify us about the problem in time...
That's why in the past we've been periodically running a script that tries to reveal all deposits from reveals from a certain time period (see https://coda.io/d/Acre_d3Vs1FswTQA/Handling-missing-deposits_sulaUZZB#_luER7vyT for the details).
As this is something that we need to remember about, it would be good to automate it.
linear[bot]
commented
2 hours ago
In the past we had situations where a user made a deposit that did not get saved to the
depositstable (but did have the associated data saved in therevealstable) and as a result was not passed to the tbtc bridge for further processing. As tbtc bridge allows for revealing the deposits only for some specific time since depositing, if we solely relied on users support tickets, we may have missed the window for revealing, if user did not notify us about the problem in time... That's why in the past we've been periodically running a script that tries to reveal all deposits fromrevealsfrom a certain time period (see https://coda.io/d/Acre_d3Vs1FswTQA/Handling-missing-deposits_sulaUZZB#_luER7vyT for the details). As this is something that we need to remember about, it would be good to automate it.