Skip to content
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

Where in the presentation request to include transaction_data objects #172

Closed
Sakurann opened this issue May 14, 2024 · 0 comments · Fixed by #197
Closed

Where in the presentation request to include transaction_data objects #172

Sakurann opened this issue May 14, 2024 · 0 comments · Fixed by #197

Comments

@Sakurann
Copy link
Collaborator

Sakurann commented May 14, 2024

(separating a discussion started in #156 (comment) into a new issue)

On a May-14-2024 WG call, there seems to be a rough consensus that transaction_data should be outside the input_descriptor objects and should contain reference to the input_descriptors that are requesting credentials to which the content of a transaction_data can be bound to (instead of putting transaction data obejct inside an input_descriptor, which was an original idea). This updated approach would prevent duplication of the same transaction data object across multiple input descriptors when the verifier is asking to "bind transaction_data to credential A or credential B".

opening an issue to make sure there is a consensus on this direction, expecting to be able to close this issue relatively soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant