-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
Make query to find what states a given node exposes #15463
Labels
Comments
tac0turtle
added
T: UX
T: Dev UX
UX for SDK developers (i.e. how to call our code)
T: Client UX
T:Sprint
and removed
needs-triage
Issue that needs to be triaged
labels
Mar 20, 2023
4 tasks
we should look at adding other configurations like state sync and pruning settings so there is a predicable way to work with. nodes |
Another one I ran into:
and
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Summary
If you want to make some tooling to run a query across many heights, you need to know what states a given full node has. (E.g. an indexer). The current ecosystem default as far as I can tell, is to use an archive node, which provides much slower queries. And in general is a bit less robust than what many people's needs could afford them. (E.g. resync from full nodes maintaining last 10k blocks, and only revert to an archive node if too old)
Right now the closest thing we have is
earliest_block_height
in theSTATUS
RPC endpoint. However this exposes the Tendermint earliest block height, not the state machine's which is subject to pruning conditions.The proposal is to add a query of some sort, that returns the earliest state that a given node is serving queries from.
Its not obvious to me what the most natural way to expose this info is, but its pretty easy for integrators to adapt to whatever standard we want to set. E.g.
an "Earliest State Query", or a more general "status" query from the state machine.
The text was updated successfully, but these errors were encountered: