fix Waku API

This commit is contained in:
fryorcraken 2025-06-03 20:03:28 +10:00
parent 9f9fbdd69d
commit 62a0665db9
No known key found for this signature in database
GPG Key ID: A82ED75A8DFC50A4
2 changed files with 3 additions and 3 deletions

View File

@ -18,8 +18,8 @@
## Reliability
1. Sends a message using peer-to-peer reliability (service node redundancy, optional store confirmation)
2. Receives messages using peer-to-peer reliability (service node redundancy, periodic store query, periodic filter ping)
1. Sends a message using peer-to-peer reliability (service node redundancy for edge, optional store confirmation)
2. Receives messages using peer-to-peer reliability (service node redundancy for edge, periodic store query, periodic filter ping)
## Performance

View File

@ -103,7 +103,7 @@ For S3. Browser
**FURPS**:
- F1. Setup, start and stop a Waku node.
- F. Support edge node operation mode.
- F3. Support relay node operation mode.
- F4. Does automatic peer discovery based on the node platform and operation mode.
- F5. Returns health and connectivity information using proven heuristics.
- U1. When setting up a Waku node, no need to specify what protocols to mount, only an operational mode (edge or relay).