-
Notifications
You must be signed in to change notification settings - Fork 17
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
Receipts #276
Comments
I think it is meant to refer to this: https://datatracker.ietf.org/doc/draft-ietf-cose-merkle-tree-proofs/ at least as an example. And this defines receipts of inclusion and receipts of consistency |
Can we get a suggestion or PR for next steps? |
I'm inclined to reduce the entry in Definitions to just the head line from "Definition of transparency" which says just - "Receipts demonstrate inclusion of Signed Statements in the Append-only Log of a Transparency Service". The particulars of how "inclusion is demonstrated" is very log specific. I'll put together a small diff and see how that looks |
ah also, quite far down, where the draft describes "append only", it does introduce "In addition to Receipts, some verifiable data structures might support additional proof types, such as proofs of consistency, or proofs of non inclusion" I think a small amount of fore shadowing or re-arangement will do the trick |
Thanks, @robinbryce |
PR added, but I think it warants some discussion regarding possible tension with the hard requirement for COSE-Receipts |
1. align Receipt definition with definition of transparency 2. Explicitly acknowlege other signed proof types, but make it clear they are "not receipts", per the issue ietf-wg-scitt#276 's query
When the draft talks about receipts does it refers only to inclusion proofs. Can we still talk about receipts, if other proof types are supported by an implementation that those are still called Receipts?
The text was updated successfully, but these errors were encountered: