Ok so a minor update on what we are (and don’t do) here at Ethereum Dev.
Above all, we are developing a robust almost-associating blockchain. This is known as Ethereum. In addition to having an almost turning complete, it offers a number of other important considerations, resulting from the fact that we develop a completely new technology of blockchain, in particular:
- Speedy, through a 12 -second block;
- Light-client-friendly thanks to the use of Merkle roots in headers for compact inclusion / state evidence and DHT integration to allow mild customers to host and share small parts of the full chain;
- ÐApp-Friendly, even for light climbles, thanks to the use of flowering filters on several levels and the reception of transaction, Merkle tries to allow indexing and light newspapers;
- Finite-BlockChain-Friendly-We designed the basic protocol to facilitate the upgrading of this technology, further reducing the imprint of light and guaranteeing the mid-term scalability;
- Asic -minornaly – through the (not yet confirmed) choice of Pow Algo and the threat that we are going to pass to the POS in the not too distant future.
It’s robust because:
- It is defined without ambiguity, allowing a highly towable analysis, saturation tests and a formal audit of implementations;
- It has an extended and ultimately complete set of tests to provide an exceptionally high degree of probability that a particular implementation is in accordance;
- Modern software development practices are observed, including an CI system, internal unit tests, a strict examination by peers, a strict non-group policy and automated code analyzers;
- Its backend mesh / P2P (AKA LibP2P) is built on well tested secure foundations (technology from the Kademlia project);
- Official implementations undergo a standard standard security audit of industry;
- A network of large -scale stress tests will be instituted for profiling and tests against probable adverse conditions and attacks before the final release.
Second (and at a priority as a consequence), we develop materials and tools to use this unprecedented technology possible. This includes:
- Develop a single CO language (contractual oriented) designed to measure;
- Develop a format and infrastructure for specifying secure natural language;
- Formal documentation to help code contracts;
- tutorials to help code contracts;
- Sponsor web projects to put people in development;
- Develop an integrated development chain development environment.
Third, to facilitate the adoption of this technology, win testers and stimulate subsequent development, we develop, collaborate and sponsor a certain number of force financing technologies that take advantage of pre -existing technology, in particular:
- a graphic client “browser” (taking advantage of the components of reception browser for Chromium Project technology and QT 5);
- A set of basic contracts and ðApps, including for recording, reputation, configuration network and accounting (taking advantage of pre -existing compilers and development technologies);
- a multi-DHT / messaging hybrid system, named by code, taking advantage of P2P and preexisting P2P protocols);
- A simple search for inverse hash DHT, named Swarm (also taking advantage of the P2P protocols and pre -existing protocols), for which there is an internal implementation in progress, but which could end up merge or be a collaboration with the IPFS project.
We no longer actively target several languages (LLL and Mutan are in an inch ball, the snake is prosecuted as a parallel project). We do not develop any server technology. And, until there is a chain of work blocks, robust, secure and effective alongside basic development tools, other parts of this global project have considerably lower priority.
Following the release of the Ethereum block chain, expect the other components to get more and more time that devotes them.
