Skip to content
This repository has been archived by the owner on Mar 5, 2022. It is now read-only.

Managing reveal value #246

Open
sandrask opened this issue Dec 17, 2020 · 1 comment
Open

Managing reveal value #246

sandrask opened this issue Dec 17, 2020 · 1 comment

Comments

@sandrask
Copy link
Contributor

sandrask commented Dec 17, 2020 •
edited
Loading

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 added a commit to sandrask/trustbloc-did-method that referenced this issue Dec 18, 2020
@sandrask
chore: update sidetree-core (add reveal value), sidetree-mock
209b2ab 
Update sidetree-core, sidetree-mock:
- add reveal value

Created issue-246 to address management of reveal value (already planned in 1.6)

Closes trustbloc#246

Signed-off-by: Sandra Vrtikapa <[email protected]>
sandrask added a commit to sandrask/trustbloc-did-method that referenced this issue Dec 18, 2020
@sandrask
chore: update sidetree-core (add reveal value), sidetree-mock
bae470a 
Update sidetree-core, sidetree-mock:
- add reveal value

Created issue-246 to address management of reveal value (already planned in 1.6)

Closes trustbloc#246

Signed-off-by: Sandra Vrtikapa <[email protected]>
sandrask added a commit to sandrask/trustbloc-did-method that referenced this issue Dec 18, 2020
@sandrask
chore: update sidetree-core (add reveal value), sidetree-mock
16187a9 
Update sidetree-core, sidetree-mock:
- add reveal value

Created issue-246 to address management of reveal value (already planned in 1.6)

Closes trustbloc#246

Signed-off-by: Sandra Vrtikapa <[email protected]>
sandrask added a commit to sandrask/trustbloc-did-method that referenced this issue Dec 18, 2020
@sandrask
chore: update sidetree-core (add reveal value), sidetree-mock
d637474 
Update sidetree-core, sidetree-mock:
- add reveal value

Created issue-246 to address management of reveal value (already planned in 1.6)

Closes trustbloc#246

Signed-off-by: Sandra Vrtikapa <[email protected]>
@sandrask sandrask mentioned this issue Dec 18, 2020
Merged
sandrask added a commit to sandrask/trustbloc-did-method that referenced this issue Dec 18, 2020
@sandrask
chore: update sidetree-core (add reveal value), sidetree-mock
f5a1ccd 
Update sidetree-core, sidetree-mock:
- add reveal value

Created issue-246 to address management of reveal value (already planned in 1.6)

Closes trustbloc#246

Signed-off-by: Sandra Vrtikapa <[email protected]>
@sandrask sandrask reopened this Dec 18, 2020
@sandrask
Copy link
Contributor Author

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sandrask