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

remove principles

This commit is contained in:
Adam Babik 2019-07-10 07:09:39 +02:00
parent 2060a449d4
commit 1aa1860ab2
No known key found for this signature in database
GPG Key ID: ED02515A1FC0D1B4
1 changed files with 0 additions and 30 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
x4.md
View File

@ -19,36 +19,6 @@ TODO:
* why on Ethereum stack?
* designed for mobile from the beginning
# Guiding principles
**TODO: This needs some tweaking, as it was taken from https://github.com/status-im/swarms/blob/master/ideas/311-status-protocol.md which also includes how to work, as opposed to how the prinicples apply technically**
One way of looking at our protocol stack is as a reflection of our principles. While this isn't always true in practice right now, this is what we are aiming for, and also what we want to see in future specification proposals.
The protocol should be a reflection of our principles.
I. Liberty - enable sovereignty of individuals with things like key management, as well as economic freedom, etc, by enabling transaction of funds and socio-economic coordination between small groups of people. This also includes being coercion resistant, and not forcing updates on people.
II. Censorship resistance - enable censorship resistance through things like pluggable transports, as well as being agnostic to the information being transported.
III. Security - use state-of-the-art technologies, and research new security methods and technologies to make strong security guarantees.
IV. Privacy - protect privacy in communication and transactions, and strive to provide right to total anonymity.
V. Transparency - be open about what we are doing, allow community contributions and be clear about trade-offs.
VI. Openness - specification is open and under a permissive license.
VII. Decentralization - p2p network, maximizing number of computers/humans who can control and use the protocol we are building.
VIII. Inclusivity - easy to use our protocols, as well as working towards interopability with other protocols, and educating users.
IX. Continuance - network should be incentivized to continue on its own.
X. Resourcefulness - work with other teams to avoid duplication of effort, study prior work deeply to minimize wasted and duplicate effort.
In the following sections we will elaborate more on these.
# Protocol Layers
The Status Protocol stack consists of multiple protocols. In this document, we give a brief overview of each layer and what they provide. We also note any specific considerations when it comes to using these components together.