Closed ogenev closed 7 months ago
I don't find
MergeAccumulator
particularly more clear.It does not clarify that it is the accumulator for pre-merge data. And merge could also just mean something specifically regarding the accumulator itself.
What about PreMergeAccumulator
, for pre-Capella headers it will be PreCapellaAccumulator
(beacon state historical_roots
) ?
Do you have any suggestions?
What about
PreMergeAccumulator
, for pre-Capella headers it will bePreCapellaAccumulator
(beacon statehistorical_roots
) ?
Yes, PreMergeAccumulator
would be better.
I would not create an additional name for the historical_roots
and the historical_summaries
. I'd just keep those names from the consensus specs.
Yes,
PreMergeAccumulator
would be better.
Updated to PreMergeAccumulator
.
Added a new commit to rename theAccumulatorProof
.
We will have more than one header accumulator for verifying the canonicalness of history headers:
historical_roots
from beacon state) for pre-Capella and post-merge headers.This PR proposes to rename
MasterAccumulator
toMergeAccumulator
to make the name less confusing and more clear.