search

trustbloc / trustbloc-did-method

DID method that extends Sidetree protocol with consortium discovery
Apache License 2.0
13 stars 10 forks source link

Managing reveal value #246

Open sandrask opened 3 years ago

sandrask commented 3 years ago

When Sidetree client builds update, recover and deactivate requests it has to provide reveal value for that operation. Currently Reveal value is bas64 encoded multihash of JWK.

Reveal value can be either: 1) saved by the client during previous operation and provided as-is (probably safest choice, but one more piece of info has to be managed) OR 2) calculated from update/recover key based on hashing algorithm of your last successful update/recovery commitment (this is what was mentioned in reference application issue when I brought up managing reveal value)

Client can check the latest commitment values by resolving DID - this information is part of did method.

sandrask commented 3 years ago

This is active issue that was referenced in merge above - shouldn't have been closed