status-im
/
specs
mirror of https://github.com/status-im/specs.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

comment out todo

This commit is contained in:
Oskar Thoren 2019-08-29 13:42:42 +02:00
parent 09a97ba436
commit 060b80ad91
No known key found for this signature in database
GPG Key ID: B2ECCFD3BC2EF77E
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
status-secure-transport-spec.md
View File

@ -135,7 +135,7 @@ In the X3DH specification, a shared server is typically used to store bundles an
- Decentralized permanent storage (e.g. Swarm, IPFS). - Decentralized permanent storage (e.g. Swarm, IPFS).
- Whisper - Whisper
TODO: Comment, it isn't clear what we actually _do_. It seems as if this is exploring the problem space. From a protocol point of view, it might make sense to describe the interface, and then have a recommendation section later on that specifies what we do. See e.g. Signal's specs where they specify specifics later on. <!-- TODO: Comment, it isn't clear what we actually _do_. It seems as if this is exploring the problem space. From a protocol point of view, it might make sense to describe the interface, and then have a recommendation section later on that specifies what we do. See e.g. Signal's specs where they specify specifics later on. -->
Since bundles stored in QR codes or ENS records cannot be updated to delete already used keys, the approach taken is to rotate more frequently the bundle (once every 24 hours), which will be propagated by the app through the channel available. Since bundles stored in QR codes or ENS records cannot be updated to delete already used keys, the approach taken is to rotate more frequently the bundle (once every 24 hours), which will be propagated by the app through the channel available.