Migrate owned did nuts to SQL #3392
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gerardsn
force-pushed
the
migrate-owned-did-nuts-to-sql
branch
from
121d543
to
703b08f
Compare
gerardsn
force-pushed
the
migrate-owned-did-nuts-to-sql
branch
from
703b08f
to
381bf97
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
closes #3329
In did:nuts a deactivated DID can never be reused. It is still possible to publish updates on the DID document after this on the network, but the node will forever consider the document deactivated. The deactivation status is stored in the document metadata that no longer exists in SQL, which means that after migrating the DID document history to SQL it will appear active again.
Possible solutions
TODO: