ipfs bitswap wantlist
Open
kind/enhancement
- Dominant language
- Go
- Stars
- 17.1k
- Forks
- 3.2k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 11
Description
`ipfs bitswap wantlist` reports different things depending on whether the user passes the `--peer` parameter:
- `ipfs bitswap wantlist` reports the wants that Bitswap has _sent_ to all peers (and has not received a response yet): "blocks that I want from my peers"
- `ipfs bitswap wantlist --peer=` reports the wants that Bitswap has _received_ from that peer: "blocks that `` wants from me"
I'd suggest that we add subcommands that are unambiguous:
- `ipfs bitswap sent-wants` (with optional `--peer` parameter)
- `ipfs bitswap received-wants` (with optional `--peer` parameter)
Contributor guide
Assessment
This issue has not been assessed yet.