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
A recent spec proposal reiterates the need to separate header fetching from full block fetching. A first step to achieve this is to add headers-only fetching support to the graphsync fetcher.
Acceptance criteria
The graphsync fetcher is extended to include functions for fetching headers only.
Risks + pitfalls
Selector foo is hard
tests are already big and unwieldy, let's try to make tests cleaner with this PR
Where to begin
Probably the vast majority of fetcher logic can be abstracted into a common method figure out a nice shared abstraction.
The text was updated successfully, but these errors were encountered:
Description
A recent spec proposal reiterates the need to separate header fetching from full block fetching. A first step to achieve this is to add headers-only fetching support to the graphsync fetcher.
Acceptance criteria
The graphsync fetcher is extended to include functions for fetching headers only.
Risks + pitfalls
Where to begin
Probably the vast majority of fetcher logic can be abstracted into a common method figure out a nice shared abstraction.
The text was updated successfully, but these errors were encountered: