remove p2p reliability concern from light push

This commit is contained in:
fryorcraken 2025-06-04 13:02:37 +10:00
parent 82de90f8e4
commit 8c67398c9b
No known key found for this signature in database
GPG Key ID: A82ED75A8DFC50A4
2 changed files with 6 additions and 7 deletions

View File

@ -16,10 +16,9 @@
## Reliability
1. Implements retransmission on failure with exponential backoff.
2. Implements DoS protection through request rate limitation.
3. Status codes indicate the best recovery method (retry, discard service node or irrecoverable failure).
4. 80% message transmission success rate on live Status network (service node from both Status Desktop and fleet Waku instances)
1. Implements DoS protection through request rate limitation.
2. Status codes indicate the best recovery method (retry, discard service node or irrecoverable failure).
3. 80% message transmission success rate on live Status network (service node from both Status Desktop and fleet Waku instances)
## Performance

View File

@ -40,8 +40,8 @@ TODO: quic PoC
**FURPS**:
- F4. Supports comprehensive error codes for various failure scenarios.
- U4. Provides descriptive error messages in responses.
- R3. Status codes indicate the best recovery method (retry, discard service node or irrecoverable failure).
- R4. 80% message transmission success rate on live Status network (service node from both Status Desktop and fleet Waku instances)
- R2. Status codes indicate the best recovery method (retry, discard service node or irrecoverable failure).
- R3. 80% message transmission success rate on live Status network (service node from both Status Desktop and fleet Waku instances)
For S1. Linux amd64 CLI as service node
Includes spec delivery
@ -61,7 +61,7 @@ Includes spec delivery
**FURPS**:
- F4. Supports comprehensive error codes for various failure scenarios.
- U4. Provides descriptive error messages in responses.
- R3. Status codes indicate the best recovery method (retry, discard service node or irrecoverable failure).
- R2. Status codes indicate the best recovery method (retry, discard service node or irrecoverable failure).
For S2. Browser as client
Spec delivery not included.