From 8734fd5d8fe4b072ca163e39d712525a0708d8b4 Mon Sep 17 00:00:00 2001 From: Ivan FB Date: Wed, 29 Apr 2026 17:49:10 +0200 Subject: [PATCH] revert changes in messaging-api --- standards/application/messaging-api.md | 9 --------- 1 file changed, 9 deletions(-) diff --git a/standards/application/messaging-api.md b/standards/application/messaging-api.md index 5601271..6531821 100644 --- a/standards/application/messaging-api.md +++ b/standards/application/messaging-api.md @@ -344,15 +344,6 @@ If the `mode` set is `core`, the initialised `WakuNode` SHOULD use: `edge` mode SHOULD be used if node functions in resource restricted environment, whereas `core` SHOULD be used if node has no strong hardware or bandwidth restrictions. -**Fetching missed messages on startup**: - -The node MUST persist the timestamp of the last message it successfully received or sent before going offline. - -After the node is started and subscriptions are set up, the node SHOULD query the -[STORE](https://lip.logos.co/messaging/standards/core/13/store.html) protocol to retrieve messages -missed while offline, scoped to the subscribed content topics and using the persisted timestamp as the -lower bound of the query. - ### Messaging #### Messaging type definitions