feat: return providing peer(s) in `bitswap:want-block:block` event

[SgtPooki]

Question

Using Helia, when I download the contents of a CID, could I easily see which node I ultimately retrieved the data from? How would I do that?

• @TheDiscordian

Answer

This could be added to bitswap - the hasBlock method here would need the id of the providing peer added as an argument, then the bitswap:want-block:block event could hold both the CID of the incoming block and the providing peer when it's emitted here.

It's worth noting that if the DAG referenced by a CID is made from multiple blocks, these blocks could come from different peers, so it'd be more like "which node(s)" rather than "which node".

• @achingbrain

This question came across in ip-js channel on slack: https://filecoinproject.slack.com/archives/C046HDAHA13/p1689877647075909

[welcome]

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

• "Priority" labels will show how urgent this is for the team.
• "Status" labels will show if this is ready to be worked on, blocked, or in progress.
• "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.