Hilarious. #6 cryptocurrency NEO is just a 7-node system Uber the control of a single party, and the code isn't designed to handle even a single, benign failure.
No idea what process Weiss Ratings uses to rate coins, but clearly, it's bunk.
If you have 7 nodes, all running exactly the same code, under the same administrator, you don't have any fault tolerance. Anyone who can compromise one can compromise all. Might as well use a single beefy server.
Replication of this kind is employed to improve liveness. The system can remain up even if a hardware failure takes out a server.
But in this case, it actually hampered liveness. The system died because just one server failed.
But in this case, it actually hampered liveness. The system died because just one server failed.
While anyone can make a mistake in an implementation, this one is far too elementary and points to a broken design and development process at NEO.
Byzantine behaviors, message reorderings, quorum membership changes, these are hard to test.
A simple 1-node failure is trivial to test. There's no excuse for a broken system as a result of a single fail-stop failure.
A simple 1-node failure is trivial to test. There's no excuse for a broken system as a result of a single fail-stop failure.
Chances of NEO NOT being broken right now: 0%
It takes time to build and test a BFT protocol, as should be evident from the thread. Takes time to go from a synchronous network assumption to an asynchronous network. There's no way that happened in a few days. Caveat investor.
It takes time to build and test a BFT protocol, as should be evident from the thread. Takes time to go from a synchronous network assumption to an asynchronous network. There's no way that happened in a few days. Caveat investor.
