vacp2p
/
rfc
mirror of https://github.com/vacp2p/rfc.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

23/WAKU2-TOPICS: Bridging recommendations (#435) 

* Minor fix and clarifications for bridge topic conversion
This commit is contained in:
Hanno Cornelius 2021-07-21 11:49:28 +02:00 committed by GitHub
parent 2be3e64cd8
commit 047dd40402
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
content/docs/rfcs/23/README.md
View File

@ -5,6 +5,7 @@ name: Waku v2 Topic Usage Recommendations
status: draft status: draft
editor: Oskar Thoren <oskar@status.im> editor: Oskar Thoren <oskar@status.im>
contributors: contributors:
- Hanno Cornelius <hanno@status.im>
--- ---
This document outlines recommended usage of topics in Waku v2. This document outlines recommended usage of topics in Waku v2.
@ -141,12 +142,15 @@ Topics in Waku v1 correspond to Content Topics in Waku v2.
To bridge Waku v1 and Waku v2 we have a [15/WAKU-BRIDGE](/spec/15). To bridge Waku v1 and Waku v2 we have a [15/WAKU-BRIDGE](/spec/15).
For mapping Waku v1 topics to Waku v2 content topics, For mapping Waku v1 topics to Waku v2 content topics,
the following structure for the content topic is used: the following structure for the content topic SHOULD be used:
``` ```
/waku/v1/<4bytes-waku-v1-topic>/rlp /waku/1/<4bytes-waku-v1-topic>/rlp
``` ```
The `<4bytes-waku-v1-topic>` SHOULD be the lowercase hex representation of the 4-byte Waku v1 topic.
A `0x` prefix SHOULD be used.
This creates a direct mapping between the two protocols. This creates a direct mapping between the two protocols.
For example: For example: