Skip to content
This repository has been archived by the owner on Jun 14, 2024. It is now read-only.

Add WakuMetadata to TWN #624

Merged
merged 3 commits into from
Oct 4, 2023
Merged

Add WakuMetadata to TWN #624

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
570a01d
Add WakuMetadata to TWN
alrevuelta Oct 3, 2023
6608d7d
Update README.md
alrevuelta Oct 4, 2023
3b4ee7e
Update README.md
alrevuelta Oct 4, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 9 additions & 2 deletions content/docs/rfcs/64/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,8 +33,9 @@ which in turn is an extension of [11/WAKU2-RELAY](https://rfc.vac.dev/spec/11/)
Traffic in the Waku Network is sharded into eight [17/WAKU2-RLN-RELAY](https://rfc.vac.dev/spec/17/) pubsub topics.
Each pubsub topic is named according to the static shard naming format
defined in [51/WAKU2-RELAY-SHARDING](https://rfc.vac.dev/spec/51/)
with `<cluster_id>` set to `1` and
`<shard_number>` occupying the range `0` to `7`.
with:
* `<cluster_id>` set to `1`
* `<shard_number>` occupying the range `0` to `7`.
In other words, the Waku Network is a [17/WAKU2-RLN-RELAY](https://rfc.vac.dev/spec/17/) network
routed on the combination of the eight pubsub topics:
```
Expand All @@ -44,6 +45,12 @@ routed on the combination of the eight pubsub topics:
/waku/2/rs/1/7
```

A node MUST use [WAKU-METADATA](https://rfc.vac.dev/spec/66/) protocol to identify the `<cluster_id>` that every
inbound/outbound peer that attempts to connect supports. In any of the following cases, the node MUST trigger a disconnection:
* [WAKU-METADATA](https://rfc.vac.dev/spec/66/) dial fails.
* [WAKU-METADATA](https://rfc.vac.dev/spec/66/) reports an empty `<cluster_id>`.
* [WAKU-METADATA](https://rfc.vac.dev/spec/66/) reports different `<cluster_id>` than the local one.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since for TWN cluster_id can only be 1, perhaps we can be explicit here and simply say something like:

reports <cluster_id> different than 1.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

indeed, fixed!
3b4ee7e


## Roles

There are two distinct roles evident in the network, those of:
Expand Down