service/block: new block listener + erasure coding #77
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renaynay
force-pushed
the
block-service-erasure-coding
branch
3 times, most recently
from
22ba323
to
2ad2cf7
Compare
renaynay
force-pushed
the
block-service-erasure-coding
branch
from
d9a2f8c
to
457ee6d
Compare
renaynay
changed the title
8 tasks
liamsi
reviewed
Sep 23, 2021
renaynay
force-pushed
the
block-service-erasure-coding
branch
from
dc61e1c
to
538143e
Compare
This was
unlinked from
issues
Sep 28, 2021
Wondertan
approved these changes
Sep 28, 2021
ghost
mentioned this pull request
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implements a new block listener loops that, upon receiving a new block from the fetcher, will handle it by doing the following:
DataAvailabilityHeaderfrom the extended block dataNumber 3 and 4 are stubbed out at the moment, but will be implemented at a later time. Number 3 is optional to implement before Devnet.
Related to celestiaorg/celestia-specs#26, celestiaorg/celestia-specs#25
Resolves celestiaorg/celestia-specs#56
TODO