Open DRK3 opened 3 years ago
wallet should have a internal default EDV implementation where wallet user can just pass an EDV URL & keys and expect wallet to use that EDV for storing contents.
Another solution: move the wallet package to a new module
Currently the
wallet
package imports theedv
storage provider, which is in another module. This creates an undesirable dependency on theedv
module from the main aries go module. We should rework thewallet
package to not be hard-coded toedv
, and instead allow the encrypted storage solution to be injected in. This may require creating a new interface inspi
.Once this is done, we don't need the
github.com/hyperledger/aries-framework-go/component/storage/edv => ../../component/storage/edv
replaces in the command modules.