logos-messaging/specs
1
0
Fork 0
mirror of https://github.com/logos-messaging/specs.git synced 2026-05-26 14:59:35 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix: dictionary

Browse Source
This commit is contained in:
pablo 2025-10-19 15:56:33 +03:00 committed by Igor Sirotin
parent 550147b0df
commit ebaea1f7ee
No known key found for this signature in database
GPG Key ID: 0EABBCB40CB9AD4A
2 changed files with 10 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
.wordlist.txt
View File

@ -110,6 +110,7 @@ Kozlov
lifecycle lifecycle
liblogosdelivery liblogosdelivery
libp libp
Keccak
libp2p libp2p
Lightpush Lightpush
LIGHTPUSH LIGHTPUSH
@ -159,6 +160,9 @@ Prathi
pre pre
Prem Prem
ProtocolsConfig ProtocolsConfig
Nim
nim
parityRate
protobuf protobuf
pubsub pubsub
rateLimitConfig rateLimitConfig
@ -211,6 +215,8 @@ SegmentationConfig
segmentationConfig segmentationConfig
segmentSizeBytes segmentSizeBytes
sharding sharding
RLN
segmentSize
SHARDING SHARDING
sqlite sqlite
subnets subnets
@ -232,6 +238,7 @@ UUID
UX UX
waku waku
Waku Waku
Waku's
WAKU WAKU
WakuNode WakuNode
www www

12
standards/application/segmentation.md
View File

@ -12,7 +12,7 @@ This specification defines an application-layer protocol for **segmentation** an
## Motivation ## Motivation
Waku Relay deployments typically propagate envelopes up to **1 MB**. To support larger application payloads (e.g., up to **10 MiB** or more), a segmentation layer is required. This specification enables larger messages by partitioning them into multiple envelopes and reconstructing them at the receiver. Erasure-coded parity segments provide resilience against partial loss or reordering. Waku Relay deployments typically propagate envelopes up to **1 MB**. To support larger application payloads (e.g., up to **10 MB** or more), a segmentation layer is required. This specification enables larger messages by partitioning them into multiple envelopes and reconstructing them at the receiver. Erasure-coded parity segments provide resilience against partial loss or reordering.
## Terminology ## Terminology
@ -129,7 +129,7 @@ Implementations **SHOULD** support:
**API simplicity:** Libraries **SHOULD** require only `segmentSize` from the application for normal operation. **API simplicity:** Libraries **SHOULD** require only `segmentSize` from the application for normal operation.
### Supportability ### Support
- **Language / Package:** Nim; **Nimble** package manager - **Language / Package:** Nim; **Nimble** package manager
- **Intended for:** all Waku nodes at the application layer - **Intended for:** all Waku nodes at the application layer
@ -163,7 +163,7 @@ Nodes that do **not** implement this specification cannot reconstruct large mess
--- ---
## Deployability ## Deploy
- Bandwidth overhead ≈ **12.5%** from parity (if enabled) - Bandwidth overhead ≈ **12.5%** from parity (if enabled)
- Additional per-segment overhead ≤ **100 bytes** (protobuf + metadata) - Additional per-segment overhead ≤ **100 bytes** (protobuf + metadata)
@ -179,9 +179,3 @@ Nodes that do **not** implement this specification cannot reconstruct large mess
4. [nim-leopard](https://github.com/status-im/nim-leopard) – Nim bindings for Leopard-RS (Reed–Solomon) 4. [nim-leopard](https://github.com/status-im/nim-leopard) – Nim bindings for Leopard-RS (Reed–Solomon)
5. [Leopard-RS](https://github.com/catid/leopard) – Fast Reed–Solomon erasure coding library 5. [Leopard-RS](https://github.com/catid/leopard) – Fast Reed–Solomon erasure coding library
6. [RFC 2119](https://www.ietf.org/rfc/rfc2119.txt) – Key words for use in RFCs to Indicate Requirement Levels 6. [RFC 2119](https://www.ietf.org/rfc/rfc2119.txt) – Key words for use in RFCs to Indicate Requirement Levels
---
## Changelog
- **0.1 — Initial draft**