Greetings everyone, I had the opportunity to spend some time with our Canadian colleagues in Toronto after delivering the presentation “Ethereum: The World Computer” at the Blockchain Training Conference last month, and I wanted to share a brief overview of some remarkable developments within the Ethereum development ecosystem. Numerous initiatives are in the works behind the scenes, so let’s dive in!<\/p>\n
<\/p>\n
Projects<\/h2>\n
<\/p>\n
Mist<\/h3>\n
<\/p>\n
The Ethereum wallet has undergone significant enhancements over the past several months, extending its support for arbitrary contract interaction through the “custom contracts” section. This marks a substantial upgrade compared to sending transactions via the command line, which was often necessary during Frontier. With new team members collaborating with the Ethereum Foundation, fresh versions of Mist are starting to roll out, incorporating upgrades to Geth and Eth as they are unified. If you’re utilizing an outdated version, make sure to update to Mist 0.8.0<\/a> for the latest features.<\/p>\n <\/p>\n Screenshot of Mist 0.8.0<\/p>\n <\/p>\n <\/p>\n Following extensive efforts to reorganize the C++ codebase, the CPP team has shifted focus from Mix to Remix, as the IDE is now targeting the web. Remix has reached its initial alpha phase and is available with a demo online. For additional details, visit its repository at https:\/\/github.com\/ethereum\/remix<\/a>. Generally, EVM IDEs have not gained significant popularity yet, making this a potential major advance in accessibility, similar to the way the online Solidity compiler<\/a> has. New security tools, such as EVMDIS<\/a>, are anticipated to be released to the community. Progress is also being made so that formal verification can recognize recursive call patterns. Further insights can be found in Christian’s C++ DEV Update<\/a>.<\/p>\n <\/p>\n <\/p>\n <\/p>\n Although not an official project, it is closely related to several initiatives, Nick Johnson has commenced work on the Ethereum Name Service. This involves smart contract-based resolvers with a standardized API. The specification allows delegation by name segments (separated by \u201c.\u201d) and various record types. It is feasible to create gateways to integrate with existing systems, such as DNS. Presently, a draft specification with a reference implementation available in Solidity<\/a> and discussions are taking place on Gitter<\/a>. This could have significant implications for the usability of various services on the Ethereum network, from wallet aliases to user-friendly Swarm node names.<\/p>\n <\/p>\n <\/p>\n <\/p>\n A development to monitor closely is the light-client functionality entering the public testing phase<\/a>. Zsolt has dedicated months to this coding effort, and the team is preparing to merge it into the primary repository soon. The new code trims chain synchronization time to under 30 minutes from the genesis block and under a minute for weekly usage. This builds upon the work done by Peter for the fast sync functionality that is now standard in Mist (–fast<\/span>). Additional endeavors are being made to enhance log and receipt retrieval, and various iterations of the protocol are expected over time, so this won’t be the last you’ll hear about LES!<\/p>\n <\/p>\n <\/p>\n <\/p>\n Swarm is also undergoing rigorous testing as PoC2 demonstrates economically self-sustaining storage and distribution layers. Viktor, Dani, and Aaron have been diligently working to ensure the code is as free of bugs as possible before its launch on testnet. Nick has crafted a simulation script for network and communication verification, which will significantly assist this effort. One of the notable features of their development is the accounting & incentive systems that facilitate long-term data storage and retrieval. For more information, the Swarm team has been highlighted in various YouTube videos<\/a> explaining how everything functions.<\/p>\n <\/p>\n <\/p>\n Although referred to by various names, this promotes a vision for decentralized storage where you have ownership of your data. Currently, while there are a handful of blockchain-based applications, the complete accessibility of Swarm will empower these blockchain-backed applications to transition into fully functional DApps and operate 100% decentralized within Mist.<\/p>\n <\/p>\n <\/p>\n On a collaborative front, ongoing dialogue between the IPFS and Ethereum teams may enable them to unify a protocol in the future, benefiting both ecosystems from their respective network effects. Additionally, the efforts directed at Raiden and Swarm have proven to be complementary, as both solutions aim to address similar challenges. I\u2019ve been informed that the Raiden Network can serve as a payment channel for the Swarm incentive framework, which would assist in resolving some privacy and scalability issues while enhancing their collective endeavors. Knowing that they are supporting each other amplifies my excitement for what lies ahead!<\/p>\n <\/p>\n <\/p>\n Devcon2 is just around the corner, with sessions planned for September 19, 20, 21 as part of the Global Blockchain Summit in Shanghai, China. The Ethereum Foundation’s informational website is now live at ethereumfoundation.org\/devcon<\/a> and additional details regarding the Summit can be found at blockchainweek2016.org<\/a>. Even with a larger venue, availability will still be limited, so be sure to register now!<\/p>\n <\/p>\n I hope that 2016 will be a transformative year for blockchains. The user interface and user experience are advancing rapidly compared to what was available just a couple of years ago, and with solutions like Raiden for state\/payment channels, many privacy and scalability challenges of blockchains are alleviated. Coupled with research innovations aimed at Serenity, we are on track to overcome many of the hurdles Vitalik previously identified as difficult problems<\/a>.<\/p>\n <\/p>\nRemix<\/h3>\n
ENS<\/h3>\n
![\"ENS](\"https:\/\/blog.ethereum.org\/images\/posts\/2016\/07\/Screen-Shot-2016-07-06-at-17.30.40.png\")
Diagram illustrating example ENS hierarchy with various records<\/p>\nProtocols<\/h2>\n
Light client<\/h3>\n
![\"Light](\"https:\/\/blog.ethereum.org\/images\/posts\/2016\/07\/Screen-Shot-2016-07-06-at-18.18.05.png\")
<\/a> Tweet showcasing light client functioning on an embedded device<\/p>\nSwarm<\/h3>\n
![\"Data](\"https:\/\/blog.ethereum.org\/images\/posts\/2016\/07\/Screen-Shot-2016-07-06-at-18.14.16.png\")
Data storage & retrieval in Swarm<\/p>\nIPFS & Raiden<\/h3>\n
Wrap-up<\/h3>\n
![\"Keep](\"https:\/\/blog.ethereum.org\/images\/posts\/2016\/07\/ethereum-keep-calm-and-code-on.png\")
Maintain Calm and Continue Coding
\n\u00a0<\/p>\n
\n<\/div>\n