-
Notifications
You must be signed in to change notification settings - Fork 974
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
EIP-7594: add custody settings config #3766
Conversation
Co-authored-by: Hsiao-Wei Wang <[email protected]>
@@ -158,6 +158,9 @@ NUMBER_OF_COLUMNS: 128 | |||
MAX_CELLS_IN_EXTENDED_MATRIX: 768 | |||
DATA_COLUMN_SIDECAR_SUBNET_COUNT: 32 | |||
MAX_REQUEST_DATA_COLUMN_SIDECARS: 16384 | |||
SAMPLES_PER_SLOT: 8 | |||
CUSTODY_REQUIREMENT: 1 | |||
TARGET_NUMBER_OF_PEERS: 70 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need the target number of peers in the config?
Currently I think most clients expose this via a CLI flag. Each client sets their own defaults based on node-resources and misc tradeoffs with performance. I think we probably still want to leave this up to client implementations to set
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Re including this values in the spec:
SAMPLES_PER_SLOT
: As of today sampling is only used for a node to influence its own view on what's safe. This is subjective and different users may have different safety requirements. I would exclude this value from the configCUSTODY_REQUIREMENT
: Only makes sense to add to the spec if this is the minimum custody per NodeID, enforceable with peer scoring.TARGET_NUMBER_OF_PEERS
: Clients allow to customize peer counts. Clients may choose to show warnings if the user selects a value less than this. Then I'm not sure of the usefulness of having this parameter in the spec. Unless we expect different networks to have widely different peers needs and it being convenient to standardized those warning messages
For the spec format, we just need to put them into either presets or configurations 😅 |
No description provided.