You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While I understand that only the holder of the ed25519 private key would be able to sign a message that could be verified by the corresponding ed25519 public key, I would like to confirm that the didDocument retrieved from the blockchain was in fact created with the particular ed25519 public key.
Can the verificationMethod[0].publicKeyMultibase be decoded in some way as to reveal the ed25519 public key?
Or can we apply the same encodings to the didID and pubKey to produce the publicKeyMultibase and compare that with the one found in the resulting didDoc?
This seems to be the best ability to prove the verifiably of the didID without having to explicitly challenge the private key holder.
The text was updated successfully, but these errors were encountered:
While I understand that only the holder of the ed25519 private key would be able to sign a message that could be verified by the corresponding ed25519 public key, I would like to confirm that the didDocument retrieved from the blockchain was in fact created with the particular ed25519 public key.
Can the verificationMethod[0].publicKeyMultibase be decoded in some way as to reveal the ed25519 public key?
Or can we apply the same encodings to the didID and pubKey to produce the publicKeyMultibase and compare that with the one found in the resulting didDoc?
This seems to be the best ability to prove the verifiably of the didID without having to explicitly challenge the private key holder.
The text was updated successfully, but these errors were encountered: