Sale Djenic 1ae956ad3c feat: accounts improvement
- setting clock when adding/updating accounts
- syncing/backing up accounts with the time they actually were updated instead
the time when dispatching is done as it was before
2023-04-21 16:35:24 +02:00
..
2022-03-23 18:47:00 +00:00
2021-09-30 13:02:41 +01:00
2023-04-16 17:06:00 +02:00
2023-03-06 13:22:40 +02:00
2021-07-26 17:06:32 -04:00
2021-06-29 13:15:15 +02:00
2023-04-21 16:35:24 +02:00
2023-03-14 16:57:33 +01:00
2023-03-16 14:31:34 +00:00
2021-09-30 13:02:41 +01:00
2023-04-21 16:35:24 +02:00
2021-07-22 13:41:49 -04:00

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.go is the main file which exports Messenger struct. 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 by Messenger as 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.