chore: bump public submodule for flare validate-peers fix#235
Merged
Conversation
a10zn8
approved these changes
Jun 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the
pkg/chains/publicsubmoduleded5267→9cd162d, pulling in drpcorg/public#234. This is the only commit the bump brings in.That PR adds
validate-peers: falseto theflarechain settings. Flare runs go-flare (Avalanche/coreth), whose C-chain EVM RPC always returnsnet_peerCount: 0x0because peering happens at the Avalanche P2P layer. With peer validation on, bothflareandflare-testnetupstreams are permanently reported asIMMATUREdespite being fully bootstrapped and synced.avalancheandkite(also Avalanche C-chains) already carry this option;flarewas missed.No code change — submodule pointer only.