{"id":19034,"date":"2026-04-06T03:02:40","date_gmt":"2026-04-06T03:02:40","guid":{"rendered":"https:\/\/cryptoted.net\/index.php\/2026\/04\/06\/ethereum-d%ce%bev-what-are-we-doing\/"},"modified":"2026-04-06T03:02:40","modified_gmt":"2026-04-06T03:02:40","slug":"ethereum-d%ce%bev-what-are-we-doing","status":"publish","type":"post","link":"https:\/\/cryptoted.net\/index.php\/2026\/04\/06\/ethereum-d%ce%bev-what-are-we-doing\/","title":{"rendered":"Ethereum \u00d0\u039eV: What are we doing?"},"content":{"rendered":"<p> <br \/>\n<\/p>\n<div id=\"\">\n<p class=\"chakra-text css-gi02ar\">OK so a minor update about what we are (and are not) doing here at Ethereum DEV.<\/p>\n<p class=\"chakra-text css-gi02ar\">We are, first and foremost, developing a robust quasi-Turing-complete blockchain. This is known as Ethereum. Aside from having quasi-Turing-completeness, it delivers on a number of other important considerations, stemming from the fact we are developing entirely new blockchain technology including:<\/p>\n<ul role=\"list\" class=\"css-1ars4k6\">\n<li class=\"css-0\">speedy, through a 12 second blocktime;\n<\/li>\n<li class=\"css-0\">light-client-friendly through the use of Merkle roots in headers for compact inclusion\/state proofs and DHT integration to allow light clients to host &amp; share small parts of the full chain;\n<\/li>\n<li class=\"css-0\">\u00d0App-friendly, even for light-clients, through the use of multi-level Bloom filters and transaction receipt Merkle tries to allow for lightweight log-indexing and proofs;\n<\/li>\n<li class=\"css-0\">finite-blockchain-friendly &#8211; we designed the core protocol to facilitate upgrading to this technology, further reducing light-client footprint and helping guarantee mid-term scalability;\n<\/li>\n<li class=\"css-0\">ASIC-unfriendly &#8211; through the (as yet unconfirmed) choice of PoW algo and the threat we&#8217;ll be upgrading to PoS in the Not-Too-Distant future.\n<\/li>\n<\/ul>\n<p class=\"chakra-text css-gi02ar\">It is robust because:<\/p>\n<ul role=\"list\" class=\"css-1ars4k6\">\n<li class=\"css-0\">it is unambiguously formally defined, allowing a highly tractable analysis, saturation tests and formal auditing of implementations;\n<\/li>\n<li class=\"css-0\">it has an extensive, and ultimately complete, set of tests for providing an exceptionally high degree of likelihood a particular implementation is conformant;\n<\/li>\n<li class=\"css-0\">modern software development practices are observed including a CI system, internal unit tests, strict peer-reviewing, a strict no-warnings policy and automated code analysers;\n<\/li>\n<li class=\"css-0\">its mesh\/p2p backend (aka libp2p) is built on well-tested secure foundations (technology stemming from the Kademlia project);\n<\/li>\n<li class=\"css-0\">official implementations undergo a full industry-standard security audit;\n<\/li>\n<li class=\"css-0\">a large-scale stress test network will be instituted for profiling and testing against likely adverse conditions and attacks prior to final release.\n<\/li>\n<\/ul>\n<p class=\"chakra-text css-gi02ar\">Secondly (and at an accordingly lower priority), we are developing materials and tools to make use of this unprecedented technology possible. This includes:<\/p>\n<ul role=\"list\" class=\"css-1ars4k6\">\n<li class=\"css-0\">developing a single custom-designed CO (contract-orientated) language;\n<\/li>\n<li class=\"css-0\">developing a secure natural language contract specification format and infrastructure;\n<\/li>\n<li class=\"css-0\">formal documentation for help coding contracts;\n<\/li>\n<li class=\"css-0\">tutorials for help coding contracts;\n<\/li>\n<li class=\"css-0\">sponsoring web-based projects in order to get people into development;\n<\/li>\n<li class=\"css-0\">developing a block chain integrated development environment.\n<\/li>\n<\/ul>\n<p class=\"chakra-text css-gi02ar\">Thirdly, to facilitate adoption of this technology, gain testers and spur further development we are developing, collaborating over and sponsoring a number of force-multiplying technologies that leverage pre-existing technology including:<\/p>\n<ul role=\"list\" class=\"css-1ars4k6\">\n<li class=\"css-0\">a graphical client &#8220;browser&#8221; (leveraging drop-in browser components from the Chromium project and Qt 5 technology);\n<\/li>\n<li class=\"css-0\">a set of basic contracts and \u00d0Apps, including for registration, reputation, web-of-trust and accounting (leveraging the pre-existing compilers and development tech);\n<\/li>\n<li class=\"css-0\">a hybrid multi-DHT\/messaging system, codenamed Whisper (leveraging the pre-existing p2p back end &amp; protocols);\n<\/li>\n<li class=\"css-0\">a simple reverse-hash lookup DHT, codenamed Swarm (also leveraging the pre-existing p2p back end &amp; protocols), for which there is an ongoing internal implementation, but which could end up merging or being a collaboration with the IPFS project.\n<\/li>\n<\/ul>\n<p class=\"chakra-text css-gi02ar\">We are no longer actively targeting multiple languages (LLL and Mutan are mothballed, Serpent is continued as a side project). We are not developing any server technology. And, until there is a working, robust, secure and effective block chain alongside basic development tools, other parts of this overall project have substantially lower priority.<\/p>\n<p class=\"chakra-text css-gi02ar\">Following on from the release of the Ethereum block chain, expect the other components to get increasingly higher amounts of time dedicated to them.<\/p>\n<\/div>\n<p><br \/>\n<br \/><a href=\"https:\/\/blog.ethereum.org\/en\/2014\/12\/17\/ethereum-dev\">Source link <\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>OK so a minor update about what we are (and are not) doing here at Ethereum DEV. We are, first and foremost, developing a robust quasi-Turing-complete blockchain. This is known as Ethereum. Aside from having quasi-Turing-completeness, it delivers on a number of other important considerations, stemming from the fact we are developing entirely new blockchain [&hellip;]<\/p>\n","protected":false},"author":6,"featured_media":18498,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"tdm_status":"","tdm_grid_status":"","footnotes":""},"categories":[24],"tags":[],"kronos_expire_date":[],"class_list":["post-19034","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ethereum"],"_links":{"self":[{"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/posts\/19034","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/comments?post=19034"}],"version-history":[{"count":0,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/posts\/19034\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/media\/18498"}],"wp:attachment":[{"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/media?parent=19034"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/categories?post=19034"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/tags?post=19034"},{"taxonomy":"kronos_expire_date","embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/kronos_expire_date?post=19034"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}