ObolNetwork / ObolNetwork/charon-distributed-validator-node
Show distance to activation when known
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 91
- Forks
- 235
- Avg merge
- 1h 42m
- Merged PRs (30d)
- 1
Description
🚀 Feature Request
Problem to be solved
When a validator deposit of the full 32 ether is recognised on the beacon chain after 2048 blocks on the eth1 side have passed, the validator is assigned an index and enters the activation queue.
Proposed Solution
Use this index, and the validator index of the most recently activated validator to display the distance to the front of the activation queue.
Describe alternatives you've considered
Comparing validator index to total active validators. This isn't accurate as there are 5.5k voluntarily exited validators already, so we would think the queue is longer than it actually is.
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
The issue names no files, tests, or entry points. Start by locating where validator deposits are recognized and activation-queue data is exposed, then trace how the most recently activated validator is identified. Done means displaying the distance to the queue front when both validator indices are known.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- blockchain
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100