Over the past month and a half, the Ethereum core improvement and analysis groups have been constructing upon the progress made within the final yr, and with the specter of final yr’s safety points now nicely behind us, work has begun in full power on implementing the Metropolis arduous fork.
First, ongoing progress on the collaboration with the Zcash staff and the implementation of zk-SNARKs:
On the proof of stake entrance, myself and Vlad and others have continued to solidify the Casper specification and converge on a roadmap. A key focus of our work has been on a notion of “protocol armor”, which might flip many courses of conventional Byzantine-fault-tolerant consensus algorithms into “attributable-fault consensus algorithms”, the place if there’s a protocol failure then not solely are you aware that numerous validators had been defective, however you additionally know whom responsible. The work has not but been totally written out, although it is going to be additional formalized and introduced quickly, and anybody is free to comply with alongside at https://gitter.im/ethereum/casper-scaling-and-protocol-economics.
A put up on parametrizing Casper was written right here: https://medium.com/@VitalikButerin/parametrizing-casper-the-decentralization-finality-time-overhead-tradeoff-3f2011672735
We had two core dev meetings, and have accepted the next EIPs for possible inclusion into Metropolis:
Moreover, there have been a number of adjustments to the EIP course of itself: https://www.reddit.com/r/ethereum/comments/5rp8mr/update_to_eip_ethereum_improvement_proposal_system/
Work on Mist, Swarm, ENS and related infrastructure is continuous at a speedy tempo; Swarm is now on the stage the place it might serve the pockets app, although the incentivization logic isn’t but in place.
Work on programming languages can be transferring ahead:
Work on implementations is progressing:
We want everybody a cheerful Valentine’s day!
