ObolNetwork / ObolNetwork/charon
Participation proof using prioritise
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 222
- Forks
- 138
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 35
Description
Problem to be solved
We need to track "cluster-wide agreed-upon participation" and we need a non-critical first use-case for the priority protocol.
Proposed solution
When duties expire, put the ParSignedData through the priority protocol to generate "cluster-wide green-upon participation per peer per duty per validator" and track that as prometheus metrics.
See design doc.
Out of Scope
This isn't officially related to Obol V2. It is an experiment on what is possible with the priority protocol.
Contributor guide
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 by reading the linked design doc and tracing how duties expire and how ParSignedData enters the priority protocol. The work is done when the experiment produces cluster-wide participation metrics per peer, duty, and validator in Prometheus, as described by the proposal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, prometheus
- Domain
- distributed-systems, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 22/100