Is your feature request related to a problem? Please describe.
Currently LSKV offers write receipts through CCF for ensuring that the correct request was performed at the server, e.g. Kubernetes API server rewriting values.
However, when reading things from the same proxy, there is no way to know that the value they serve you is actually from the datastore.
Describe the solution you'd like
Some sort of receipt or signature on read values that confirms the value is from the LSKV cluster and from the given txid.
Is your feature request related to a problem? Please describe.
Currently LSKV offers write receipts through CCF for ensuring that the correct request was performed at the server, e.g. Kubernetes API server rewriting values.
However, when reading things from the same proxy, there is no way to know that the value they serve you is actually from the datastore.
Describe the solution you'd like
Some sort of receipt or signature on read values that confirms the value is from the LSKV cluster and from the given txid.
Additional context
c.f. SCITT's read receipts: https://github.com/microsoft/scitt-ccf-ledger/blob/b6d3c98cbe107d8665e2da206ace06b2b2d5371b/app/src/prefix_tree/read_receipt.h