Open koslambrou opened 2 years ago
I need something like this as well. @rooooooooob
Need a good definition of what is the "wallet id" in that case, and how Daedalus/PAB define it. It's gotta be a Blake2b_160
of something specific, there's no such thing as a wallet identity inherently in the scheme, can be some part of the derivation.
Yoroi has an experimental feature available in the connector now where you can request identification from a user, when connecting, and then receive an auth object with some parameters like a wallet ID and a dapp-specific pubkey, etc. We could add some PAB-specific identity there as well quite easily, before proposing the final version of this to the spec, but need to know what exactly the cardano-wallet is using in that case.
@koslambrou , can you provide some links to the PAB or cardano-wallet documentation where this specific wallet id is described?
The wallet id is a blake2b-160 digest of the root verification key of the wallet (root key obtained from CIP-0003).
One idea we had in the past was to instead define a new derivation paths for wallets that are a "utility key" path. You can still find the draft idea for this here: https://github.com/Emurgo/EmIPs/pull/4
Also, depending on what you want this for, it may be related to https://github.com/cardano-foundation/CIPs/issues/204
When trying to integrate light wallets with the Plutus Application Backend, I came across the issue where I need a wallet id before activating a contract. Currently, the PAB requires a wallet id encoded in
blake2b_160
, which is whatDaedalus
(cardano-wallet
) uses.Therefore, does it make sense to enhance the API with a
getWalletId
function?Maybe something like:
@rooooooooob