Skip to content

Commit

Permalink
Revise motivation section
Browse files Browse the repository at this point in the history
Prioritize the actual outcomes of the proposed features, not
first the case of interoperability.

Rel #2 (comment)
  • Loading branch information
meowsbits authored and whilei committed Feb 12, 2019
1 parent 589e463 commit 34634a1
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 1 deletion.
1 change: 1 addition & 0 deletions ECLIPs/.#ECLIP-etcbyz.md
4 changes: 3 additions & 1 deletion ECLIPs/ECLIP-etcbyz.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,9 @@ For more information on the opcodes and their respective EIPs and implementation

### Motivation

To enable and maintain interoperability between Foundation and Classic Ethereum Virtual Machines ("EVM"s). This protocol specification notably omits the scheduled features of the anticipated _Constantinople_ fork, which would be expected to include various further EVM upgrades. The reasoning for this omission hinges on a hedge toward battle-testing of those changes in light of multiple delays of that fork ([here](https://medium.com/ethereum-cat-herders/a-post-mortem-report-the-constantinople-ethereum-hard-fork-postponement-dd780d7ae63d), a postmortem of the latest delay) due to security and implementation discrepencies.
To enhance the EVM's capabilities by adding 5 opcodes and 4 precompiled contracts, all of which have been in use on the ETH network since 2017-10-16. Adoption of the "receipt status" feature provides a helpful method for Dapp developers to access the successful or failed state a contact. This would (re)establish a greater level of interoperability between Foundation and Classic Ethereum Virtual Machines ("EVM"s), and make a wider array of tooling available for the ETC network (eg. Solidity version, several contract debugging tools).

This protocol specification notably omits the scheduled features of the anticipated _Constantinople_ fork, which would be expected to include various further EVM upgrades. The reasoning for this omission hinges on a hedge toward battle-testing of those changes in light of multiple delays of that fork ([here](https://medium.com/ethereum-cat-herders/a-post-mortem-report-the-constantinople-ethereum-hard-fork-postponement-dd780d7ae63d), a postmortem of the latest delay) due to security and implementation discrepencies.

### Specification

Expand Down

0 comments on commit 34634a1

Please sign in to comment.