Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Participation proof using prioritise #1255

Open
corverroos opened this issue Oct 12, 2022 · 0 comments
Open

Participation proof using prioritise #1255

corverroos opened this issue Oct 12, 2022 · 0 comments
Labels
protocol Protocol Team tickets V2

Comments

@corverroos
Copy link
Contributor

corverroos commented Oct 12, 2022 •
edited
Loading

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.
@thomasheremans thomasheremans added the protocol Protocol Team tickets label Jan 23, 2023
@boulder225 boulder225 added the V2 label Apr 19, 2024
@pinebit pinebit mentioned this issue Jul 9, 2024
Merged
obol-bulldozer bot pushed a commit that referenced this issue Jul 9, 2024
@pinebit
core/validatorapi: propose v1 and v2 returns 404 (#3167)
3b2f598 
Endpoints `produce_block` and `produce_blinded_block` must return 404 explicitly to prevent processing as proxy calls. Because previously we removed these from the router.
Also, this ensures all attempts to call these endpoint will increment `core_validatorapi_request_error_total` counter. 

category: feature
ticket: #1255
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
protocol Protocol Team tickets V2
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@corverroos @boulder225 @thomasheremans