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
To protect against the length attack we should store the first share of the blob in the blob's proof.
A length attack is an attack when a malicious node can give us invalid proof and commitment and it could be proved against the header's DataRoot correctly. It can happen when the proof will contain only part of the subtreeRoots.
The text was updated successfully, but these errors were encountered:
vgonkivs
changed the title
Store the first share of the Blob in the blob's proof.
blob: store the first share of the Blob in the blob's proof
May 31, 2023
From the first share of the Blob you can get the Sequence Length. From the sequence Length, you can check the length of the blob. If i don't, i can create a correct inclusion proof for 3/4 of a blob that is actually 4 shares long. The malicious commitment would be PFB2
To protect against the length attack we should store the first share of the blob in the blob's proof.
A length attack is an attack when a malicious node can give us invalid proof and commitment and it could be proved against the header's DataRoot correctly. It can happen when the proof will contain only part of the subtreeRoots.
The text was updated successfully, but these errors were encountered: