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 first copy of payload data is evals, which is what we use everywhere in ADVZ.
The second copy is hidden deep inside evals_proof. The call to lookup returns a MerkleProof, which contains a copy of the payload data as described in #658 .
One of these copies must be eliminated. If we do not remove it from MerkleProof as suggested in #658 then ADVZ should extract the data from there instead of storing an independent copy in Share struct. cc @mrain
The text was updated successfully, but these errors were encountered:
This is bad because it doubles the communication size.
Shares are constructed here:
jellyfish/vid/src/advz.rs
Lines 923 to 932 in 92714a4
The first copy of payload data is
evals
, which is what we use everywhere in ADVZ.The second copy is hidden deep inside
evals_proof
. The call tolookup
returns aMerkleProof
, which contains a copy of the payload data as described in #658 .One of these copies must be eliminated. If we do not remove it from
MerkleProof
as suggested in #658 then ADVZ should extract the data from there instead of storing an independent copy inShare
struct. cc @mrainThe text was updated successfully, but these errors were encountered: