Uploaded image for project: 'Indy SDK'
  1. Indy SDK
  2. IS-1285

Indy SDK 2.0: Design for Aries vs Indy

    Details

    • Type: Task
    • Status: Complete
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Story Points:
      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

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                sergey.minaev Sergey Minaev
                Reporter:
                esplinr Richard Esplin
                Watchers:
                Ajay Jadhav, Kyle Den Hartog, Richard Esplin, Sergey Minaev
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: