The split in the Ethereum community for EIP 867

The split in the Ethereum community for EIP 867

Representatives of the ethereum community began to actively speak out against the recent proposals for improvement, which describes a mechanism for the return of funds after the loss or theft.

After leaving one of the developers, Yoichi Hirai, the community members literally stormed Github leaving negative comments under the proposal EIP 867.

Over the last 24 hours there were over 80 comments, most of which commentators speak out against EIP 867.

The question about what to do in case of loss or theft often arises with users of ethereum. It is because of this incident and appeared at the time cryptocurrency – ethereum classic.

Interestingly, the dismissal Yoichi Hirai, obviously served as a catalyst for discussion, as in the beginning of the week, offers almost no comments (when compared with the situation today).

In the comments users describe EIP 867 as something “very dangerous”, “a terrible thing”, and one commentator writes that it “goes against everything that I was thinking about this movement.”

It is worth noting that at a meeting of developers last week, one of the developers of ethereum, Vlad Zamfir mentioned the need for feedback from the community on this issue, stating that the EIP 867, perhaps, too important to work through the normal process of the EIP.

Another issue is that concerning the status of the proposal there is some confusion here. The proposal has appeared as a issue (problem) and then its status was changed to a pull request (request for performance). This status means that the code EIP 867 will soon become part of the core ethereum code.

James levy of the Tap Trust, one of the three developers, in charge of the work on the proposal, closed the issue on Github in the midst of a discussion last night, and many have begun to think that EIP 867 is no longer active.

However, to date the corresponding request for execution is still open and feedback is still coming in.

News tags
Let's Disqus