ObolNetwork / ObolNetwork/obol-docs
Add Lodestar voluntary-exit command to the Obol Launchpad UI.
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
For Obol users who are using the Lodestar VC, the information should be relatively available to demonstrate how to voluntary exit validators on the Launchpad UI. It currently does not exist on the Launchpad for any of the networks as seen on the screenshot below:
The solution is within another page inside of: https://docs.obol.tech/docs/start/quickstart-exit
- Link to the codebase issue that prompted this docs change
🛠️ Proposed solution
Lodestar should be added in the Launchpad UI to demonstrate how to exit validators:
Holesky:
docker exec -it charon-distributed-validator-node-lodestar-1 /usr/app/lodestar validator voluntary-exit --beaconNodes="http://charon:3600" --dataDir=/opt/data --exitEpoch=${EXIT_EPOCH:-112260} --network=holesky --yes
Mainnet:
docker exec -it charon-distributed-validator-node-lodestar-1 /usr/app/lodestar validator voluntary-exit --beaconNodes="http://charon:3600" --dataDir=/opt/data --exitEpoch=${EXIT_EPOCH:-112260} --network=mainnet --yes
- For major overhaul of docs, design doc link:
🧪 Tests
- Netlify deployment build tests passing
👐 Additional acceptance criteria
❌ Out of Scope
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.
Research direction
Start with the Launchpad UI documentation page and the existing quickstart-exit page at docs.obol.tech/docs/start/quickstart-exit. Add the Lodestar voluntary-exit commands for Holesky and Mainnet, then verify that the Netlify deployment build passes and both networks display the instructions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100