edited

This comment has been minimized.

Note that one important issue with this hard fork is that we are most likely to discontinue multi-geth and go-ellaism support. Parity may be the only full node implementation that we're able to support. This is just due to limited manpower and we need to make sure people using the network are able to switch to Parity.

This comment has been minimized.

edited

We're having a small opinion poll created using CarbonVote. Note that we're not doing a plurality vote here. The voting is not to divide the community, but to bound it together. The intention is that everyone can learn about other people's opinion, and we can collectively decide a path forward that's beneficial for most people. The vote is non-binding. Core devs and community members may call off the hard fork if it turned out to be contentious, or may carry on the hard fork even if it does not have majority vote, but it is up to everyone whether to follow them or not. The vote poll is open from April 30, 2018 till the date of hard fork.

The vote is about Do you support enabling WebAssembly scripting as described in 2018-0003?. To cast your vote:

This comment has been minimized.

An advantage Ellaism enjoys has been the possibility of using Ethereum developers' codes and implementations. If you change this from solidity to webassembly, does it mean we will be on our own or we can still use Ethereum stuff? Especially since great things such as sharing and plasma are in the pipeline.

This comment has been minimized.

@mohsenghajar We can still use Ethereum stuff. WebAssembly is added to Ellaism. We don't remove anything, so all existing EVM environments continue to work as they are.

The version we proposed to add here is "pwasm" (a little bit different compared with eWASM, but they all mostly run a restricted version of vanilla WASM with metering). So in addition to reusing Ethereum ecosystem's code, with this, we can also reuse many of the development in the wider WebAssembly community.