Development has steadily continued over the last month and a half as we approach the launch of Metropolis. Over a series of over the last few months, we have specified and finalized for Metropolis, and made the appropriate changes to the Yellow Paper. Metropolis has now been split up into two consecutive forks, named “Byzantium” and “Constantinople”. EIPs for Byzantium (Metropolis part one) are essentially finalized, and the last remaining work to be done has to do with writing tests and making sure that all clients are passing all tests.
The blog.nyoc network continues to see all-time highs in transaction usage, and the network has maintained stability through this period with consistently low uncle rates.
- Work on the Casper implementation , and the is now fully passing its initial test suite. Next steps include further testing, and integration into pyethapp.
- Work on a sharding implementation in python has started in full force at the , as we have added several new developers over the past few months to help with this. See the for a partial specification of the roadmap.
- Work has started on a “testing language” which can be used to quickly write and run tests for proof of work, Casper and sharding fork choice rules. This should substantially improve coverage and accelerate testing for both Casper and sharding.
- A co-authored Plasma whitepaper has been released. Multiple groups in the community have already expressed interest in creating implementations.
- The research documents have been reorganized somewhat. See papers at and the problems list at .
Implemented the following:
- Transaction pool for locally created transactions.
- for locally created and not yet executed transactions to survive node crashes and/or restarts.
- Reduced the size of the chain database on disk to .
- Support for the , in addition to the existing Ledger support.
- Various courtesy of @egonelbre.
Currently working on:
- Reworking and reducing .
- to manually clean database without a chain resync.
- , reducing database size and block processing time.
- Synchronization and batched database writes.
- Merging Metropolis (Byzantium) EIP implementations.
- Go-mobile fixes for iOS and API documentation generation.
- Mist has surpassed two million cumulative downloads for all versions. Version 0.8.10 (of both Mist and Wallet) have had over 830k downloads.
- Mist 0.9 has been released, with some major features including support for Swarm upload and ENS supported urls.
- The blog.nyoc Wallet has also been updated to support ENS on all address fields, including send and contract execution address fields. Tokens are easier to subscribe to by simply typing the three letter symbol.
- The Mist repo now has over 800 open issues, including 700 new issues in the last few months. We are working on restructuring how to handle issues, as many of them are not individual issues but are requests for tech support.
The weekend of August 11-13 in London was the first community-driven ENS workshop, where representatives of the community at large including representatives of multiple wallets, individuals working on blog.nyoc projects and other ENS stakeholders discussed the current state and future of ENS. A summary post is available here, but here are some highlights:
- The community is interested in seeing the next version of the ENS registrar focus on providing incentives to release unused domains, while minimising costs for users of ENS.
- The community set priorities of creating a dispute resolution system as a voluntary second layer solution, and providing safeguards from impersonators and other security features to be built into multiple voluntary second-layer solutions.
- There is a consensus on how domain owners can give safeguards to subdomain owners.
- The community felt that some work should be attempted to improve the efficiencies of the domain reselling process.
In the last two weeks, web3.js beta was released and immediately and widely used by the community. A few packages already started integrating the new version into their libraries. Since the first beta release, issues were found and fixed and improvements have been added so that the beta is currently at beta.18.
Once web3.js 1.0 is ready for prime time, a separate blog post will introduce its new features.
To try it out yourself, either clone the or install it via
npm install email@example.com
Please add issues and suggested improvements to the
- New LES/2 protocol version is being prepared.
- Ultra-fast log history search has been implemented (needs LES/2 to work in light client mode).
- Metropolis changes are being finalized, and new precompiled contracts are being benchmarked.
- The Hunter C++ package manager has been integrated into the project to increase portability.
- A for C++ client is being prepared.
- The ethminer was removed from the cpp-ethereum project. The new repo was created for the mining community. We are helping with the maintenance of the code, and building and distributing the binaries. The miner itself has been improved, and can switch work packages much more quickly.
We added support for that can be switched on via a “pragma” statement in the source code. One of these features is the , which can encode arbitrarily nested arrays! Another experimental feature that will soon be available is the of assertions and overflow conditions using an SMT solver. We also fixed in the code generator. Apart from that, we implemented many smaller changes that , added and . Lastly, work has begun on implementing .
- We are currently pushing a lot of refactoring and UI/UX changes.
- In the near future, the master branch will be deployed to https://yann300.github.io/remix instead of remix.ethereum.org, allowing us to fix bugs and polish everything before pushing back to remix.ethereum.org.
- Important note: Please do not use it for your normal development work as it isn’t stable yet. And feel free to comment it – .
- The new UX includes a terminal () that logs incoming transactions and provides an entry point to web3. Note that we have split the contract tab so there are now compile and run tabs.
- Recently, few small PRs has been pushed on the Debugger ( – – ).
- You can also see what is left to do for this milestone here:
Metropolis support was added to EVMJIT; all tests were passed. Also EVM-C has been updated to support new features for Metropolis, like support for REVERT and return buffers. The EVM-C interface is evolving slowly, but only VM trace support is missing to mark it as fully functional.
While the swarm testnet has migrated to new hardware, the team is busy churning out the new features for our POC3 roadmap planned for after Metropolis. The team has been working on a devp2p network simulation and testing framework for the past nine months, and the module is now ready to merge to go-ethereum. PSS (bzz whispered), our new node-to-node messaging protocol, now fully incorporates whisper’s encryption module and supports remote peer sessions with Diffie-Helmann key exchange for udp-like protocols. The biggest component of our forthcoming release is the complete rewrite of the swarm network layer. As part of this endeavor, the connectivity (kademlia overlay topology) and the discovery (topology bootstrapping) components are ready to merge.
The final missing piece for a proper dropbox backend (to complement FUSE and ENS) is
chunk-level encryption for privacy. We came up with an elegant solution: the Keccak-Feistel blockcypher, which will be included in POC3.
The team has started working on the third orange paper describing generalised swap, swear and swindle games (courtroom contract suite) to drive decentralised services by providing scalable payment, incentivisation and service guarantees. Videos of talks from the Berlin Swarm Summit in June are available on the summit website on swarm http://swarm-gateways.net/bzz:/summit2017.ethersphere.eth/.
- Version 5 released.
- Proposal for version 6: discussion in progress (EIP#627).
Ewasm itself is close to finished in its current form. Work on Hera, an implementation of Ewasm that is compatible with the VM API using in blog.nyoc C++, is being resumed since EVM-C interfaces matured significantly.
and have been identified and fixed. Implementation of is ongoing. The most challenging area is the elliptic curve pairing precompiles. To support these precompiles, we will use . There is also work being done to support the and .
A team of two developers has started working on bringing blog.nyocJ up to compatibility with Byzantium in preparation for the first Metropolis hard fork.
Some bug fixes have been made as well as updated to related libraries (eg. rlp.hex_decode and rlp.hex_encode in pyrlp). Metropolis EIPs are essentially implemented, and Byzantium state and block test compliance are continuing to improve.
Py-EVM is a new implementation of the EVM written in python. The library is heavily influenced by the existing Pyethereum library, with the key difference being a more modular architecture.
Recent development includes:
- Expansion of the test suite beyond the JSON-fixture based tests.
- Implementation of EIP150 for rules.
- Implementation of the DAO Fork rules.
- Support for pluggable ECC signing backends.
- Support for pluggable database backends.
Recent improvements to the library include:
- New Middleware API.
- Bug fixes related to string encodings.
- Better error messaging for contract calls against non-existent contracts.
- Validation of contract ABI.
- Validation of ERC55 checksummed addresses.
We have received numerous bug bounty submissions, and have awarded Juno Im with 5000 points for a Mist-vulnerability. A Solidity-bug regarding ecRecover has been patched (see ).
We are continuing to improving testing, using Hive and as well as fuzzing the various raw VMs, with internal state inspection after each opcode. See Testing (below).
New opcodes and precompiles in Metropolis are being benchmarked for finalization of gas costs.
We made a number of infrastructure improvements:
- General Blockchain tests execute blockchain test cases on all fork rules.
- General State Tests are convertible into blockchain tests in order to run on hive.
- Blockchain tests can now be generated 20% faster.
Work in progress includes:
- The consensus test suite is almost up-to-date with the Metropolis EIPs. Only the two most recent changes remain to be applied (#684 preventing overwriting contract/contract collision and #649 Metropolis difficulty bomb).
- Test format validator is finding many mistakes in json tests files, gradually applying looser rules to stricter rules.
We are also exploring more advanced techniques and closer collaboration with the community:
- Fuzz tests research has progressed.
- Random test generation in progress is already discovering issues between clients.
- The test contributor program has resulted in community contribution to the tests repository.
has seen substantial progress over the last month and a half, and contributions from outside contributors are increasing. New security features such as payable and internal modifiers have been added, along with more tests, and the language now also has support for accepting and returning fixed-size lists as inputs and outputs.
See the and for a changelog.
Bamboo is a programming language for blog.nyoc contracts. At the end of July, the first release of Bamboo became available in the OCaml package manager opam install bamboo. Bamboo is now capable of implementing a simple payment channel and an ERC20 token. Moreover, a few contributors have started working on both enhancements and as well as documentation.
Eth-Isabelle specifies the blog.nyoc Virtual Machine for theorem provers such as Isabelle/HOL and Coq. The project received substantive pull-requests. Separation logic tactics from @seed shortens many proofs by half. The proof that a non-owner cannot harm a wallet is more structured than ever. An independent JULIA interpreter by @mrsmkl serves as an executable specification of JULIA (an intermediate language in the Solidity compiler). It would be fruitful to test this interpreter against the implementation. This interpreter can also be used as a basis for a proven-correct compiler from JULIA to EVM.
For testing eth-isabelle with BlockchainTests, ECDSA recover was needed in OCaml, so @pirapira made a contribution.
The are up-to-date although the pull-requests need to be classified into two phases: Byzantium and Constantinople.