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

Lookup of previous on-chain points #24

Closed
KtorZ opened this issue Jun 9, 2022 · 0 comments · Fixed by #29
Closed

Lookup of previous on-chain points #24

KtorZ opened this issue Jun 9, 2022 · 0 comments · Fixed by #29
Labels
enhancement New feature or request
Projects

Comments

@KtorZ
Copy link
Member

KtorZ commented Jun 9, 2022

Describe your idea, in simple words.

Given some point (i.e. slot number + block header hash), it would be nice to have a way to query the direct ancestor of that point on-chain. This could be achieved through a simple GET HTTP query, provided that Kupo keeps track of on-chain points. At the moment, Kupo does only store checkpoints as, the last point of the batch that's just been processed. And, it discards past checkpoints that are too old based on protocol parameters.

Why is it a good idea?

Having such a feature would allow to combine Kupo with solutions such as Ogmios where having a point on-chain can be used to recover pretty much any data from the chain-sync protocol. Yet, the chain-sync protocol requires to know the previous point to the one we are interested about (because it seeks intersection from that point on, and keep streaming block starting with the following point). Thus, while we could technically enhance existing data to return not only points where events happen but also previous points, it is just awkward to explain and cumbersome to do overall. Instead, providing an easy way to lookup previous points feels more elegant.

Are you willing to work on it yourself?

Yes.

@KtorZ KtorZ added the enhancement New feature or request label Jun 9, 2022
@KtorZ KtorZ added this to To do in v2.0.0 Jun 9, 2022
@KtorZ KtorZ moved this from To do to In progress in v2.0.0 Jun 9, 2022
@KtorZ KtorZ closed this as completed in #29 Jun 10, 2022
v2.0.0 automation moved this from In progress to Done Jun 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

1 participant