You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
- 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)
- RatifyState, which is the result of invocation of RATIFY and ENACT ledger rules. This can be achieved by forcing the pulser:
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:
psPorposals
ordpProposals
.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)RatifyState
, which is the result of invocation ofRATIFY
andENACT
ledger rules. This can be achieved by forcing the pulser:cardano-ledger/libs/cardano-ledger-api/src/Cardano/Ledger/Api/State/Query.hs
Lines 312 to 316 in 88d7885
The text was updated successfully, but these errors were encountered: