Skip to content
This repository has been archived by the owner on May 23, 2023. It is now read-only.

The new opcodes introduced in Constantinople are not supported #897

Open
HarryR opened this issue May 29, 2019 · 0 comments
Open

The new opcodes introduced in Constantinople are not supported #897

HarryR opened this issue May 29, 2019 · 0 comments

Comments

@HarryR
Copy link

HarryR commented May 29, 2019

As per title, see: https://blog.ethereum.org/2019/02/22/ethereum-constantinople-st-petersburg-upgrade-announcement/ - the relevant EIPs are:

Newer versions of the Solidity compiler emit the 0x1c (SHR) opcode as part of the prelude, however it's not possible to run these contracts using PyEthereum. I am using ethereum.tools.tester because it allows me to test Solidity code directly from within Python without any other dependencies.

Furthermore, PyEthereum doesn't seem to have any support for Constantinople, aside from brief mentions in config.py, messages.py, state.py and test_blocks.py.

And neither does PyEthereum have any mention of Byzantium. What is the best course of action here? I would love to be able to keep using PyEthereum, especially for its ethereum.tools.tester.

eth-tester v0.1.0-beta.39 supports these new opcodes, as does PyEVM.

Does this mean that PyEthereum is currently unmaintained? Or should be refactored to use eth-tester and PyEVM as dependencies instead?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants
@HarryR and others