mirror of
https://github.com/status-im/status-go.git
synced 2025-02-03 10:25:35 +00:00
db65d42912
There's only one scenario in which a `RevealedAccount` will have an empty `ChainIDs` list attached to it: When the community in question requires users to satisfy certain criteria to join, and the user's wallet does not own the necessary funds on any of the supported chains. If there are **no** permissions to join on the community, then we want to reveal all (selected) accounts with all supported chainIDs. This is necessary so that, once the community *does* become permissioned, it'll have address + chain information from all joined members. Closes: https://github.com/status-im/status-desktop/issues/11255
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.