-
Notifications
You must be signed in to change notification settings - Fork 157
Update wallet for connecting #428
Comments
A few things to do on this one:
|
Proposal is that each connection has a wallet with the identities in for that connection. If you only had one wallet for all connections how would you know which identity was for which connection? |
@EdMoffatt @Tobias-Hunter @caroline-church the SDK allows you to use a single wallet across multiple gateway connections; IMO we should think about reflecting this in the developer tools as well. With the refocusing on peers rather than "networks", it is more likely that developers will use the same identities to connect to multiple peers. Maybe the default is "one connection, one wallet" but you can have "two connections, one wallet" if you want to do the above? |
i think when we do the refocusing on the peers we should then do the two connections, one wallet but until then i think we should have one connection one wallet |
I think all these suggestions are spot on :) |
Tried to capture everything that we talked about @heatherlp - once you have a first version of the implementation, if we could go through it that'd be great! Blockchain connections pannel: Any questions please lemme know! ✌🏻 |
Currently the extension asks the user for a cert and private key. It does not allow users to use an existing wallet, which means that it's confusing for a user to use with samples such as commercial paper that instructs users to create a wallet.
Currently the extension uses the in-memory wallet. Under the covers. A proposal would be to change to using a file system wallet. This way a user could point the extension at an existing wallet to use for that connection.
We would create the wallets on the file system where we keep other data if the user wasn't using their own wallet
The other advantage is that when developing applications they could point their application at the wallet used in a configuration.
The text was updated successfully, but these errors were encountered: