Add block hash in the response of "matches" API

[KtorZ]

Discussed in #5

^{Originally posted by cffls March 9, 2022}
Currently, responses returned by matches doesn't not have block hash. Since the response already contains the slot in which the transaction lives, my naive guess is that it wouldn't be much work to add block hash in the response?


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 Ogmios, 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 matches API if they present in the witness of the transaction, but this might be a bigger change than simply adding the block hash.