Current text:
There is no routing. A node sends every statement to every peer that lacks it. No topic-aware forwarding, no per-recipient path.
Suggested replacement:
Celerity distributes signed statements between peers. A recipient retrieves matching statements by subscribing to an exact 32-byte topic through its RPC provider.
The current sentence makes full replication the privacy guarantee. Current
Polkadot SDK master also implements statement/2, which can filter
propagation with a peer's advertised topic affinity. The deployed protocol must
be confirmed before the text says that every peer receives every statement.
Update Figure 2, “One message, end to end.” Do not add another figure.
flowchart LR
Chain["People chain<br/>publishing allowance"]
Alice["Sender app"]
SenderRPC["Sender RPC node"]
Network["Celerity<br/>statement network"]
RecipientRPC["Recipient RPC node"]
Bob["Recipient app"]
Chain -. "authorises signer" .-> SenderRPC
Alice -->|"1. Submit signed,<br/>encrypted statement"| SenderRPC
SenderRPC -->|"2. Propagate using the<br/>deployed protocol"| Network
Network --> RecipientRPC
Bob -->|"3. Subscribe to<br/>exact topic"| RecipientRPC
RecipientRPC -->|"4. Return matching<br/>statement"| Bob
Proposed caption:
Figure 2. The chain authorises publishing capacity, while the encrypted message remains off-chain. The recipient subscribes to an exact topic through an RPC provider. The provider sees that topic filter. Statement propagation follows the protocol deployed by the Celerity network.
The revised figure should:
- distinguish chain authorisation from the off-chain message path;
- show both RPC edges, including the matching response;
- state the RPC provider's visibility;
- replace “GOSSIP TO EVERY PEER” with verified deployed behavior; and
- use a narrow, stacked mobile composition rather than scaling desktop text to an unreadable size.