Skip to content

ipfs bitswap wantlist #7284

@dirkmc

Description

@dirkmc

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=<peer> reports the wants that Bitswap has received from that peer: "blocks that <peer> 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)

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/enhancementA net-new feature or improvement to an existing feature

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions