-
Notifications
You must be signed in to change notification settings - Fork 250
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
adds peerdas-supernode flag #6764
Conversation
…in subscribeAllSubnets
beacon_chain/conf.nim
Outdated
peerdasSupernode* {. | ||
defaultValue: false, | ||
desc: "Subscribe to all column subnets, thereby becoming a peerdas supernode" | ||
name: "peerdas-supernode" .}: bool |
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.
debug-peerdas-supernode
would be nicer.
https://nimbus.guide/options.html
Any
debug
-prefixed flags are considered ephemeral and subject to removal without notice.
Until Fulu
becomes production, this is a debugging flag for devnet/testnet/Kurtosis purposes, so shouldn't be documented or supported-per-se.
Also, probably, hidden
, because again, it's not really part of the supported UI/UX yet, certainly before Fulu is in public testnets (months from now).
It does seem possible it will at some point, but no need to do that prematurely.
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.
ok, resolving
In order to measure resources efficiently it's beneficial to have a separate peerdas supernode flag, this is because if we launch a peerdas supernode on
subscribe-all-subnets
, then we also end up subscribing to all attnets and syncnets, which would thereby use of more resources to run the peerdas supernode.