[Deliverable] Specify private chat protocol

[plopezlpz]

Summary

Understand and document the current Status private chats protocol stack. This includes encryption, usage of content topics, message flows, control message - size, frequency and purpose, MVDS usage.
This acts as the basis for future work, to modify the one-to-one chat protocol to stabilize, secure and scale it.

TODO

• Document the current protocol as it is used currently
• Improve and define specs based on the current protocol, keep in mind reliability, encryption, bandwidth usage and DoS protection

Tasks

• Document current encryption in Status one-to-one status-im/status-go#6319
• Document current usage of content topics (one-to-one) status-im/status-go#6320
• Document current message flows (one-to-one) status-im/status-go#6350
• Document current MVDS usage in one-to-one messages status-im/status-go#6382
• Document current control messages: size, frequency and purpose (one-to-one) status-im/status-go#6383
• (maybe) Small PoC of chat protocol to consider viability of extracting chat protocol logic from status-go here

[plopezlpz]

@jazzz FYI

[plopezlpz]

Chat SDK roadmap: https://forum.vac.dev/t/private-chat-sdk-roadmap-skeleton/463/2

[jazzz]

Heres why we need a new chat protocol: https://forum.vac.dev/t/chatsdk-motivations/501

[fryorcraken]

Thank you @jazzz .

The present work has enabled us to propose writing a new protocol and implementation from scratch, as a better effort/value ratio item.

Hence, while some documentation has been produced in terms of the current Status Chat protocol. We will not proceed with writing formal specs as it has little to no value.

Instead, formal specs can be expected from the new chat protocol, along side the new implementation.

Closing as completed with reduced scope.