This repository was archived by the owner on Jun 5, 2026. It is now read-only.
introduce reliable channel API#89
Closed
fryorcraken wants to merge 11 commits into
Closed
Conversation
Merged
Merged
Ivansete-status
added a commit
that referenced
this pull request
Apr 9, 2026
Contributor
|
Closing in favour of #104 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The "Reliable Channel" API is the layer that fits between "Chat SDK" and "Waku API", it provided e2e reliability via SDS, as well as other useful utilities for developers.
It fits in more refined proposed layers for Waku: logos-messaging/pm#364
It is partially implemented in js-waku, see logos-messaging/logos-delivery-js#2683 for the most up to date version (blocked on some
subscribeandsendimplementations for the Waku API).See forum post (TODO) for more details.