Content Comparison

...

• Does aries wallet really needs lock/unlock feature?

  Open question : Still investigating
• Should we provide password in each api call as given in specification? 

VC plugin:

VC plugin adds verifiable credential features to the wallet. By default aries-framework-go verifiable command features will be used for creating and verifying credentials/presentations.
The new interface 'presentationSubmission' can be used to submit presentation definitions to the wallet and to get presentation submission as response.

...

• Verify: Takes a Verifiable Credential or Verifiable Presentation as input, returns a boolean verified, and an error if verified is false.
• Issue: Adds proof to verifiable credential provided. (options contains at least a verificationMethod, and proofPurpose.)
• Prove:  Takes an id of the verifiable credential and verifies the proof (options contains at least a challenge.)
• presentationSubmission: Produces presentation submission based on wallet contents.

...

• Why we need a new query interface for querying VCs using presentation exchange? Why can't we use existing 'query' interface from store plugin?
  'add' interface function from store plugin can be used to add any data model. Modifying 'query' interface to support presentation exchange may increase the complexity for non-VC data model users.

Key plugin:

Key plugin provides 2 interfaces : verifyRaw & signRaw. Framework will use aries kms api for these features.

This plugins can be injected to customize the wallet to use other kms implementations like webkms.

Store plugin: