ipfs/go-graphsync
View on GitHubInitial Implementation Of GraphSync Wire Protocol
- Stars
- 103
- Forks
- 41
- Open beginner issues
- 0
- Indexed issues
- 36
- Dominant language
- Go
- License
- No license data
- Last GitHub push
- Jul 31, 2026
- Latest indexed
- Sep 17, 2026
- Contributing guide
- Contributing guide
- Code of conduct
- No code of conduct
- Beginner labels
- good first issue
- PR merge metrics
- No merged PRs in 30d
-
effort/weeks exp/wizard P3
ipfs/go-graphsync#24 · 0 comments · 0 reactions · 0 assignees ·
-
exp/expert need/maintainer-input needs definition P3
ipfs/go-graphsync#31 · 0 comments · 0 reactions · 0 assignees ·
-
effort/days exp/expert need/maintainer-input P2
ipfs/go-graphsync#53 · 0 comments · 1 reaction · 0 assignees ·
-
effort/days exp/expert P2
ipfs/go-graphsync#88 · 5 comments · 1 reaction · 1 assignee ·
-
need/triage P2
ipfs/go-graphsync#107 · 1 comment · 0 reactions · 0 assignees ·
-
exp/expert kind/bug P2 x/ignite
ipfs/go-graphsync#158 · 2 comments · 0 reactions · 0 assignees ·
-
effort/weeks exp/wizard P2
ipfs/go-graphsync#160 · 0 comments · 0 reactions · 0 assignees ·
-
effort/days exp/expert need/maintainer-input need/triage needs definition P2
ipfs/go-graphsync#220 · 0 comments · 1 reaction · 0 assignees ·
-
effort/hours exp/intermediate good first issue P2
ipfs/go-graphsync#221 · 0 comments · 0 reactions · 1 assignee ·
-
effort/hours exp/expert P2
ipfs/go-graphsync#222 · 0 comments · 0 reactions · 0 assignees ·
-
Add UnlimitedSimultaneousOutgoingRequests startup option via an "execute immediately" TaskQueue Openeffort/days exp/intermediate P2
ipfs/go-graphsync#233 · 0 comments · 0 reactions · 0 assignees ·
-
effort/hours exp/intermediate need/analysis P3
ipfs/go-graphsync#249 · 2 comments · 0 reactions · 0 assignees ·
-
effort/hours exp/intermediate need/analysis P3
ipfs/go-graphsync#250 · 0 comments · 0 reactions · 0 assignees ·
-
effort/days exp/expert kind/architecture kind/discussion needs definition P2
ipfs/go-graphsync#251 · 0 comments · 0 reactions · 1 assignee ·
-
effort/weeks exp/intermediate need/analysis need/maintainer-input P2 status/blocked
ipfs/go-graphsync#253 · 2 comments · 0 reactions · 0 assignees ·
-
effort/hours exp/intermediate P2
ipfs/go-graphsync#255 · 2 comments · 0 reactions · 0 assignees ·
-
Graphsync Simplication Idea: one libp2p stream per request, no message queues (except for retries) Openeffort/weeks kind/discussion
ipfs/go-graphsync#259 · 2 comments · 0 reactions · 0 assignees ·
-
effort/days kind/discussion
ipfs/go-graphsync#260 · 0 comments · 0 reactions · 0 assignees ·
-
need/triage
ipfs/go-graphsync#293 · 2 comments · 0 reactions · 0 assignees ·
-
need/triage
ipfs/go-graphsync#326 · 3 comments · 0 reactions · 0 assignees ·
-
need/triage
ipfs/go-graphsync#330 · 0 comments · 0 reactions · 0 assignees ·
-
need/triage
ipfs/go-graphsync#343 · 0 comments · 0 reactions · 0 assignees ·
-
need/triage
ipfs/go-graphsync#344 · 3 comments · 0 reactions · 2 assignees ·
-
need/triage
ipfs/go-graphsync#346 · 6 comments · 0 reactions · 2 assignees ·
-
need/triage
ipfs/go-graphsync#347 · 2 comments · 0 reactions · 2 assignees ·
-
need/triage
ipfs/go-graphsync#353 · 0 comments · 0 reactions · 0 assignees ·
-
need/triage
ipfs/go-graphsync#357 · 5 comments · 0 reactions · 2 assignees ·
-
need/triage
ipfs/go-graphsync#371 · 0 comments · 0 reactions · 0 assignees ·
-
ipfs/go-graphsync#372 · 0 comments · 0 reactions · 0 assignees ·
-
ipfs/go-graphsync#373 · 0 comments · 0 reactions · 0 assignees ·
-
ipfs/go-graphsync#374 · 0 comments · 0 reactions · 0 assignees ·
-
Support caching layer for metadata traversals on the responder to answer future requests quickly Open
ipfs/go-graphsync#375 · 0 comments · 0 reactions · 0 assignees ·
-
ipfs/go-graphsync#376 · 0 comments · 0 reactions · 0 assignees ·
-
ipfs/go-graphsync#377 · 1 comment · 0 reactions · 0 assignees ·
-
need/triage
ipfs/go-graphsync#379 · 1 comment · 0 reactions · 1 assignee ·
-
need/triage
ipfs/go-graphsync#380 · 0 comments · 0 reactions · 1 assignee ·