-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Peer Report Configuration #1340
Comments
This applies to a number of locations marked with TODOs and this issue number, including heartbeat peer rep, etc. |
This was referenced Sep 22, 2023
crypto523
pushed a commit
to crypto523/fuel-core
that referenced
this issue
Oct 7, 2024
… values (#1380) This was left behind from this work: FuelLabs/fuel-core#1356 As we did for the syncing peer config, we left hard-coded values for each variant. The followup work for that is tracked here: FuelLabs/fuel-core#1340 --------- Co-authored-by: Green Baneling <XgreenX9999@gmail.com>
This is probably a good thing to have, but no one is asking for it. On the other hand, any values we are using inside peer review are arbitrary, so having some control of them is probably important. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As a follow-up to #943 we might want to provide a way for the client operator to modify the
PeerReportConfig
that is passed to theP2PAdapter
.It should be configurable via CLI and maybe it worth to have a separate
--p2p-reputation
config.The text was updated successfully, but these errors were encountered: