Add EIP: Beacon Block Reporting Field - #12063
Conversation
|
✅ All reviewers have approved. |
eth-bot
left a comment
There was a problem hiding this comment.
All Reviewers Have Approved; Performing Automatic Merge...
eth-bot
left a comment
There was a problem hiding this comment.
All Reviewers Have Approved; Performing Automatic Merge...
eth-bot
left a comment
There was a problem hiding this comment.
All Reviewers Have Approved; Performing Automatic Merge...
Co-authored-by: Andrew B Coathup <28278242+abcoathup@users.noreply.github.com>
Head branch was pushed to by a user without write access
eth-bot
left a comment
There was a problem hiding this comment.
All Reviewers Have Approved; Performing Automatic Merge...
Co-authored-by: Andrew B Coathup <28278242+abcoathup@users.noreply.github.com>
Head branch was pushed to by a user without write access
eth-bot
left a comment
There was a problem hiding this comment.
All Reviewers Have Approved; Performing Automatic Merge...
eth-bot
left a comment
There was a problem hiding this comment.
All Reviewers Have Approved; Performing Automatic Merge...
eth-bot
left a comment
There was a problem hiding this comment.
All Reviewers Have Approved; Performing Automatic Merge...
|
The commit 641af4e (as a parent of 0f94319) contains errors. |
Adds a new Standards Track Core EIP for an optional 32-byte beacon block body
reportingfield.The field allows validators to report CL client, EL client, setup type, and multi-node threshold information for aggregate client-diversity visibility. The field is informational only and does not make blocks invalid based on reported contents.
Discussion: https://ethereum-magicians.org/t/eip-proposal-beacon-block-reporting-field/29224