You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 14, 2024. It is now read-only.
Currently in Waku v1 we have basic encryption capabilities (public key crypto, symmetric keys). However, these are tightly coupled and a poor design so we are re-designing them (#145).
This means that in Waku v2 there is no end to end encryption by default. It'd be useful to have a basic form of E2EE, etc that people can use.
Acceptance criteria
Companion spec to Waku v2 that is optional and compatible with e.g. Status needs.
Future enhancements of this would be attacked separate. Making these decoupled is mostly at the implementation layer now, and per spec it can be omitted.
Problem
Currently in Waku v1 we have basic encryption capabilities (public key crypto, symmetric keys). However, these are tightly coupled and a poor design so we are re-designing them (#145).
This means that in Waku v2 there is no end to end encryption by default. It'd be useful to have a basic form of E2EE, etc that people can use.
Acceptance criteria
Companion spec to Waku v2 that is optional and compatible with e.g. Status needs.
Details
Possible Solutions
Notes
This is part of #151
https://specs.vac.dev/specs/waku/envelope-data-format.html
The text was updated successfully, but these errors were encountered: