mirror of https://github.com/status-im/specs.git
remove fluff
This commit is contained in:
parent
5a65cf9b90
commit
d817fb2edc
49
x7.md
49
x7.md
|
@ -9,53 +9,6 @@ created: 2019-04-18
|
|||
updated:
|
||||
---
|
||||
|
||||
## Introduction
|
||||
|
||||
## Requirements
|
||||
|
||||
TODO: Elaborate on requirement such as devp2p and possibly Whisper, and geth/parity/nimbus gotchas.
|
||||
|
||||
## Design goals
|
||||
|
||||
TODO: Elaborate on selection of design goals such as
|
||||
Privacy
|
||||
|
||||
Sender Anonymity
|
||||
Recipient Anonymity
|
||||
Particip. Anonymity
|
||||
Unlinkability
|
||||
Global Adv. Resistant
|
||||
Usability
|
||||
|
||||
Contact Discovery
|
||||
No Message Delays
|
||||
No Message Drops
|
||||
Easy Initialization
|
||||
No Fees Required
|
||||
Adoption
|
||||
|
||||
Topology Independent
|
||||
No Additional Service
|
||||
Spam/Flood Resistant
|
||||
Low Storage
|
||||
Low Bandwidth
|
||||
Low Computation
|
||||
Asynchronous
|
||||
Scalable
|
||||
|
||||
NOTE: We are probably not fulfilling all of these very well, and this is something we can note as well. "Ideally such a layer would provide...currently this isn't doing and we are doing further research into better options."
|
||||
|
||||
|
||||
# Raw import from previous document
|
||||
|
||||
**TODO: Specify transport privacy through Whisper and guarantees**
|
||||
|
||||
See https://notes.status.im/sDKuBAiPSH6iB9cFmEKLyg?both# for things that we want to capture here.
|
||||
|
||||
*NOTE: Using Adam's initial spec as a starting point*
|
||||
|
||||
**TODO: Remove non transport privacy layer aspects here**
|
||||
|
||||
Status Secure Messaging Protocol
|
||||
==================================================
|
||||
|
||||
|
@ -585,4 +538,4 @@ For a mixnet based approach, see e.g. https://github.com/w3f/messaging/issues/22
|
|||
|
||||
- This trade-off appears suboptimal.
|
||||
|
||||
- Peer steering: https://github.com/ethereum/wiki/wiki/Whisper-PoC-2-Protocol-Spec
|
||||
- Peer steering: https://github.com/ethereum/wiki/wiki/Whisper-PoC-2-Protocol-Spec
|
||||
|
|
Loading…
Reference in New Issue