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

23/WAKU2-TOPICS: bridge content topic changes (#452)

This commit is contained in:
Hanno Cornelius 2021-08-12 10:11:45 +02:00 committed by GitHub
parent 6f5eae0d12
commit f7d81d55d6
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

@ -145,17 +145,19 @@ For mapping Waku v1 topics to Waku v2 content topics,
the following structure for the content topic SHOULD be used:
```
/waku/1/<4bytes-waku-v1-topic>/rlp
/waku/1/<4bytes-waku-v1-topic>/rfc26
```
The `<4bytes-waku-v1-topic>` SHOULD be the lowercase hex representation of the 4-byte Waku v1 topic.
A `0x` prefix SHOULD be used.
`/rfc26` indicates that the bridged content is encoded according to RFC [26/WAKU-PAYLOAD](/spec/26).
See [15/WAKU-BRIDGE](/spec/15) for a description of the bridged fields.
This creates a direct mapping between the two protocols.
For example:
```
/waku/1/0x007f80ff/rlp
/waku/1/0x007f80ff/rfc26
```
# Copyright
@ -180,3 +182,5 @@ Copyright and related rights waived via
7. [6/WAKU1](/spec/6)
8. [15/WAKU-BRIDGE](/spec/15)
9. [26/WAKU-PAYLOAD](/spec/26)