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

eth1 deposit tracker cache populate flawed in slow networks #4109

Closed
dapplion opened this issue Jun 3, 2022 · 0 comments · Fixed by #4111
Closed

eth1 deposit tracker cache populate flawed in slow networks #4109

dapplion opened this issue Jun 3, 2022 · 0 comments · Fixed by #4111
Labels
prio-critical Drop everything to resolve this immediately. Examples: consensus bug, un-usable CLI

Comments

@dapplion
Copy link
Contributor

dapplion commented Jun 3, 2022

Describe the bug

Ropsten is having very long block times. Our eth1 deposit tracker assumes constant times of 14 seconds, and doesn't populate the blocks necessary latter for block production.

DB cache has
blocks here
=========|      we are querying blocks here
    |    |    |xxxx|    |
day 0    1    2    3   now

Expected behavior

When computing which block to download too, it should be computed based on timestamp, not blockNumber. This way to cache will be populated up to where it's needed

@dapplion dapplion added the prio-critical Drop everything to resolve this immediately. Examples: consensus bug, un-usable CLI label Jun 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
prio-critical Drop everything to resolve this immediately. Examples: consensus bug, un-usable CLI
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant