[ad_1]
The first post-Devcon4 Ethereum 1.x meeting presented updates from the four working groups on the initiative.
Ethereum 1.x, a proposed set of updates to the main network that occur in parallel with the research and development of Ethereum 2.0 (known as Serenity), has emerged during a series of major development meetings at Devcon4 in Prague. 1.x, in its most basic form, "will introduce important and revolutionary changes to the main network", focusing on scalability, sustainability and a better development experience.
The first 1.x synchronization meeting occurred on Friday, November 30th, and complied with the Chatham House Rule, which means that it has not been recorded or streamed, nor have the speakers been identified in the notes published yesterday. The call included updates from the four main 1.x workgroups: simulation, rental status, eWASM and chain deletion.
The simulation work group has the task of developing three configurations: a simulation structure that, when a data set is entered, produces an output to estimate the properties of the proposed changes (such as reducing the speed of zeal and increases in the gas limit); an emulation structure that alters environmental conditions to test the properties of the changes launched; and a testnet that starts these changes together on the same network. This simulation platform, so to speak, aims to provide information to community members on project progress.
During the meeting, the simulation group reported some progress, but did not complete any of its simulation parameters. The members of the group mentioned in particular Whiteblock, an emulation framework on which they worked, but are still determining the specifications for. In addition, I am about to collect the data sets for the simulation.
The state-owned working group deals with the implementation of a storage system for EDCC (aka smart contrac)t) data on Ethereum. In theory, a renting mechanism would help manage the ever-growing status of Ethereum, which includes data from every EDCC deployed on the network. With the emergence of Dapps left and right, however, this state has grown considerably, making it difficult and time-consuming for node synchronization.
In the meeting, the idea of a stateless contract was addressed as an alternative solution to the problem of storage. According to this mechanism, portions of the EDCC data would have been moved from the chain, even if a main developer noticed that it should have been a subprotocol dedicated to the delivery of off-line contract data.
The final group, chain pruning, tries to put a limit on the growth of the storage of Ethereum data. Part of the proposal includes the cancellation of blocks, registers and historical indices. Group members noted during the synchronization that if Ethereum were growing at the current rate, 91 GB would be added each year to conservation, although individuals were ambivalent about the implications of this growth rate and how to curb it, one speaker said the majority of users of Ethereum do not necessarily care about historical data, therefore the deletion of such information could be performed in a feasible way (although, as indicated by another participant, an agreement on a data retention policy would be necessary) .
It is important to note that the 1.x initiative, despite the progress made so far, remains a work in progress. There is no guaranteed roadmap for updates.
Daniel Putney is a full-time writer for ETHNews. He graduated in English at the University of Nevada, in Reno, where he also studied journalism and queer theory. In his spare time, he writes poetry, plays the piano and dances on fictional characters. He lives with his partner, three dogs and two cats in the middle of nowhere, Nevada.
ETHNews is committed to its editorial policy
Do you like what you read? Follow us on Twitter @ETHNews_ to receive the latest Ethereum 1.x, Ethereum 2.0 or other news on the Ethereum ecosystem.
[ad_2]
Source link
