You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The "Compute sum of commitments" code can be simplified by just doing an MSM over all commitments and their weights. That is, without sieving which are used and which are not which IMO complicates the codebase. Anything that is not used would have zero weight and hence it would not contribute to the MSM.
After all, if I'm not mistaken, for PeerDAS we will always use all the commitments since we fetch the entire column, so we will not do any wasted bytes_to_kzg_commitment().
The text was updated successfully, but these errors were encountered:
The "Compute sum of commitments" code can be simplified by just doing an MSM over all commitments and their weights. That is, without sieving which are used and which are not which IMO complicates the codebase. Anything that is not used would have zero weight and hence it would not contribute to the MSM.
This is what @b-wagn did in his PR (ethereum/consensus-specs#3812) and it's simpler.
After all, if I'm not mistaken, for PeerDAS we will always use all the commitments since we fetch the entire column, so we will not do any wasted bytes_to_kzg_commitment().
The text was updated successfully, but these errors were encountered: