Details
-
Task
-
Status: Complete
-
Medium
-
Resolution: Done
-
None
-
None
-
None
-
None
-
13
Description
Key considerations:
- What moves from LibIndy to LibAries. What stays.
- Indy: Ledger resolver
- Aries: Wallet, Pack / unpack, payment API
- CLI: move to Aries to be generic, or stay in Indy to focus on usability?
- The future of LibVCX
- Which API calls should stay in Indy, move to Aries, or move to be Evernym specific
- Threading model improvements.
- Renaming "Wallet"
Acceptance Criteria
- Close the current Indy SDK Architecture proposal design PR
- Create a new Indy SDK design PR with a revised architecture proposal
- Review this proposal with the Aries and Indy communities and decide on next steps
