Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose and test petersburg_at and latest_mainnet_at #1787

Merged
merged 2 commits into from
Jun 4, 2019

Conversation

carver
Copy link
Contributor

@carver carver commented Jun 4, 2019

What was wrong?

petersburg_at wasn't exposed in eth.tools.builder.chain.

No easy way to use the chain builder to always test the latest VM. (Every network upgrade would require updating the tests explicitly)

How was it fixed?

Exposed petersburg_at() and latest_mainnet_at().

Cute Animal Picture

put a cute animal picture link inside the parentheses

carver added 2 commits June 4, 2019 12:45
Also, note that petersburg is the canonical mainnet VM, not
constantinople.
@@ -234,6 +237,8 @@ def dao_fork_at(dao_fork_block_number: BlockNumber,
petersburg_at = fork_at(PetersburgVM)
istanbul_at = fork_at(IstanbulVM)

latest_mainnet_at = petersburg_at
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 to not making this magic so tests don't suddenly start failing without this being updated explicitly.

@carver carver merged commit 65e9fd9 into ethereum:master Jun 4, 2019
@carver carver deleted the latest-mainnet-at branch June 4, 2019 20:36
@carver carver mentioned this pull request Jun 4, 2019
20 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants