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.

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

[Nakamoto] Emit signer performance data #4257

Closed
zone117x opened this issue Jan 18, 2024 · 3 comments · Fixed by #4526
Closed

[Nakamoto] Emit signer performance data #4257

zone117x opened this issue Jan 18, 2024 · 3 comments · Fixed by #4526

Comments

@zone117x
Copy link
Member

Related to signer support in the API & Explorer hirosystems/explorer#1248

The API and Explorer would like to show signer performance, e.g. a record of uptime and slot success rate.

It sounds like some changes in addition to the event emitter may be required:

I think this requires an extension to the NakamotoBlock event: inclusion of which stackers signed off on the block. The FROST protocol doesn't actually make this recoverable, but stacks-core needs this in place anyways to punish non-responsive signers, so it should be easy to add once that's in place.

Note: this is probably a nice-to-have and lower priority compared to the other signer related events.

@saralab
Copy link
Contributor

saralab commented Feb 27, 2024

@AshtonStephens Can you drop in specific details here

@saralab saralab removed the argon3.0 label Feb 27, 2024
@hstove
Copy link
Contributor

hstove commented Mar 8, 2024

I took a look at this today, and I'll admit I'm not quite sure where to start. I can figure out how to add data to the dispatched event, but I'm not sure where (or if) we store signer participation. @kantai any pointers?

@blockstack-devops
Copy link
Contributor

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@stacks-network stacks-network locked as resolved and limited conversation to collaborators Oct 30, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

4 participants