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
I created a transaction with label, few days later that label is not there :(
I don't know how exactly it happened. The transaction was unconfirmed for more then week, it contained only one input and one output and meanwhile I recieved and sent other transactions from this and other wallets in sparrow. Sorry that I don't hove more concrete steps how to reproduce this.
The text was updated successfully, but these errors were encountered:
My guess is that the node you were connected to purged the transaction from it's mempool during the recent period of high congestion. This may have removed it from Sparrow too, and then when the congestion decreased the transaction was propagated again from nodes with a higher mempool limit. Sparrow would then have picked it up again sans the label.
There's a good argument to say that Sparrow should never drop transactions (once broadcast they are in effect permanent) but there is a reality of buggy server implementations and bad connections to consider as well. If Sparrow cannot remove transactions it cannot fix these issues.
The alternative is to store labels in some other place. I'll look into this.
I created a transaction with label, few days later that label is not there :(
I don't know how exactly it happened. The transaction was unconfirmed for more then week, it contained only one input and one output and meanwhile I recieved and sent other transactions from this and other wallets in sparrow. Sorry that I don't hove more concrete steps how to reproduce this.
The text was updated successfully, but these errors were encountered: