<\/p>\n
Metropolis is at long last (nearly) upon us! The fork for Byzantium, the initial and more substantial segment of Metropolis, was successfully executed on the testnet over two weeks ago, and the anticipated date for the fork on the mainnet has been scheduled for block 4.37 million, expected on Oct 17. New attributes encompass opcodes like REVERT and RETURNDATACOPY, along with precompiles that can aid in supporting a diverse range of cryptographic algorithms. Concurrently, enhancements to Ethereum core code, Whisper, Swarm, and Ethereum\u2019s forthcoming scaling strategies have also been occurring.<\/span><\/p>\n <\/p>\n The research group has onboarded one full-time new developer and one part-time to Viper, with a growing number of community contributors. Features currently in development include:<\/span> cpp-ethereum<\/b> Progress is being made in synchronizing with the test and main networks. Currently, cpp-ethereum can <\/span>import warp snapshots <\/span><\/a>and proceed with syncing from the snapshot block. The implementation of Byzantium has been completed. Since the previous roundup:<\/span><\/p>\n Since the last roundup, Geth experienced a <\/span>significant release (v1.7.0)<\/span><\/a> followed by a <\/span>maintenance release (v1.7.1)<\/span><\/a> primarily aimed at the imminent Byzantium hard fork (enabled for all networks as of v1.7.1).<\/span><\/p>\n <\/p>\n Alongside Byzantium, several features have been finalized (some of which you may have noted in the <\/span>v1.7.0 Megara blogpost<\/span><\/a>):<\/span><\/p>\n <\/p>\n Several key features we are presently developing (but may require some time due to Devcon preparations) include:<\/span> \u00a0 Numerous bug fixes have also been integrated into both releases, which you can glance through at the GitHub milestones for <\/span>v1.7.0<\/span><\/a> and <\/span>v1.7.1<\/span><\/a>.<\/span><\/p>\n <\/p>\n \u00a0<\/p>\n <\/p>\n Testing<\/b><\/p>\n <\/p>\n Test scenarios for Byzantium are prepared and some clients have successfully passed all of them. Following the last round up, we:<\/span><\/p>\n \u00a0 Yellow Paper<\/b><\/p>\n <\/p>\n \u00a0<\/p>\n <\/p>\n All Byzantium modifications<\/span><\/a> have been recorded on pull-requests. The next concern to resolve is the handling of the empty account states on precompiled contracts, where different clients behave differently. <\/span>A GitHub issue<\/span><\/a> has been established to discuss this matter.<\/span><\/p>\n <\/p>\n Formal Verification<\/b><\/p>\n <\/p>\n @pirapira presented talks at the <\/span>ARM Research Summit<\/span><\/a> and at <\/span>TU Berlin<\/span><\/a>. We have implemented <\/span>RLP in OCaml<\/span><\/a>, accessible with opam install rlp.<\/span><\/p>\n <\/p>\n Bamboo<\/b><\/p>\n <\/p>\n We have commenced<\/span> drafting a specification<\/span><\/a>. External interfaces are <\/span>currently being developed<\/span><\/a>.<\/span><\/p>\n <\/p>\n EVM 1.5<\/b><\/p>\n <\/p>\n Solidity assembly can now accommodate <\/span>EIP #615<\/span><\/a> opcodes for subroutines and the like, thanks to Alex. \u00a0Initial implementations ofboth EIP #615 and <\/span>EIP #616<\/span><\/a> have been composed and assessed by Andrei, and testing has commenced. Greg is preparing to present preliminary performance metrics at Devcon.<\/span><\/p>\n <\/p>\n web3.js<\/b><\/p>\n <\/p>\n The web3.js 1.0 beta has received substantial community contributions, which is thrilling as it looks like 1.0 is already widely utilized. Caution is advised while using account generation and signing features, as these have not undergone an audit. Such accounts should not store significant volumes of ether. We are presently at beta.22. If all progresses smoothly, we anticipate a 1.0.0 Release candidate by Devcon3.<\/span><\/p>\n <\/p>\n web3.py<\/b><\/p>\n <\/p>\n Recently, Web3.py introduced enhancements and features, including:<\/span><\/p>\n <\/p>\n py-evm<\/b> Development continues effectively, bringing us closer to an early alpha release, which will permit running py-evm as a light client.<\/span><\/p>\n <\/p>\n Ethereum Tester<\/b> Ethereum Tester is a novel tool for Python developers aimed at providing a standard API for testing applications that engage with the EVM. The library utilizes a pluggable backend system that enables swapping the underlying VM implementation. This library can also be used seamlessly with web3.py via the <\/span>experimental EthereumTesterProvider<\/span><\/a><\/p>\n <\/p>\n Remix<\/b><\/p>\n <\/p>\n Two exceptionally important PRs have been recently implemented: (1) a terminal that enables tracking transactions and interacting with web3, and (2) a redesign of the UI.<\/span><\/p>\n <\/p>\n We are currently addressing bugs and assisting the community in adapting to this new GUI.<\/span><\/p>\n <\/p>\n Several new features are in development for release in the upcoming weeks:<\/span><\/p>\n <\/p>\n – <\/span> Highlighting of declarations and references, basic autocomplete features, and renaming<\/span><\/p>\n <\/p>\n <\/a>https:\/\/github.com\/ethereum\/browser-solidity\/pull\/819<\/a><\/p>\n <\/p>\n https:\/\/github.com\/ethereum\/browser-solidity\/pull\/806<\/span><\/a> https:\/\/github.com\/ethereum\/browser-solidity\/pull\/802<\/span><\/a> \u00a0<\/p>\n <\/p>\n Solidity<\/b><\/p>\n <\/p>\n We are nearing completion of the <\/span>new ABI en\/decoder<\/span><\/a> utilizing the Julia language. This facilitates the passing of structs and arbitrarily nested arrays through function calls. It also imposes stricter restrictions regarding invalid input data, including <\/span>invalid array lengths<\/span><\/a>. You can enable it using pragma experimental ABIEncoderV2;<\/span> With a similar directive, pragma experimental \u201cv0.5.0\u201d;<\/span> you can enable forthcoming breaking changes that we are implementing sequentially. You can now use f.selector<\/span><\/a> to retrieve the selector (also referred to as the \u201cfunction hash\u201d) of a function. Utilizing the default visibility of a function will now generate a <\/span>warning<\/span><\/a>, which should make you cognizant of <\/span>unintentional public functions<\/span><\/a>. Ultimately, Solidity is <\/span>advising<\/span><\/a> regarding (and more rigorously <\/span>enforcing<\/span><\/a> if you choose to already enable v0.5.0 features) breaches of \u201cview\u201d (previously termed \u201cconstant\u201d) and \u201cpure\u201d designations for functions. Following Byzantium, invoking a \u201cview\u201d function will utilize the new <\/span>STATICCALL<\/span><\/a> opcode and thus uphold the \u201cview\u201d attribute of the function at the VM level.<\/span><\/p>\n <\/p>\n Mist<\/b><\/p>\n <\/p>\n Launched version 0.9.1: <\/span><\/p>\n <\/p>\n \u00a0<\/p>\n <\/p>\n\n
\n<\/p>\n\n
\n<\/p>\n
\nGeth<\/b>
\n<\/p>\n\n
\n<\/p>\n\n
\n<\/p>\n
\n<\/p>\n\n
\n<\/p>\n\n
\n<\/p>\n\n
\n<\/p>\n\n
\n
\nhttps:\/\/github.com\/ethereum\/browser-solidity\/pull\/799<\/span><\/a>
\n<\/p>\n