ObolNetwork / ObolNetwork/charon-distributed-validator-node
keep nimbus vc database
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 91
- Forks
- 235
- Avg merge
- 1h 42m
- Merged PRs (30d)
- 1
Description
🎯 Problem to be solved
every time that we update the nimbus validator client the validator database is lost. See potential solution here to avoid having to build docker images and to allow the vc database to persist between updates:
https://github.com/ObolNetwork/charon-distributed-validator-node/pull/476
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
Review PR #476 and the repository's Docker Compose setup first, since no file or test is named in the issue. Trace how validator-client updates handle the validator database, then verify that updating the client preserves the existing database without rebuilding Docker images.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, shell
- Domain
- databases, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100