Changes here address the bulk of what is necessary for
https://github.com/waku-org/pm/issues/266 and
https://github.com/status-im/status-go/issues/5821 to define the new
shared-shard strategy for Communities.
This PR should be enough unblock implementation and, once merged, we can
go ahead with the pubsub topic changes in status-go.
I'm not yet closing the accompanying deliverable, as the spec still
requires a full list of all Communities-related messages with functional
scope explicitly assigned.
This adds a new raw specification covering the Status protocol stack,
including:
- common app-level features (content topics, functional scopes,
ephemerality)
- e2e reliability layer
- encryption layer (TBD)
- Waku transport layer
It deprecates/replaces the previous status waku-usage spec.
---------
Co-authored-by: Jimmy Debe <91767824+jimstir@users.noreply.github.com>
