mirror of
https://github.com/status-im/status-go.git
synced 2025-02-09 05:16:35 +00:00
81e279a055
This might look like a weird requirement at a fist glance. The reason this is needed, is because some message signals require admin rights to take effect (e.g. PinMessage). When messages are imported from third-party services, translated to status messages, signed by the community, and eventually distributed via the archive protocol, we need to ensure that messages signed by the community itself are considered as admin privileges as well, so they can be correctly replayed into the database.
status-go/protocol
This is an implementation of the secure transport and payloads which are a part of the Status Client specification.
This implementation uses SQLite and SQLCipher for persistent storage.
The payloads are encoded using protocol-buffers.
Content
messenger.gois the main file which exportsMessengerstruct. This is a public API to interact with this implementation of the Status Chat Protocol.protobuf/contains protobuf files implementing payloads described in the Payloads spec.encryption/implements the Secure Transport spec.transport/connects the Status Chat Protocol with a wire-protocol which in our case is either Whisper or Waku.datasync/is an adapter for MVDS.applicationmetadata/is an outer layer wrapping a payload with an app-specific metadata like a signature.identity/implements details related to creating a three-word name and identicon.migrations/contains implementation specific migrations for the sqlite database which is used byMessengeras a persistent data store.
History
Originally this package was a dedicated repo called status-protocol-go and was migrated into status-go. The new status-go/protocol package maintained its own dependencies until sub modules were removed and the root go.mod file managed all dependencies for the entire status-go repo.