-
Notifications
You must be signed in to change notification settings - Fork 270
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
refactor!: remove v0 mempool #1388
base: main
Are you sure you want to change the base?
Conversation
Hmm I want this to only be apart of v3. Which might be okay since v0.34.x is the branch for v1 and v2. I would ideally like to be sure of our v3 release strategy i.e. will v3 have a v2 of celestia-core. Will we diverge from cometbft in our release naming because we already released a v1, will this be compatible with the SDK and our ambitions of no longer needing a fork etc... In any case it's probably fine to still go ahead and deprecate this. I just want to give ample time to double check. We should be in no rush to have to remove v0 |
should i convert this into a draft? |
we just need to avoid backporting it, and can keep all of our changes for v3 in main |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should i convert this into a draft?
IMO yes. I personally haven't been convinced that we should deprecate and remove the v0 mempool. Is there anything I can read about how difficult it is to maintain?
my understanding is that we just wanted to save some time implementing bestTx things multiple times, and no one is using the v0 mempool. This is a good point though. When we look upstream, we see that they exclusively use v0, so this might make backporting certain test require further changes. |
Description
Fixes #1387