filecoin-project / filecoin-project/lassie
prioritize candidates in bitswap requests
Open
- Dominant language
- Go
- Stars
- 118
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
we get a set of candidates from the indexer.
when bitswap is started my understanding is that it doesn't use these, but rather will only use them once it's finished dialing it's current swarm.
that seems inefficient
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.