search

ASCS-eV / envited-x-data-space

The ENVITED-X data space provides transparent and trustworthy access to shared data and services for innovators in mobility.
https://staging.envited-x.net/
Other
2 stars 0 forks source link

Refactor db to use naked addresses #373

Open royscheeren opened 3 weeks ago

royscheeren commented 3 weeks ago

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 commented 1 week ago

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.