-
The docs: https://docs.next.id/rest-api/proofservice-platforms-supported have the following text on an adding an ethereum id to your next.id DID:
My question is:
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
POST: https://proof-service.nextnext.id/v1/proof Payload:
Response: 201 Created
Note that one of the signatures is from the wallet that created the avatar. And the other is the signature from the wallet address that we want added to the avatar. In our case they are the same wallet address. |
Beta Was this translation helpful? Give feedback.
-
When dealing with wallets one would need to connect to: (i) the wallet the avatar was created with to be able to sign payload data This means both wallet addressed neet to be in metamask. So one way of doing this in the wallet world is to: (i) Prompt the user to connect to their avatar wallet address This is not that easy for end users. They need to be careful about which address they are connecting to. Of course no storage and switching between addresses is required if both addresses are the same one. The addresses are the same if we want to add the same address which made the avatar to the avatar. |
Beta Was this translation helpful? Give feedback.
POST: https://proof-service.nextnext.id/v1/proof
Payload:
Response: 201 Created
{}
Note…