Awarded a $150,000 grant by the Foundation, Sigma Prime is building the second client implementation in Rust next to Parity. The 2.0 client is called Lighthouse and though the two products are fundamentally very similar, the duplication of work is desired in where software can have bugs. Diversity allows the network to stay up when one client goes down.
This week, Sigma Prime has published their benchmark for the most recent version of Lighthouse. You can read about the benchmarks , though be warned — the results are quite technical in detail.
Most famous for their messaging platform and mobile browser specifically designed to engage users on the , it is no surprise that Status wants to contribute to the development of 2.0. Status is also developing an 2.0 client called Nimbus, and aim’s to drive mass addition of .
In their latest , Status announced that they are launching a client specific test net for the beacon chain. With all the attention on adapting clients towards the beacon chain, we might see a testnet for the public soon.
In the latest 2.0 call, Mamy from Nimbus updated us on the latest bls tests and how there is a simulation out and ready to test with plenty of validators. The github can be found .
Trinity
While the other organizations are building their clients on Java or Rust, Trinity is the only client to be written in Python. Comprised of a small, but robust team of six developers who are all contracted to work by the Foundation, Trinity is also expected to build support for 2.0 specifications. The client itself has also had over 40 other to the open sourced project.
One thing we have noticed with 2.0 is that although decentralized development can have great governance benefits, it lacks clear incentive alignment and funding structure. 2.0 might be more than a year away and delays are likely to happen. For those that support Serenity, how can we Move Forward?
Published at Wed, 03 Apr 2019 16:18:05 +0000
