Skip to content
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

Next step after fixing misconception in ForkedChain #2950

Open
jangko opened this issue Dec 18, 2024 · 0 comments
Open

Next step after fixing misconception in ForkedChain #2950

jangko opened this issue Dec 18, 2024 · 0 comments
Labels
EL enhancement New feature or request

Comments

@jangko
Copy link
Contributor

jangko commented Dec 18, 2024

after we fix #2949

the next step after that is going to be to add to BlockDesc a layer or blockT field that holds the state associated with having applied that block - any time a fork is created, instead of replaying via stagingTx, this field will be used instead as a starting point - I've mentioned a few other, more efficient designs in the past, but this is the most simple one that gets us over the finish line

@jangko jangko added EL enhancement New feature or request labels Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
EL enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant