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
Our current implementation of mempool doesn't has rollback capability, since there is no block_height field in it to reference. We'll need to implement rollback to mempool to avoid strange behaviour in the system.
case:
- client post tx -> got into mempool, spendable got decreased
- rollback happen, and mempool is still considered valid, but new account_balance.spendable has not been decreased yet, because the new last block does not recognized that new tx
- when block got pushed (tx got applied) it undo the unconfirmed action (a.k.a add money to spendable) this cause spendable balance > balance.
Breakdown
Mempool BlockHeight
Rollback and save into KV
Additional Diagram / File
Put additional diagram or file
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Description
Our current implementation of mempool doesn't has rollback capability, since there is no
block_height
field in it to reference. We'll need to implement rollback to mempool to avoid strange behaviour in the system.case:
Breakdown
Additional Diagram / File
Put additional diagram or file
The text was updated successfully, but these errors were encountered: