You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per #beta-net discussion on Discord, it seems like some nodes might be trying to bootstrap forked blocks. Is it possible to only bootstrap cemented blocks? Seems like an easy win for both less bandwidth usage and improved fork resolution (fewer repeat forks), but I'm not sure sure if this has any hidden implications or difficult implementation issues.
The text was updated successfully, but these errors were encountered:
@zhyatt - Is this solved by the linked PRs? #3152 (replacing #3047). Not sure if "optionally send confirmed frontiers" is the same as "only send confirmed frontiers for bootstrap"
@zhyatt - Is this solved by the linked PRs? #3152 (replacing #3047). Not sure if "optionally send confirmed frontiers" is the same as "only send confirmed frontiers for bootstrap"
@qwahzi PR #3152 only implements the option to ask for confirmed blocks only on bootstrap, but does not set that as the default. It is mostly a debug option at this point. Although I don't recall the specific issues with bootstrapping on confirmed blocks, there are some considerations which may not allow this to be fully implemented. It needs further research so I have added it to the milestone for that.
Per #beta-net discussion on Discord, it seems like some nodes might be trying to bootstrap forked blocks. Is it possible to only bootstrap cemented blocks? Seems like an easy win for both less bandwidth usage and improved fork resolution (fewer repeat forks), but I'm not sure sure if this has any hidden implications or difficult implementation issues.
The text was updated successfully, but these errors were encountered: