<= Back to FRONT

Furthermore, understanding which features are at the core, and which are higher level or add-ons will help to focus development and create a stronger foundation made to last. The separation between core goals and non-core goals is unofficial, but an attempt to rank the importance of features.

The primary goal of SAFE Network is becoming completely autonomous; impossible to change, break or stop by any single entity or group of actors.

The first iteration of the SAFE Network will achieve the following core goals (discussion):

1. de-centralize ownership of certain network functions so that they cannot be changed or disabled by any group of actors(*3)
   1. function: identity proofing
   2. function: access control
   3. function: communication
   4. function: information storage
2. protect all information perpetually(*1) from unpermitted access, interception, tampering or deletion
3. preserve stored information, and end-to-end communications, and global access to these perpetually(*1) and for free(*2)
4. provide a digital medium of exchange

• (*1) The meaning of perpetual is not clear yet. 30 years?
• (*2) Free, except for the cost of broadband access and the user terminal.
• (*3) That the threshold is to making changes is unclear yet. A majority?

A future iteration is expected to achieve the following additional goals

1. function: computation

Trustless network, autonomous network, and de-centralized network may be very similar ways to express the same goal.

Certain goals not included in the previous section, but on the roadmap, could be considered non-essential, or merely good-to-have. This is a list of such goals, and is subject to change:

1. multiple identities
2. de-centralized name resolution
3. CLI interface and API

1. SAFE Browser
2. Language bindings

1. RDF Format

Benefits will be the results of SAFE Network achieving its goals. Many individual benefits may not be unique to SAFE Network, but the combination of a large number of them might be.

1. No censorship
2. Perfect privacy
3. Full control over own data
4. No loss of data or access issues ever
5. No loss of ability to communicate ever
6. Always on; 100% availability

1. No transaction fees
2. Anonymous and untraceable transactions

Does permanent availability of published data not contradict having full control over own data?

1. No need to implement and maintain reliable data storage
2. No need to implement and maintain basic security measures
3. No need to implement authentication
4. Get paid for development of software
5. Inherently scaling storage infrastructure

1. Scalable immutable transaction ledger
2. Scalable cryptocurrency (without a block chain)

1. Consensus at low power consumption
2. Secure cryptocurrency at low power cost (in contrast to PoW)

This is intended to be an immutable record, allowing over time a comparison of prediction to actual. Official Project Roadmap and a summary:

• Alpha 2 - Live - Interact with a network of MaidSafe vaults using SAFEBrowser - PUT limits apply, minimum forum membership level required. Data will not be carried forward to next releases.
  • Self-Authentication - logging into network without centralized permissioning
  • Self-Encryption - splitting files into chunks, hashing, encryption
  • Disjoint Sections - splitting (and combining/) sections based on network size
  • Message Relay - early iteration - messaging capability without signature verification

• SAFE Fleming - A guess August 2019 - PARSEC, Node Ageing, Secure Messaging, and potentially (!) vaults at home and test SafeCoin. Since then, there was a staff reduction in 2019. Actual delivery of a first Fleming testnet was in April 2021, but with more features than initially planned. Since the staff reduction, the focus has been on “feature completeness.”

• SAFE Maxwell - A guess May 2020 - The scope was TBD but could include: test SafeCoin, wallet, vaults at home, farming, identity management, spam handling. This was the plan before the staff reduction.

RFC Project Board Github