Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor db to use naked addresses #373

Open
royscheeren opened this issue Nov 9, 2024 · 1 comment
Open

Refactor db to use naked addresses #373

royscheeren opened this issue Nov 9, 2024 · 1 comment

Comments

@royscheeren
Copy link
Contributor

Problem statement

We currently mix identifiers with and without identifiers like did:pkh:tz and urn:uuid:
It's annoying to keep track of when we use what.

Definition of done

Our system works completely without identifiers unless required by external parties like wallets or identity providers.
We strip them before putting them into db
We keep track of which identifier came with it

@jdsika
Copy link
Contributor

jdsika commented Nov 20, 2024

We shall use did:pkh:tezos:NetXdQprcVkpaWU:tz1TzrmTBSuiVHV2VfMnGRMYvTEPCP42oSM8 as this keeps track of all the other information. The only option I see is to store the information pairs like:

key {
   method: "did:pkh",
   namespace: "tezos",
   chainId: "NetXdQprcVkpaWU",
   address: "tz1TzrmTBSuiVHV2VfMnGRMYvTEPCP42oSM8"
}

But I actually like it better to keep the parsing rules and store the whole values.

@jdsika jdsika added this to the End February Milestone milestone Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants