-
Notifications
You must be signed in to change notification settings - Fork 151
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
node operator guide to deal with a byzantine node #1260
Conversation
Co-authored-by: j pimmel <frankly.watson@gmail.com>
Co-authored-by: j pimmel <frankly.watson@gmail.com>
Co-authored-by: j pimmel <frankly.watson@gmail.com>
this seems very big power to give to node operator, without any consequences. What will happen node operator blocks a non-byzantine node as a byzantine one ? Is this only targeted for ANs? If so can we say we enable permissionless AN little premature? |
If node operators block a byzantine node then their node will not receive all the data it needs to function. e.g. if a verification node blocks an execution node then it may not receive the execution results. |
so this is only targeted for misbehaving AN ( byzantine is not apply here I guess ) ? |
This is intended for node operators to deal with attacks from other nodes on the network. Whether the behavior is intentional or a bug is hard to determine, so the triaging steps include coordinating with other operators to add context. I just added some more details to cover that part of the process. |
thanks for the clarification |
Closes: #???
Description
For contributor use:
master
branchFiles changed
in the Github PR explorer