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

bug: fee estimation don't have foresight #10261

Closed
LHerskind opened this issue Nov 27, 2024 · 0 comments · Fixed by #10262
Closed

bug: fee estimation don't have foresight #10261

LHerskind opened this issue Nov 27, 2024 · 0 comments · Fixed by #10262
Assignees

Comments

@LHerskind
Copy link
Contributor

The fee estimation used for building the block is not looking into the future (the classic), so it would have issues around boundaries leading to skipped slots, but for a prune, it could cause a case where the "next" block keep being estimated using the non-pruned chain meaning that it would keep being rejected.

We can update this like we have done other times, by passing along a timestamp for the estimation function such that we can estimate for the future, and then taking into account the prune.

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 a pull request may close this issue.

1 participant