-
Notifications
You must be signed in to change notification settings - Fork 49
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
Hyperledger Aries Q3 Quarterly Report #148
Conversation
Signed-off-by: Stephen Curran <swcurran@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
approved with a minor request for clarification. thanks!
* [Aries Bifold] using AFJ 0.4.0 was deployed with ease, including updates | ||
to existing Mobile Wallets being updated on the fly from using the Indy | ||
SDK to using Askar. | ||
* Instances of [Aries Framework JavaScript] using non-Indy ledgers were |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"deployed" was used in the two bullets above, can you clarify what that means? "deployed by adopters that have upgraded existing solutions to the new version"? or something else? if the former, can you add some context (doesn't need the details if the adopter's solution isn't a public reference) of the deployed solution? thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated the wording. Use — deployed by adopters that have upgraded their implementations. The smooth transition from Indy SDK storage to Askar is significant - requiring the safe updating of stored data from one format to another.
Signed-off-by: Stephen Curran <swcurran@gmail.com>
Signed-off-by: Stephen Curran swcurran@gmail.com