Message Delivery Order Inconsistency in Waku Gossip Protocol

Gossip Propagation and Sequencing

Waku employs a decentralized gossip-based protocol to propagate messages across a peer-to-peer network. While the store-and-forward mechanism ensures that offline peers can eventually retrieve missed data, the protocol does not natively guarantee a global deterministic order for message arrival across varying network topologies.

Topology Constraints

In environments with high peer churn or significant network latency, messages published to the same topic may reach different nodes in different sequences. This behavior creates uncertainty for applications that require strict causal ordering or sequential state synchronization across all participants.

• Dependence on DHT for peer discovery.
• Topic-based routing filters.
• Asynchronous propagation delays.

Does Waku provide a built-in mechanism to ensure deterministic message ordering across all nodes in a gossip network? If not, what is the recommended approach for implementing sequential consistency at the application layer?