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

docs: fix TeX superscript

Browse Source
This commit is contained in:
Jazz Turner-Baggs 2025-02-25 14:27:34 -08:00 committed by GitHub
parent 25e3f5a09a
commit d92bb72ca5
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
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. but the discovery of these shards is managed by Waku.
Static shards are managed in shard clusters of 1024 shards per cluster. Static shards are managed in shard clusters of 1024 shards per cluster.
Waku static sharding can manage $2^16$ shard clusters. Waku static sharding can manage $2^{16}$ shard clusters.
Each shard cluster is identified by its index (between $0$ and $2^16-1$). 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, A specific shard cluster is either globally available to all apps,
specific for an app protocol, specific for an app protocol,
or reserved for automatic sharding (see next section). 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. App protocols can either choose to use global shards, or app specific shards.