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

Addition of two new governance related ledger state queries #4511

Closed
2 tasks done
lehins opened this issue Jul 26, 2024 · 0 comments · Fixed by #4514
Closed
2 tasks done

Addition of two new governance related ledger state queries #4511

lehins opened this issue Jul 26, 2024 · 0 comments · Fixed by #4514
Assignees
Labels

Comments

@lehins
Copy link
Collaborator

lehins commented Jul 26, 2024

It looks like users can benefit from accessing information related to ratification and enactment (see #4509). Therefore we need to add some ledger state queries:

  1. - proposals that are considered for ratification, as well as their votes. This can be achieved in constant time without forcing the drep pulser by exposing those proposals through a ledger state query that looks into the DRepPulserState. In partuclar, depending on the pulser state it will return either psPorposals or dpProposals.
    We need to also add filtering capabilities by the GovActionId, similarly how we do filtering on other queries (i.e. empty input Set means no filtering)
  2. - RatifyState, which is the result of invocation of RATIFY and ENACT ledger rules. This can be achieved by forcing the pulser:
    finishedPulserState ::
    ConwayEraGov era =>
    NewEpochState era ->
    (PulsingSnapshot era, RatifyState era)
    finishedPulserState nes = finishDRepPulser (nes ^. newEpochStateGovStateL . drepPulsingStateGovStateL)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants