[Bug Bounty] Limit number of provers we connect to #3090
Merged
Conversation
This file contains 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
ljedrz
reviewed
Feb 12, 2024
ljedrz
reviewed
Feb 12, 2024
howardwu
reviewed
Feb 14, 2024
Signed-off-by: Howard Wu <9260812+howardwu@users.noreply.github.com>
howardwu
approved these changes
Feb 14, 2024
howardwu
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivation
Partially mitigates: https://github.com/AleoHQ/snarkOS/issues/3011 - clients are not syncing on testnet because they're only connected to provers.
Explicitly limits the number of prover connections we maintain - assuming honest peer responses.
Test Plan
Should be stress tested on a network with clients and provers.