Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions pubsub/gossipsub/gossipsub-v1.2.md
Original file line number Diff line number Diff line change
Expand Up @@ -56,6 +56,7 @@ This section lists the configuration parameters that needs to agreed on across c
When the peer receives the first message instance it immediately broadcasts
(not queue for later piggybacking) `IDONTWANT` with the `messageId` to all its mesh peers.
This could be performed prior to the message validation to further increase the effectiveness of the approach.
Additionally, on networks where multiple messages share the same messageId, a user may choose to broadcast IDONTWANT when publishing.
Copy link
Contributor

@ppopth ppopth Nov 26, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's good to note that the publisher still shouldn't publish the message to the peers that previously sent an IDONTWANT to the publisher.

It's trivial to know this but I'm afraid that some implementers will forget this.


On the other side a node maintains per-peer `dont_send_message_ids` set. Upon receiving `IDONTWANT` from
a peer the `messageId` is added to the `dont_send_message_ids` set.
Expand Down