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

Update used bootstrap as they become available + require trusted-block-root only at first start-up #2213

Open
kdeme opened this issue May 23, 2024 · 0 comments

Comments

@kdeme
Copy link
Contributor

kdeme commented May 23, 2024

Currently when we start a fluffy node and want to enable the Portal beacon network, we need to provide a trusted-block-root and always start from that one.

We should make following changes which would highly improve the UX:

  • Require to provide trusted-block-root only on first start
  • Or require to provide trusted-block-root when last stored bootstrap is not is_within_weak_subjectivity_period. (perhaps with potential overwrite flag on this)
  • When a fluffy node is consensus light client synced, update the actually bootstrap starting point each time to the last received bootstrap.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant