WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

Revisit how we implement glacier/bpo forks #1837

New issue
New issue
Open
Open
Revisit how we implement glacier/bpo forks#1837
Labels
A-spec-specsArea: Specification—The Ethereum specification itself (eg. `src/ethereum/*`)C-questionCategory: this is a question or request for clarificationS-needs-discussionStatus: needs discussion
@SamWilsn

Description

@SamWilsn
SamWilsn
opened on Dec 3, 2025

Currently, constant-only hardforks (aka glacier and BPO forks) are full forks with their own directory in src/ethereum/forks/..., and they have special privileges as far as code coverage and ethereum-spec-lint go.

@petertdavies wondered whether these forks deserve a full copy of the code, and should instead be replaced with a table somewhere.

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-spec-specsArea: Specification—The Ethereum specification itself (eg. `src/ethereum/*`)C-questionCategory: this is a question or request for clarificationS-needs-discussionStatus: needs discussion

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions