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

consider blocks with deposits in eth1 data vote #3944

Merged
merged 1 commit into from
Aug 9, 2022
Merged

Conversation

etan-status
Copy link
Contributor

When importing blocks with deposits from the EL, the timestamp is never
initialized for them. Therefore, only blocks without deposits (for which
the timestamp is obtained) are considered for is_candidate_block.
This is fixed by also importing timestamps for blocks with deposits.

When importing blocks with deposits from the EL, the timestamp is never
initialized for them. Therefore, only blocks without deposits (for which
the timestamp is obtained) are considered for `is_candidate_block`.
This is fixed by also importing timestamps for blocks with deposits.
@github-actions
Copy link

github-actions bot commented Aug 9, 2022

Unit Test Results

       12 files  ±0       860 suites  ±0   1h 13m 46s ⏱️ + 11m 24s
  1 911 tests ±0    1 764 ✔️ ±0  147 💤 ±0  0 ±0 
10 341 runs  ±0  10 151 ✔️ ±0  190 💤 ±0  0 ±0 

Results for commit edde6b1. ± Comparison against base commit 06a5c67.

@zah zah merged commit ede83b1 into unstable Aug 9, 2022
@zah zah deleted the dev/etan/el-timestamp branch August 9, 2022 22:14
zah added a commit that referenced this pull request Aug 9, 2022
#3944

The use of nested `awaitWithRetries` calls would have
resulted in an unexpected number of retries (3x3).
We now use regular `await` in outer layer to avoid the problem.

#3943

The new code has an invariant that the `headMerkleizer` field in
the `Eth1Chain` is always kept in sync with the blocks stored in
the chain.

This invariant is now enforced better by doing the necessary merkleizer
updates in the `Eth1Chain.addBlock` function.
@zah zah mentioned this pull request Aug 9, 2022
zah added a commit that referenced this pull request Aug 10, 2022
#3944

The use of nested `awaitWithRetries` calls would have
resulted in an unexpected number of retries (3x3).
We now use regular `await` in outer layer to avoid the problem.

#3943

The new code has an invariant that the `headMerkleizer` field in
the `Eth1Chain` is always kept in sync with the blocks stored in
the chain.

This invariant is now enforced better by doing the necessary merkleizer updates
in the `Eth1Chain.addBlock` function, in the `Eth1Chain.init` function and in the
`Eth1Chain.reset` function.
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.

None yet

2 participants