You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Gossipsub grants the ability to set a msgIdFn and a fastMsgIdFn that are used to determine if a message is the same.
By default, gossipsub will allocate a random string if this has not been overridden, this behaviour is not good for us as it means that even though all of our messages have a unique identifier p2pMessageIdentifier (defined on the gossipable interface) they are not actually in use.
This results in txs sent to two different nodes having two different MsgIds, which means they are identified as different messages in gossipsub control messages, which will result scenarios where the same message being propagated across the p2p network multiple times over.
It should be enough to replace these msgIdFns with a function that resolves to the p2pMessageIdentifier.
AC
Replace the message ID function with a custom one that reads the p2pMessageIdentifier
The text was updated successfully, but these errors were encountered:
Overview
Gossipsub grants the ability to set a
msgIdFn
and afastMsgIdFn
that are used to determine if a message is the same.By default, gossipsub will allocate a random string if this has not been overridden, this behaviour is not good for us as it means that even though all of our messages have a unique identifier
p2pMessageIdentifier
(defined on the gossipable interface) they are not actually in use.This results in txs sent to two different nodes having two different MsgIds, which means they are identified as different messages in gossipsub control messages, which will result scenarios where the same message being propagated across the p2p network multiple times over.
It should be enough to replace these msgIdFns with a function that resolves to the p2pMessageIdentifier.
AC
Replace the message ID function with a custom one that reads the p2pMessageIdentifier
The text was updated successfully, but these errors were encountered: