Replies: 2 comments
-
BACKROUND FOR CONTEXT: (Note the answer is further down) Adding an address looks like this: POST: https://proof-service.nextnext.id/v1/proof Payload:
Notice that signature comes from the wallet that signed the avatar and that the wallet_signature is the wallet address you want to add. In this example I have already shown how to do it when both the wallet address signing the avatar and the wallet address I want to asoociate with my avatar DID are the same: https://github.com/spotadev/next-id-twitter-wallet However I want to do it when they are different and without the user handling private keys. i.e. only want the wallets involved to managing private keys and doing the signing. ANSWER: Meta Mask can have multiple addresses in it. So maybe the user could import all the addresses they want to associate with their DID into metamask. Then the user could connect to each of the wallets it wants associated with its avatar DID, in turn and create the signatures. The signatures could be stored in browser storage. Finally the user could switch to the wallet which is managing the avatar and dig out all the other signatures from storage and send them to the proof service. |
Beta Was this translation helpful? Give feedback.
-
Using wallet containers like MetaMask is still considered as "having access". Since we haven't impl a dedicated Avatar private key management (will be impl in MPC way later). For now:
|
Beta Was this translation helpful? Give feedback.
-
How do I associate multiple wallet addresses to a next.id avatar DID without having access to the private keys. i.e. do this only using metamask wallets?
Beta Was this translation helpful? Give feedback.
All reactions