Skip to content

v1.18: Remove the chained merkle root check#1161

Closed
AshwinSekar wants to merge 1 commit intoanza-xyz:v1.18from
AshwinSekar:v1.18
Closed

v1.18: Remove the chained merkle root check#1161
AshwinSekar wants to merge 1 commit intoanza-xyz:v1.18from
AshwinSekar:v1.18

Conversation

@AshwinSekar
Copy link
Copy Markdown

@AshwinSekar AshwinSekar commented May 3, 2024

This is a partial revert of commit 07a9b53.

The original commit does not account for the fact that the validator can upgrade with incomplete shreds in a slot.
If the upgrade happens around an FEC set boundary, checking the previous merkle root chaining should not assume the merkle root meta column exists for the previous FEC set.

@AshwinSekar AshwinSekar requested a review from a team as a code owner May 3, 2024 03:10
@AshwinSekar AshwinSekar requested a review from a team May 3, 2024 03:10
@AshwinSekar AshwinSekar changed the title Revert "v1.18: blockstore: send duplicate proofs for chained merkle r… v1.18: Remove the chained merkle root check May 3, 2024
@AshwinSekar AshwinSekar marked this pull request as draft May 3, 2024 04:01
@codecov-commenter
Copy link
Copy Markdown

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.5%. Comparing base (c8e6fd0) to head (9b56af9).

Additional details and impacted files
@@            Coverage Diff            @@
##            v1.18    #1161     +/-   ##
=========================================
- Coverage    81.6%    81.5%   -0.2%     
=========================================
  Files         827      827             
  Lines      225352   225332     -20     
=========================================
- Hits       184011   183704    -307     
- Misses      41341    41628    +287     

@AshwinSekar
Copy link
Copy Markdown
Author

closed in favor of #1163

@AshwinSekar AshwinSekar closed this May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants