The safe network explained using bitcoin terminology


#1

I came to the safe network because of my interest in bitcoin. I know many others do for the same reason.

This fact, combined with the difficulty of reading the widely spread and aging documentation of the safe network inspired this blog post:

MaidSafe and the safe network explained using bitcoin terminology (original blog post)

MaidSafe and the safe network explained using bitcoin terminology (github page)

It uses bitcoin terms as ‘windows’ to observe how the safe network functions (both the similarities and the differences). This hopefully makes it more comfortable for bitcoiners to approach and appreciate the safe network. I’ve found the safe network is a distinctly exciting innovation unlike the standard blockchain competitors, and want to share it with people who are most able to appreciate it.

There’s a lot of information there, about forty individual topics are addressed. It would be great if people could provide feedback and corrections before I show it to the bitcoin community.

For sake of a preview, here is the first topic:

Blockchain

The blockchain is the most important innovation of bitcoin. The purpose of the blockchain is to achieve consensus for the state of data in the bitcoin network.

The safe network addresses the same problem as the blockchain, namely that of consensus, but does not use a blockchain. The major innovation introduced by the safe network to solve the consensus problem is called ‘close group consensus’.

With bitcoin and blockchains, every node of the network has a full copy of all data on the network. As new data is added to the network, every node keeps a copy of that data.

Safe keeps only six copies of each piece of data on the network. Each piece of data is allocated a group of 32 nodes by the network to keep watch over the integrity of that piece of data. Changes to that data can only be made if there’s consensus by 28 of the 32 nodes as to the true state of the data. Because only that relatively small group of nodes must agree on the true state of the data, safe is much more efficient than bitcoin.

There is some doubt about why 32, is this secure, why not more, why not less? Rather than jump to deriving this number by proof, take a moment to consider what is being achieved by the consensus rules of both bitcoin and safe: data should not be vulnerable to being lost, corrupted, or incorrectly modified. If those 32 nodes can be manipulated (hacked or bribed etc), the data they control would not be considered secure. This concern is addressed by the first part of the phrase, ‘close’ group consensus.

Closeness is the algorithm which determines how the group governing each piece of data is formed. Members of this group are chosen by the network in a way that is very difficult to manipulate (the difficulty of doing this, like bitcoin, changes depending on the size of the network, becoming harder as the network grows). Rather than go into the details of the close group consesus algorithm here, I would instead recommend reading about xor distance as used by the safe network and follow the information trail from there.

To directly compare the language for the security of the bitcoin vs safe network, bitcoin is secured by ‘proof of work’, safe is secured by ‘close group consensus’.

For more reading about consensus using close groups rather than a blockchain, it’s worth reading Consensus Systems on the maidsafe blog.

In the same way the blockchain was the key innovation that allowed the realization of bitcoin, close group consensus is the key innovation that allows safe to provide the same functionality but with vastly improved efficiency.

If you want to contribute to this documentation it’s open source on github, so changes or additions are easy to make. Please see the readme for information about contributing.


How confident are you that Maidsafe will deliver?
Is SHIFT a competitor of SAFE?
Blockchain Vs Safe Network.(Smart Contracts)
MaidSafe Dev Update - June 22, 2017
Investment Research Report on Maidsafe - Questions
#2

It’s basically a new version of the internet, replacing layers 3-7 of the OSI network model.

Oh yeah. Still reading through, but dude, you’ve really got a good handle on the Network’s basics.


#3

It is 6 copies grouped in 3 address groups


#4

Thanks, fixed.

(twenty characters)


#5

Wow! impressing! give me some time to read it Oo xD just getting up and need some coffee! but first impression: amazing


#6

:slight_smile: this looks great, can’t wait to read… great effort !


#7

Holy crap, this is great stuff!!!


#8

This is a great write-up.

Nice job.


#9

Brilliant piece of work that explains a lot of detail. I feel this can be updated as we move forward, but what a great overview, better than we have done so far I would say (easily) and exactly what bitcoin folks are looking for. Nice balance as well.


#10

This is some seriously good stuff - nice work!


#11

Amazing work. We needed something like this.

And just in terms of website functionality, I think your page would really benefit from a button that stays with you and redirects to the table of contents at the top of the page, because I would read a topic I found interesting, and then have to scroll up for a few minutes straight every time, to get back to the table of contents.

I have a few tools in mind that I use if you want links


#12

Thanks for the suggestion.

I added a ‘Back to Table Of Contents’ link at the end of each section which takes you back to that part of the TOC. Unfortunately the platform used for this post (svbtle.com) doesn’t allow custom styles, so I can’t add a link that follows as you scroll. If you know a way to add it, send me a message.


#13

Can we get a community-run version of this site? I think the instance I’m reading is hosted on your blog?

Can we start a Github-pages version, so anyone can add to it?

One part in particular I’d like to see added to is the “Mining Centralization.” it has no mention of MaidSafe’s plans to allow decreasing rewards after Providing 20% above average resource to the network, which is pretty crucial. The section mostly paints a very worrysome picture for SAFE by not including this


#14

Great idea. If the community can decide on a place to host it I will gladly provide the source markdown and remove the content from the blog, instead linking it to the community page (a single source of truth is best!!).

I think github is a good place to host since it clearly retains the history of edits. Maybe the safenetwork wiki? I’ll leave it to the community to decide, since that’s where most of the edits will come from.


#15

Have you heard of Github’s open source website hosting service: “Github-pages” ?

It’s free and I use it a great deal. It’s awesome and you can grant specific other people, or everyone, access to the “pages” (website) branch and they can push / pull commits that directly update the website


#16

Yeah I use github.io for some other projects. I think this is a good approach.

edit:

I made a github page, still very rudimentary but at least contributions can easily be made.


#17

Are you able to elaborate on this a bit? I haven’t come across this in my reading so far (or at least don’t remember it if I did).


#18

Thanks for spreading the word! :slight_smile:


#19

This is a function called a “sigmoid curve”

https://blog.maidsafe.net/tag/farming/


#20

@mav awesome job, loved to read it. Did you post it already on Reddit or some other forum? I might use it to work on the Wikipedia page.