feat: bridge relay topics #854
Merged
Conversation
This file contains 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
Jenkins BuildsClick to see older builds (18)
|
richard-ramos
commented
Oct 31, 2023
richard-ramos
force-pushed
the
relay-bridge
branch
from
bbce263 to
579f3c6
Compare
richard-ramos
force-pushed
the
relay-bridge
branch
from
579f3c6 to
0f04c31
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
On today's message reliability call, creating a bridge between pubsub topics was suggested as a way to solve backward compatibility due to the breaking change introduced in status-im/status-go#4161.
This PR adds a hidden
--bridge-topic=fromTopic:toTopicflag that can be used to bridge messages from a pubsub topic to another. This is meant to be used withstatus.prodto get messages going from between the default shard and the default pubsub topic (since mixing named and static sharding introduces a lot of problems).go-waku nodes must be configured with the following flags:
(Maybe we can reuse
gowaku.prodfleet)