ethereum / ethereum/execution-specs
Revisit how we implement glacier/bpo forks
Open
A-spec-specs
C-question
S-needs-discussion
stale
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 505
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 116
Description
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.
Contributor guide
Assessment
This issue has not been assessed yet.