logos-messaging/specs
1
0
Fork 0
mirror of https://github.com/logos-messaging/specs.git synced 2026-01-02 22:23:07 +00:00
Code Issues Packages Projects Releases Wiki Activity

small typos

Browse Source
This commit is contained in:
pablo 2024-04-11 17:29:23 +03:00
parent 4c3aec4669
commit 335e812f2d
No known key found for this signature in database
GPG Key ID: 78F35FCC60FDC63A
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
standards/core/relay-sharding.md
View File

@ -49,14 +49,14 @@ Assigning content topics to specific shards is up to app protocols,
but the discovery of these shards is managed by Waku.
Static shards are managed in shard clusters of 1024 shards per cluster.
Waku static sharding can manage $2^16$ shard clusters.
Each shard cluster is identified by its index (between $0$ and $2^16-1$).
Waku static sharding can manage $2^{16}$ shard clusters.
Each shard cluster is identified by its index (between $0$ and $2^{16}-1$).
A specific shard cluster is either globally available to all apps,
specific for an app protocol,
or reserved for automatic sharding (see next section).
> *Note:* This leads to $2^16 * 1024 = 2^26$ shards for which Waku manages discovery.
> *Note:* This leads to $2^{16} * 1024 = 2^{26}$ shards for which Waku manages discovery.
App protocols can either choose to use global shards, or app specific shards.
@ -128,6 +128,7 @@ Nodes MAY interpret `rs` in such ENRs, but MUST ignore `rsv`.
The ENR key is `rs`.
The value is comprised of
* a two-byte shard cluster index in network byte order, concatenated with
* a one-byte length field holding the number of shards in the given shard cluster, concatenated with
* two-byte shard indices in network byte order