PARSEC
It’s called PARSEC (Protocol for Asynchronous, Reliable, Secure and Efficient Consensus) and the details of the RFC are available here 1 and today we are also releasing a corresponding Whitepaper. In addition, those looking for a higher level introduction should also check out our Medium article. We hope you enjoy reading them as much as we enjoyed working on them.

As you will find, PARSEC is an effective solution to the difficult challenge of achieving vote ordering in a decentralised network, even if ⅓ of nodes minus one are malicious. This is very interesting in itself, but when we incorporate some of the other deliverables of the Routing library, such as: Add, Remove, Split, Merge and Secure message transfer the functionality this provides is quite revolutionary.

The exciting part about these papers is that the code is already written, and some of it is running in Alpha 2!

As many have speculated, this algorithm will reduce significantly the number of testnets and code we write. Instead of huge conditional sets in our codebase, it will be reduced to this algorithm. Then adding features: add, remove, split, merge and secure message relay, Routing will be complete for Alpha 3. This marks the end of the unknowns we have to face before launch. From this point on we will be finalising Vault rules, Safecoin farming, SOLID integration and all of the client API’s and bindings.

In last week's #SAFENetwork Dev Update we promised a big announcement in routing this week, keep your eyes open to find out what's coming

It's not Alpha 3, we think it's bigger than that! Exciting news coming soon from the #SAFENetwork

All decentralised networks must overcome a fundamental problem: without centralised control how do you collectively agree on what's happening?  To do this you must have a consensus mechanism #SAFENetwork

More details to come tomorrow... #SAFENetwork

Inventor of the World Wide Web Tim Berners-Lee throws his support behind the Safe Network!

Check out his tweet...

https://twitter.com/timberners_lee

I have wanted to get Tim up to speed on SAFEnetwork for a long time, and while it was great just to have his help once we’d made contact, he is now wanting to dig deeper and has been very complimentary about the tiny contribution (in the scheme of his work and David’s work) that I’ve made the subject of my DevCon talk.

Today is the day! We will be kicking off SAFEDevCon18 here in Ayr at 9am. Join via the livestream for all today’s action
https://www.youtube.com/watch?v=8DKjsJxVdfg

Hi there - sorry I just noticed your post, I might just add a couple of words as a MaidSafe dev. Of course I am happy to have this job because the team is extremely hard working and knowledgeable, you can learn lots and lots of computer science and Rust-related things while working there. And I do think the network is feasible. What makes you believe it is not? What technical concerns do you have? I'll do my best to answer any questions you might have.

And to be honest I don't understand the claim about the "Rust community embarrasment" as I have not noticed anything like that despite being involved in the community myself. And even though someone might think that the network is not feasible - all code is open sourced and many of MaidSafe projects are not strictly confined to the SAFE network. You can use Crust, Utils, Self Encryption, and even Routing as building blocks in any Rust project and even invent your own network on top of these libraries. We also contribute to other open Rust projects, sometimes in the core projects like rust-libc, clippy, and the compiler. So why is it an "embarassment"?

Obligatory disclaimer: I'm not participating in this discussion in an official capacity and I'm not speaking for all of MaidSafe - only for myself.

EOS will launch in a few months, here’s what we know…

Around 70 days to go (June 3rd) until the EOS blockchain goes live. Over the last few weeks we learned quite some interesting details. Here are the ones I think are most important:

EOS is on schedule and will launch in June. No delays expected as all tests are going well.
EOS will support at least 1000 transactions per second at start. This is reached using a 1-core implementation. The devs expect 1 CPU-core to support up to 30K transactions per second but as security comes first the EOS Virtual Machine will scale to this number step by step...

.....

Here are some of the main things to highlight this week:

- Big news this week with the announcement of our partnership with Identillect Technologies Corp. Read more about the collaboration on the Forum2, Medium13 and our blog4.
- The Indian office is running a hackathon on the 15th of March 2018 to attract graduate developers from one of Chennai’s top colleges. We’ve launched a website18 to promote the event being held at Venkateshwara College.
- Saturday, March 10th sees the second meetup of the Kuala Lumpur group2. @dugcampbell will be calling into the meeting via Skype and we’re looking forward to an interesting chat with the community.
- The front-end team recently published a new version of safe-node-app (v0.8.0) which upgrades the native safe_app lib to the latest available version (v0.6.0).
- The SAFE Client Lib team is getting back to Java bindings and working together with the front-end team to fix some of the issues that they have discovered.
- The Routing team is currently focused on implementing a push-pull gossip protocol and carrying out evaluation work on that.
- A few members of the Routing team have also been working in the background on improving the asynchronicity of our consensus ordering algorithm for data chains.

I recently had dinner with one of the world's top Rust developers.  He had nothing positive to say about MaidSafe, implied the rest of the Rust community is embarrassed to have Maid using their platform, and confirmed our suspicion that Maid devs know their project is not feasible but are happy to get a job.

Not the best news for MAID. It is a little surprising that Bittrex still lists MANY coins that don't have a live network yet.