Currently, data being replicated between wallets is not securely encrypted and signed. We are using OrbitDB to store and replicate data, but it doesn't allow removing peers. This means that even if a user revokes a device, there is no current easy way to protect new information circulating around after a rovocation.
We should research on a good strategy to tackle this problem and implement a solution.
Acceptance Criteria
[ ] Research a good strategy to stop replication on revoked devices.
[ ] Restrain a revoked device from access/publish new data.
Description
Currently, data being replicated between wallets is not securely encrypted and signed. We are using OrbitDB to store and replicate data, but it doesn't allow removing peers. This means that even if a user revokes a device, there is no current easy way to protect new information circulating around after a rovocation.
We should research on a good strategy to tackle this problem and implement a solution.
Acceptance Criteria