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

Beacon sync revisting fc automove base #2961

Closed
wants to merge 3 commits into from

Conversation

mjfh
Copy link
Contributor

@mjfh mjfh commented Dec 19, 2024

This is a proof of concept for the beacon syncer running without knowledge of a finalised header.

The FC module part using a modified importBlock() function has been adapted from PR #2845 (fc-automove-base).

The automatic finaliser part of importBlock() needs to be double checked for compliance. But it will be invalidated anyway by the upcoming PR #2960 (forked-layers) and so needs to be rewritten.

The beacon sync part of this PR works well and there should be no functionality updates necessary regarding the usage of the modified importBlock() function.

mjfh added 3 commits January 13, 2025 10:15
details:
  This is basically a tweaked version of Andri's function
  `importBlockBlindly()` from the draft PR mentioned above.
why:
  Not needed anymore, `forkChoice()` as has been integrated into
  `importBlock()`.
@mjfh mjfh force-pushed the Beacon-sync-revisting-fc-automove-base branch from 23e1bbb to c9667f8 Compare January 13, 2025 11:21
@mjfh mjfh closed this Jan 13, 2025
@mjfh mjfh deleted the Beacon-sync-revisting-fc-automove-base branch January 13, 2025 11:26
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.

1 participant