sebak
sebak copied to clipboard
Make sure that pending transactions are not lost on restart
With MainNet around the corner, we will sometimes need to update sebak all nodes at once. We should make sure that nodes do not loose their pending txs on shutdown.
I think that we need a tx pool with WAL ( or to keep in file or persistend keep when add)
In the current scenario, the lost transactions could not be found thru /api/v1/transactions/{hash}, so the client fails to check, they will send it again. This feature will make sebak to be more stable.
Without persisted txs in the pool, Delayed txs is OK?
Delayed ops will have to be saved as well, but they were reverted so it's not a problem ATM.