Add windowed leaderboard and transparency APIs - #346
Open
Quanwritescodes wants to merge 1 commit into
Open
Conversation
|
@Quanwritescodes Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds the missing public visibility and historical tracking needed for solver performance, slash transparency, and protocol reporting.
What changed
1) Windowed solver leaderboard history
GET /api/v1/solvers/leaderboard?window=24h|7d|30d|allendpoint.GET /api/v1/solversall-time endpoint remains intact for compatibility.GET /api/v1/solvers/:address/stats?window=....2) Slash history and dispute workflow
GET /api/v1/solvers/:address/slasheswith pagination.POST /api/v1/solvers/:address/slashes/:slashId/disputewith signature validation using the repo's Stellar-signature pattern.resolved-upheldandresolved-reversedoutcomes.3) Public protocol transparency endpoint
GET /api/v1/stats/public.SupportedChainintent counts and volumedocs/public-transparency-contract.mddescribing the stable contract policy.Why this matters
These changes improve the protocol's transparency in the same way a real public reputation system should: they allow recent performance to be evaluated separately from historical activity, make slashing auditable, and give the community a stable public reference surface for dashboards and reporting.
Notes
closes #249
closes #250
closes #251
closes #252