Interoperability with thirdpaty wallets

[Volland]

Quite often applications already use a ssi or web3 wallets some of them are white label wallets with hight security features that not reveal or give access to private keys but offer methods for sign / encrypt / decrypt operations. I have seen few initiatives that allow to export or import of private keys as a part of the profile. Also new identity agents focus on managing multiple DIDs and corresponding private keys, but all this solution require raw private keys. It makes integration with white-label wallets practically impossible. Much flexible interface is to allow web5 to be configured by external interface of signer that offer sign and decrypt operations. it will give next benefit

• decouple crypto operations and operations with private keys
• enable integration with third party white-label wallets
• enable use of hardware keys and hardware modules
• give interoperability

[sondreb]

The integration can and should happen within the wallet software itself. Extension wallets can be triggered through messages within the browser, while desktop or mobile app-based wallets can use something like Wallet Connect protocol.

I work on a wallet where we are committed to supporting multiple identity systems and especially Web5.

https://github.com/block-core/blockcore-wallet

Exposing the private key out of the wallet is a massive risk.

[Volland]

@sondreb Users not always control a wallet implementations and some times private keys simple never exported from wallets.

[sondreb]

@sondreb Users not always control a wallet implementations and some times private keys simple never exported from wallets.

I think the process will be to ask the wallet developers to add support for the different new protocols related to Web5.

[Volland]

@sondreb well when web5 will have massive adoption for sure but still we have a yubikey hardware modules and privacy first wallets that never espouse a keys etc. My proposal made this integration possible