fix(consensus, beacon): hardened proposer validation

[abi87]

Hardened proposer validation by checking that validator address from CometBFT consensus matches with the key registered for the validator in Beacon state

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[codecov]

Codecov Report

Attention: Patch coverage is 9.96885% with 289 lines in your changes missing coverage. Please review.

Project coverage is 24.66%. Comparing base (66bad3e) to head (2c7f448).
Report is 30 commits behind head on consensus_decorated_events.

Files with missing lines	Patch %	Lines
mod/state-transition/pkg/core/state_processor.go	7.40%	50 Missing ⚠️
.../consensus/pkg/cometbft/service/middleware/abci.go	0.00%	41 Missing ⚠️
mod/beacon/blockchain/receive.go	0.00%	27 Missing ⚠️
mod/beacon/validator/block_builder.go	0.00%	21 Missing ⚠️
...nsus/pkg/cometbft/service/middleware/middleware.go	0.00%	20 Missing ⚠️
mod/consensus/pkg/cometbft/service/abci.go	0.00%	17 Missing ⚠️
...ate-transition/pkg/core/state_processor_payload.go	0.00%	16 Missing ⚠️
mod/beacon/blockchain/payload.go	0.00%	13 Missing ⚠️
mod/consensus/pkg/types/slot_data.go	0.00%	12 Missing ⚠️
mod/beacon/blockchain/execution_engine.go	0.00%	11 Missing ⚠️
... and 15 more

Additional details and impacted files

@@                      Coverage Diff                       @@
##           consensus_decorated_events    #2102      +/-   ##
==============================================================
+ Coverage                       23.48%   24.66%   +1.18%     
==============================================================
  Files                             357      359       +2     
  Lines                           16064    16183     +119     
  Branches                           12       12              
==============================================================
+ Hits                             3772     3991     +219     
+ Misses                          12121    11997     -124     
- Partials                          171      195      +24     

Files with missing lines	Coverage Δ
mod/node-core/pkg/components/service_registry.go	0.00% <ø> (ø)
mod/node-core/pkg/components/chain_service.go	0.00% <0.00%> (ø)
mod/node-core/pkg/components/middleware.go	0.00% <0.00%> (ø)
mod/node-core/pkg/components/state_processor.go	0.00% <0.00%> (ø)
...tate-transition/pkg/core/state_processor_randao.go	0.00% <0.00%> (ø)
testing/e2e/config/config.go	0.00% <0.00%> (ø)
mod/node-core/pkg/components/dispatcher.go	0.00% <0.00%> (ø)
...ate-transition/pkg/core/state_processor_genesis.go	48.95% <89.47%> (+48.95%)	⬆️
mod/consensus/pkg/types/common.go	0.00% <0.00%> (ø)
mod/primitives/pkg/transition/context.go	0.00% <0.00%> (ø)
... and 16 more

... and 4 files with indirect coverage changes

[abi87]

fGetAddressFromPubKey avoids the inconvenience of setting BLS keys in unit tests, since it allows injecting whatever function we care to pass or not validation.
It is useful as we merge in unit tests and we need to pass proposer address checks