ObolNetwork / ObolNetwork/obol-docs
Update current exit documentation with Capella fork epoch
Open
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 27
- Forks
- 61
- Avg merge
- 1h 22m
- Merged PRs (30d)
- 2
Description
🎯 Problem to be Solved
The current exit documentation lacks specific information about using the "Capella fork epoch," which is 256 in the case of Holesky. This omission leads to issues with invalid voluntary exits, causing increased error rates and support tickets.
🛠️ Proposed Solution
- Update the exit documentation section Obol Quickstart Exit Docs.
- Introduce a subsection addressing the "Capella Fork Epoch" and its role in the exit process.
- State that the exit epoch should match the last fork's epoch to avoid invalid voluntary exits.
- [ ]Explain why aligning the exit epoch with the last fork's epoch is crucial. Provide examples for clarity.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.