Replies: 2 comments 4 replies
-
|
Hi @cl0ete, could you maybe provide some examples of what "allowing credo to return SD-JWT credentials with modified claims" looks like? I get what you're trying to do, but I don't understand returning modified claims looks like in this case. |
Beta Was this translation helpful? Give feedback.
4 replies
-
|
Just wanna restate that the goal here is for cheaper storage for large payloads in credentials. I am open to any other ideas 👀 We are looking for a solution that:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Yo.
So I have a requirement to add images to SD-JWT credentials (react with a 👍 or 👎 for images in SD-JWT)
However I want to store the image data in cheaper storage, something like S3.
Currently I grab the original claim/disclosure and drop it in S3 and modify the claim that is stored in the wallet with a pointer back to S3. I can then replace the modified claim/disclosure with the original when needed.
However credo does not return the SD-JWT with modified claims/disclosures (by design I expect/hope), for presentation requests.
How do we feel about allowing credo to return SD-JWT credentials with modified claims?
It feels like this might go against some VC philosophy let me know what you think.
The goal is to have a cheaper storage solution for large payloads.
Thanks
Beta Was this translation helpful? Give feedback.
All reactions