-
Currently, responses returned by The reason that I would want to see block hash in the returned value is that so I can query the entire block using both block hash and slot number in Ogmios (findIntersect API). My main use case is to get the actual datum sitting at a specific address by using only Kupo and Ogimios, without running additional sync service or database, such as cardano-db-sync (I try to avoid adding new services as much as possible). Do you think this usage pattern is reasonable? An alternative solution to such use case is to add datum directly in the response of |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
Both changes are possible and make a lot of sense. The former however (adding block hashes) seem a bit more in the spirit of Kupo and the lightweight goal. Using then Ogmios to get data out of the chain-sync protocol is actually a great idea! I originally thought of Kupo used mainly in conjunction with the state query protocol but, it can work indeed very well with the chain-sync protocol provided that the full points description is available. Thanks for the feedback! |
Beta Was this translation helpful? Give feedback.
-
This is now available on |
Beta Was this translation helpful? Give feedback.
Both changes are possible and make a lot of sense. The former however (adding block hashes) seem a bit more in the spirit of Kupo and the lightweight goal.
Using then Ogmios to get data out of the chain-sync protocol is actually a great idea! I originally thought of Kupo used mainly in conjunction with the state query protocol but, it can work indeed very well with the chain-sync protocol provided that the full points description is available.
Thanks for the feedback!