If a third or more of the elder nodes in a section are faulty, they can break the consensus process.
There are three aspects that mitigate this risk:
The performance advantage given by gossip allows much larger section sizes
Node ageing means that there is a cost to having a faulty node in the network
Secure random rellocation means that a particular section can’t be targeted on purpose
Ah yes thank you for a quick reply, the secure random reallocation seals the deal imo, cant think of a way to get around that, despite resources…
Cheers guys, enjoy your evening and thank you all at @maidsafe for the great work!
Let’s get this to the front page of hacker news 
This is incredible. One small step for maidsafe, one giant leap for the distributed/cryptocurrency community.
Congrats to the Maidsafe team for their inspired hard work and to the community for backing the right horse. Now to poke at this over the next few days/weeks.
well done team only one thing to do tonight and that’s to get drunk 
Thank you. I’ll be smiling even more a long the way knowing the SAFE Network just took one giant leap forward towards beta and full launch. Exciting times ahead! Can’t wait to get home and start learning how I can develop on top of SAFE.
Absolutely, we believe it is almost completely asynchronous with just one caveat (a malicious scheduler delaying messages), while not an attack that matters much it can be argued there is a little bit of synchronicity. We might address that but probably do not need to. The next 2 papers should be much more relevant for fully decentralised projects or a new Internet 
In time we will swing back to that point I imagine.
The time is now for the crypto-currency community to embrace open source and professionalism. We will push to launch but there is so much here for others to work on that it would be a crime if they ignore it. Effective sharding will also help many projects and we have that in the bag. Stuff I (we ?) would love to see progress on is, full network restarts, upgrades, and interoperability of apps (like SOLID take up) and homomorphic encryption to allow shared facts without identity leaks and much more. We embrace Open Source and hope others also will as this Internet needs fixed and fixed properly before much longer.
Now I am off for a beer, a big one
And you deserve it! I’d buy you one some day!
Congratulations everyone at Maidsafe. Truly groundbreaking stuff. From POW to POS and now to PARSEC, the ongoing innovation in crypto is fantastic.
From privacy thefts to malicious third parties (and governments!) it’s clear there’s never been a more urgent need for the Maidsafe project. With this crucial piece of the puzzle solved, I can’t wait for the network to get up and running…
What a time to be alive!
I’ll brew you one!
You and the entire team deserve it. Were I in Scotland that I would cover it too.
Frankly, the work that you guys are doing is amazing. Even if most of the crypto community would rather reward blowhards at this point in time, take solace in knowing that in the end, only substance will survive. Not just survive, thrive.
We are behind you all the way. Your success means our success. When the network is ready, you will see some of what we have also been quietly building to run on top of your creation.
I’ve just read the Medium post which, considering I’m not technical, gave me a real sense of what is happening here, and I literally can’t contain my excitement.
I’ve been involved since 2014 and have never lost faith in this project nor the team behind it - so congratulations on this major breakthrough!
i seriously feel bad for all the moments that i ever doubted this project.
it hasn’t been many though, i assure you
Nice. Let’s see PARSEC in action. Good job all.
OMG this is ground breaking work! Amazing job Maidsafe!!
Just read the Medium post and it blew my mind!
Role on Alpha 3 and beyond 
So many in the crypto sphere claimed Maidsafe was a scam or that it would never work.
The naysayers have been proven wrong!
Congrats to all you genius Tesla code writers, you truly have written history!
Thank you 
i think the email in the first page of the whitepaper is wrong
∗MaidSafe Ltd., emails: firstname.lastname@maidsafe.net
Anti-spam measure presumably?
probably didnt think that 
Definitely helped, @antifragile! This concrete coin idea helped close the loop in a way that’s much more elegant than what we were considering before you brought it to our attention.
Big props 