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.

Sign up for GitHub

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

Jump to bottom

Mismatch of version in transaction author agreement and acceptance mechanisms response #1010

Closed
jakubkoci opened this issue Sep 5, 2022 · 1 comment · Fixed by #1013
Closed

Mismatch of version in transaction author agreement and acceptance mechanisms response #1010

jakubkoci opened this issue Sep 5, 2022 · 1 comment · Fixed by #1013

Comments

@jakubkoci
Copy link
Contributor

If agent’s config contains version 0.1, then AuthorAgreement contains version 2.0 which seems correct because text attribute contains “Transaction Author Agreement V2“ but AcceptanceMechanisms contains version 0.1. This fails with CommonInvalidStructure error, respective with “Calculated hash of concatenation version and text doesn't equal to passed hash value.” thrown by Indy SDK function prepare_acceptance_data to which we pass authorAgreement.text and authorAgreement.digest gotten from ledger and taa.version from our agent config.

If agent’s config contains version 2.0 AFJ throws an error because of condition authorAgreement.acceptanceMechanisms.version !== taa.version and AcceptanceMechanisms containing version 0.1.
@TimoGlastra
Copy link
Contributor

What's the difference between the acceptance mechanism version and the taa version?

@jakubkoci jakubkoci mentioned this issue Sep 6, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(ledger): check taa version instad of aml version
2 participants
@jakubkoci @TimoGlastra