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
Quote: @shakreiner
The current iterations over Update operation using the commit-reveal chain may lead to an infinite loop when trying to resolve a DID.
The thing that can cause this state is having a DID with 2 Update operations, where the second operation commits to the first one again.
This situation should not be allowed based on the specification (updateCommitment must be a new commitment in every operation), but the code doesn't seem to enforce that.
As a sidetree implementation, we need to make sure that this is working in-code and not just in-theory. We need to add a unit test that tracks multiple-commits to make sure it doesn't result in an unsolvable did, and formulate a response depending on the unit test.
The text was updated successfully, but these errors were encountered:
decentralized-identity/sidetree#1169
As a sidetree implementation, we need to make sure that this is working in-code and not just in-theory. We need to add a unit test that tracks multiple-commits to make sure it doesn't result in an unsolvable did, and formulate a response depending on the unit test.
The text was updated successfully, but these errors were encountered: