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 think we can only be sure it's Deprecated once the pending tx has been confirmed. Otherwise, we would have to try broadcasting it to see whether it can replace the pending tx or not.
Perhaps we could indicate that it conflicts with the pending tx and so the user knows it might not be possible to broadcast.
We don't currently keep track of replacements in the DB so I don't think there's an easy way for the GUI to know if one transaction has replaced another in the mempool.
Before the cancel tx is mined
after the cancel tx mined:
shouldn't the canceled tx already appear deprecated before the cancel tx mined as the canceled tx not anymore in mempool?
The text was updated successfully, but these errors were encountered: