-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Add support for query parameters on staking queriers #2202
Comments
Concept ACK. Some of these are efficient and others are not - retrieving bonded validators, for example, is easy - but we aren't going to add an index from monikers or websites to validator addresses, so those queries would require |
What is the benefit of querying for |
@fedekunze Can this be closed? |
@cwgoes I don't think so. We can label it pre1.0 if you want, not high priority but definitely a nice to have |
cc @alessio |
Is this still something we want @fedekunze? |
I think so, yes. Would it be possible to set the context to a specific height i.e |
I've already implemented supporting height queries for querier-based queries (wow) here. Does this accomplish your needs? |
cool ! do we need to add REST query params or it only supports CLI for the moment ? |
Only CLI atm because it was super trivial. REST will involve more work. Essentially each REST handler will have to parse for a height query param and update the context. Still trivial and easy to implement, just more places in the code to this. |
Closing as implemented. |
Summary
Add support for query parameters on staking queriers for Gaia-lite GET requests
Problem Definition
No current way to query staking parameters from validators or delegation txs.
Rephrasing @sunnya97 #2139 (comment):
Same applies for the state of delegations, unbonds and redelegations on a specific block
height
, which is currently supported on CLIProposal
Delegation txs:
For the following endpoints:
delegators/{delegatorAddr}
).../<delegations>/...
.../unbonding-delegations/...
.../redelegations/...
Queries supported:
?height=<block_height>
: status at a specific block height.Examples:
Validators query
For the following endpoints:
.../validators
:Queries supported:
?jailed=<true/false>
?status=<bonded/unbonding/unbonded>
?height=<block_height>
: status at a specific block height. Useful to track voting power progress?moniker=<name>
?website=<website>
Examples:
For Admin Use
The text was updated successfully, but these errors were encountered: