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

fix: remove limit from spec, leave in the implementation

Browse Source
This commit is contained in:
pablo 2025-10-27 08:59:44 +02:00
parent 9b5e7b9ac3
commit f1804a8dff
No known key found for this signature in database
GPG Key ID: 78F35FCC60FDC63A
1 changed files with 1 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
standards/application/segmentation.md
View File

@ -43,7 +43,6 @@ When the original payload exceeds `segmentSize`, the sender:
- **MUST** split the payload into one or more **data segments**,
each of size up to `segmentSize` bytes.
- **MAY** use Reed–Solomon erasure coding at the predefined parity rate.
Implementations **MUST NOT** produce more than 256 total segments (data + parity).
- Encode each segment as a `SegmentMessageProto` with:
- The `entire_message_hash`
- Either data-segment indices (`segments_count`, `index`) or parity-segment indices (`parity_segments_count`, `parity_segment_index`)
@ -133,7 +132,7 @@ Implementations **SHOULD** support:
**Fixed parameters:**
- `parityRate` — fixed at **0.125** (12.5%)
- `maxTotalSegments` — **256** (library limitation for data + parity segments combined)
- `maxTotalSegments` — **256**
**Reconstruction capability:**
With the predefined parity rate,