feat(parachain/availability-distribution): handle ChunkFetchingRequest
#4487
Labels
C-simple
Minor changes changes, no additional research needed. Good first issue/review.
S-subsystems-availability
issues related to polkadot host availability subsystem functionality.
T-implementation
this issue/pr is a new feature or functionality.
Issue summary
This is a network message received from other validators. The node responds with an erasure chunk from the local availability store.
Implementation details
When receiving a request, send
availabilitystore.QueryChunk
to the availability store via the overseer, passing the candidate hash and validator index from the request. Receive the response from the channel included inQueryChunk
, construct aChunkFetchingResponse
from it and send it to the requesting peer.Protocol versions
v1
andv2
exist for chunk fetching. TheChunkFetchingRequest
message is structurally identical in both versions. There is a subtle difference in the meaning of validator index between the two request messages, but it should not affect this issue. TheChunkFetchingResponse
message inv1
omits the chunks index. Inv2
it contains the fullErasureChunk
object.Our implementation only covers
v1
so far. We should probably add the chunk index to this struct and only supportv2
for the initialimplementation, analogous the approach in other subsystems.
The implementation depends on support for receiving requests of request/response network protocols being implemented. This is tracked in #4453.
Other information and links
Acceptance criteria
The text was updated successfully, but these errors were encountered: