-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE]: Fork aware mempool
#79
Labels
Comments
sgerbino
added a commit
that referenced
this issue
Dec 12, 2022
sgerbino
added a commit
that referenced
this issue
Dec 13, 2022
sgerbino
added a commit
that referenced
this issue
Dec 13, 2022
sgerbino
added a commit
that referenced
this issue
Dec 13, 2022
sgerbino
added a commit
that referenced
this issue
Dec 13, 2022
1 task
sgerbino
added a commit
that referenced
this issue
Dec 13, 2022
sgerbino
added a commit
that referenced
this issue
Dec 13, 2022
sgerbino
added a commit
that referenced
this issue
Dec 13, 2022
sgerbino
added a commit
that referenced
this issue
Dec 13, 2022
… loss of any known transaction, updated test to reflect this
sgerbino
added a commit
that referenced
this issue
Dec 13, 2022
sgerbino
added a commit
that referenced
this issue
Dec 14, 2022
sgerbino
added a commit
that referenced
this issue
Dec 14, 2022
sgerbino
added a commit
that referenced
this issue
Dec 14, 2022
sgerbino
added a commit
that referenced
this issue
Dec 14, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
New feature
As a Koinos user, I would like a fork aware
mempool
such that transactions do not get forgotten on forks.statedb
so thatroot
can be backed by astd::map
koinos-state-db-cpp#9statedb
and replicate the workflow inaccount_history
#81add_pending_transaction
to add transactions to each fork head #82mempool
on a particular fork -- default to the known head block koinos-proto#192mempool
irreversibility up #85Note: Upon startup, the
statedb
root should be genesis (0x00
). If transactions come in prior to a LIB, apply the transactions directly to the genesis node. When LIB comes in, attempt to attach it toprevious
, if there is no previous attempt to attach the node to genesis. If there is no genesis, report an error because something went wrong.Anything else?
Right now it is possible for a transaction to end up on a fork, the cluster makes no attempt to re-apply this transaction on the main fork. This will cause bad UX for both users.
The text was updated successfully, but these errors were encountered: