-
Notifications
You must be signed in to change notification settings - Fork 264
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove the DataAvailabilityHeader
from Block
#512
Comments
Makes sense |
1 task
We also have to the option to only remove the DAH from the proto type of |
This was referenced Aug 26, 2021
This was referenced Sep 20, 2021
closed by the merging of #534 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
We don't strictly need the
DataAvailabilityHeader
to be inBlock
, so we can remove it.Problem Definition
Since the
DataAvailabilityHeader
does not have to be inBlock
, and validators already have to regenerate the DataAvailabilityHeader to verify the block, then we could optimize the size of theBlock
struct by removing theDataAvailabilityHeader
field.Proposal
Instead of passing the
DataAvailabilityHeader
with theBlock
, we can remove theDataAvailabilityHeader
field and instead generate it after receiving theBlock
. TheDataAvailabilityHeader
would then be passed to any function that needs it, or regenerated.Note: this is purely an optimization, and should therefore not be prioritized until later. This could also be accomplished in conjunction with #505, as that will be required to fully remove the DAH from the block
Implementation
DataAvailabilityHeader
from blockBlockMeta
by passing it theSaveBlock
methodPutBlock
(assuming we keep PutBlock at all)blocked by:
#518
#505
The text was updated successfully, but these errors were encountered: