We already store messages in the redux store after receiving them from OrbitDB, so until we prioritize work to move from the redux store to a better local storage solution we should just decrypt during the replicate and replicate.progress events in storage.service:subscribeToChannel and pass the decrypted message to the redux store. We can maintain a queue of messages that failed to decrypt in LevelDB until we have a better solution.
Acceptance Criteria
Messages are decrypted in backend when replicated from OrbitDB and passed to Redux
Messages which fail to decrypt are added to a queue and checked when the lockboxes a user can access change
Description
We already store messages in the redux store after receiving them from OrbitDB, so until we prioritize work to move from the redux store to a better local storage solution we should just decrypt during the replicate and replicate.progress events in storage.service:subscribeToChannel and pass the decrypted message to the redux store. We can maintain a queue of messages that failed to decrypt in LevelDB until we have a better solution.
Acceptance Criteria