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
What is this task and why do we need to work on it?
With some upcoming changes to storage, the confirmation will soon be able to serve catchup from any node in the network, DA or not. With PoS making the node set more dynamic, it will become crucial that we can tap into the existing networking mechanisms to reach our peers for catchup requests, rather than relying on a configured list of nodes which is static and often incomplete.
What work will need to be done to complete this task?
There should be some interface that allows the application layer (e.g. confirmation layer) to make arbitrary requests and receive responses. These requests should be routed to the entire network over the combined CDN+p2p network.
Are there any other details to include?
No response
What are the acceptance criteria to close this issue?
We are able to implement the following request types in the query service/confirmation layer:
Request leaf by height (served by query service)
Request payload by VID commitment (served by query service)
Request VID common by VID commitment (served by query service)
Request fee account states (served by confirmation layer/validated state persistence)
Request blocks frontier (served by confirmation layer/validated state persistence)
Request config (served by confirmation layer)
Branch work will be merged to (if not the default branch)
No response
The text was updated successfully, but these errors were encountered:
What is this task and why do we need to work on it?
With some upcoming changes to storage, the confirmation will soon be able to serve catchup from any node in the network, DA or not. With PoS making the node set more dynamic, it will become crucial that we can tap into the existing networking mechanisms to reach our peers for catchup requests, rather than relying on a configured list of nodes which is static and often incomplete.
What work will need to be done to complete this task?
There should be some interface that allows the application layer (e.g. confirmation layer) to make arbitrary requests and receive responses. These requests should be routed to the entire network over the combined CDN+p2p network.
Are there any other details to include?
No response
What are the acceptance criteria to close this issue?
We are able to implement the following request types in the query service/confirmation layer:
Branch work will be merged to (if not the default branch)
No response
The text was updated successfully, but these errors were encountered: