Skip to content

Single source in-development fork name #1330

@SamWilsn

Description

@SamWilsn

tox.ini currently contains a hardcoded reference to Osaka. This'll be a problem when switching to developing the next fork.

We should single source this information, perhaps using the Hardfork class.

I'm thinking something like $ ethereum-spec-forks -n N --test-name (or whatever) where N is the fork number (0 being Frontier and -1 being the most recent).
Originally posted by @SamWilsn in #1280 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-toolArea: toolingC-enhanceCategory: a request for an improvementE-easyExperience: easy, good for newcomersP-low

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions