From f7d81d55d6e57b96df2ee75c8ca8a8cf15dc9ed4 Mon Sep 17 00:00:00 2001
From: Hanno Cornelius <68783915+jm-clius@users.noreply.github.com>
Date: Thu, 12 Aug 2021 10:11:45 +0200
Subject: [PATCH] 23/WAKU2-TOPICS: bridge content topic changes (#452)

---
 content/docs/rfcs/23/README.md | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/content/docs/rfcs/23/README.md b/content/docs/rfcs/23/README.md
index 2aac459e..f4f98cea 100644
--- a/content/docs/rfcs/23/README.md
+++ b/content/docs/rfcs/23/README.md
@@ -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)