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

sync recent miner/ccc changes #1062

Merged
merged 5 commits into from
Oct 10, 2024

Conversation

@0xmountaintop 0xmountaintop changed the title SyncUpstream/less-state-access sync recent miner/ccc changes Oct 10, 2024
@0xmountaintop 0xmountaintop force-pushed the syncUpstream/less-state-access branch 2 times, most recently from a16e490 to d3b712c Compare October 10, 2024 03:10
@0xmountaintop 0xmountaintop force-pushed the syncUpstream/less-state-access branch from d3b712c to 231b2ef Compare October 10, 2024 03:12
we assume that same height wont trigger multiple reorgs to be able
to put an upper bound on the reorg depth. We rely on the fact that
AsyncChecker executes transactions one-by-one and tells worker the
safe set of transactions to include in the replacement block that
wont trigger another error on the same block. If worker changes the
timestamp and that causes significant changes to the execution flow
of included transactions; we might have a height where multiple
reorgs happen.
@0xmountaintop 0xmountaintop merged commit 3d88e87 into syncUpstream/active Oct 10, 2024
3 of 4 checks passed
@0xmountaintop 0xmountaintop deleted the syncUpstream/less-state-access branch October 10, 2024 06:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants