Skip to content

Keep client group membership state management #657

Description

@pdyraga

Keep client does not store information about group membership and generated keys in any persistent way. Everything is kept in memory and single client restart is enough to lose all this information.

This card covers work on introducing basic state management to Keep client:

  • group memberships should be persisted once obtained and read when the client starts
  • group key shares should be persisted once obtained and read when the client starts
  • registry of active groups should be synced from the chain when the client starts

Important technical aspects:

  • Keep client data should be stored in a secure manner (password-encrypted file?)
  • persistent storage should be quasi-transactional - update failure should not break all the other data, multiple writes should be synchronized to avoid writing garbage

This card does not cover storing the current protocol execution state.

Flowdock thread: https://www.flowdock.com/app/cardforcoin/keep/threads/hib9k937zQqi6txJyDnXYqw5fm-

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions