Message ordering is not maintained in Gossipsub

[dvasanth]

Summary

Previous version of Gossipsub messages had some message sequence ordering. With newer latest 0.52.3 version, the ordering is always wrong.

Expected behaviour

Expecting the messages published for a topic to be in order or at least provide a sequence id to help the application order the messages.

Actual behaviour

Messages published in Gossipsub received always out of sequence.

Possible Solution

Instead of having random message Id it can have a sequence number to help application order it. Security risks due to linear message Ids can be avoided with other mechanisms.

Version

libp2p = { version = "^0.52.3", features = ["full"] }
I think there is some changes introduced that affects the ordering.

Would you like to work on fixing this bug?

Yes.

[thomaseizinger]

I think what you are looking for is #3551. If you use signed messages, you'll get sequential IDs.