Files
prysm/specrefs
Justin Traglia 31f77567dd Add a README for specrefs (#16302)
**What type of PR is this?**

Documentation

**What does this PR do? Why is it needed?**

This PR adds a basic README for the specrefs.


**Acknowledgements**

- [x] I have read
[CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md).
- [x] I have included a uniquely named [changelog fragment
file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd).
- [x] I have added a description with sufficient context for reviewers
to understand this PR.
- [x] I have tested that my changes work as expected and I added a
testing plan to the PR description (if applicable).
2026-01-29 20:36:29 +00:00
..
2026-01-07 16:48:50 +00:00
2026-01-29 20:36:29 +00:00

Specification References

This directory contains specification reference tracking files managed by ethspecify.

Installation

Install ethspecify with the following command:

pipx install ethspecify

Note

You can run ethspecify <cmd> in the specrefs directory or ethspecify <cmd> --path=specrefs from the project's root directory.

Maintenance

When adding support for a new specification version, follow these steps:

  1. Change directory into the specrefs directory.
  2. Update the version in .ethspecify.yml configuration.
  3. Run ethspecify process to update/populate specrefs.
  4. Run ethspecify check to check specrefs.
  5. If there are errors, use the error message as a guide to fix the issue. If there are new specrefs with empty sources, implement/locate each item and update each specref source list. If you choose not to implement an item, add an exception to the appropriate section the the .ethspecify.yml configuration.
  6. Repeat steps 3 and 4 until ethspecify check passes.
  7. Run git diff to view updated specrefs. If an object/function/etc has changed, make the necessary updates to the implementation.
  8. Lastly, in the project's root directory, run act -j check-specrefs to ensure everything is correct.