-
Notifications
You must be signed in to change notification settings - Fork 213
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
Service endorsements as COSE during DR #6500
Comments
@achamayou @eddyashton, regarding the services with lots of DRs, shall we introduce a new request parameter to ask for the endorsements chain explicitly? Possible options
|
@maxtropets we can do, but the chain should only get substantial if you ask for receipts that are many DRs ago. If you ask for recent receipts, it'll still be short. Having an option to skip endorsements definitely makes sense, and an endpoint to just get the chain (or even the chain in a tx range). Proposal:
|
@maxtropets we should have an endpoint that takes a historical service identity, and returns the chain of endorsements up to the current service, if found, and a clear message otherwise. This will be useful for users who have large amounts of receipts, and want to quickly check/confirm that a new service endorses them. We also want a CDDL schema of the endorsements, with an automatic test, and Merkle root chaining as discussed. |
Return COSE service identity endorsements chain in historical TX receipts.
Tasks
The text was updated successfully, but these errors were encountered: