Ethereum (ETH) is getting ready for the next hard fork. A couple of EIPs have been implemented in geth 1.4.19 and 1.5.0 as well as latest parity.
Etherwall has been updated to include the updated clients.
Work on 2.0.0 has been delayed because I need to concentrate on personal issues right now.
Ethereum classic has decided to diverge from Ethereum on the go implementation. They have just made a new release that is incompatible to current ETH geth.
Ethcore has implemented this "divergence" into their codebase so parity remains a compatible client for both ETH and ETC.
All ETC users of Etherwall will need to supply their own geth unless the original geth incorporates these changes.
Since I do not officially support ETC with my releases I will continue to supply the ETH geth with Etherwall until version 2 with dual node support and automated client downloads.
A new fork is right around the corner. It seems both ethcore and foundation devs have decided to do a new fork to fix the DDOS issues plaguing ethereum lately.
From what I see they're doing all the old mistakes as before. They don't take the possibility of the "original" post fork chain staying seriously and don't plan to change the transaction format to prevent replays.
The fork seems to be very rushed with next Monday as the target.
I hope they reconsider, if this fork goes anything like ETC it'll be a disaster. Arguments like "nobody would stay on a DDOSable chain" just don't stand in a world of speculation and markets.
Parity has fixed the geth account import bug in version 1.3.4. I have decided to give people a choice of backend client they want to use.
This means version 2 will be delayed a bit, but it'll bring with it some new juicy features.
Etherwall v2 will also download the latest backend node binary directly without needing to do full releases each time someone hotfixes an issue in geth or parity.
Other new features will include usage of parity's trace API and tracking of "internal" contract transactions with the parity backend.
With geth having so many issues lately we have decided to switch to ethcore.io parity client.
This change will be incorporated with a migration wizard as part of the 2.0.0 Etherwall release.
The main issue blocking us from releasing 2.0.0 right now is the parity account import bug.
2.0.0 will be released as soon as ethcore team fixes this issue.
If you want to try running Etherwall with parity right now, you need to follow the steps from our FAQ page.
Version 1.4.0 is out. New features include contract deployment (from bytecode only), wallet import/export.
The feature I like most in this release is automated gas estimates. No need to fiddle with gas anymore, be it for normal sends, contract invokes or even contract deployment.
Contract invoking and watching has been implemented! This means that all the core features are implemented and it's the time to find out what the next steps are.
Vote on which feature is the most important for you:
Vote is done the results were:
2. Account import/export
3. Faster syncing
Aleš Katona is an open source contributor and author of various projects like Etherwall and Lighthouse.