veramolabs / did-ens-spec Goto Github PK

• Provide values for TEXT records
• Provide examples for more complex DID Docs, e.g., more service endpoints, more auth keys

Since ENS name leases can end or the owner can be transferred we should also add versioning as per DID Core.

I believe that a simpler solution than what is currently proposed could provide a lot of short term value, by making use of the work done on did:ethr, without sacrificing any future capabilities.

Rather than using ENS Text Records to specify a DID's properties, a did:ens:chainId:example.eth would simply be treated as did:ethr:chainId:{(await ens_resolve(chainId:example.eth)).controller}

Future versions of this specification could augment did:ens with TEXT Record CRUD updates, if a consensus develops around that.

If this seems like a reasonable idea, I'd be happy to draft a PR that would simplify this spec.

Describe how it works using ENS contracts, resolvers, registrars etc.

We might use did:pkh as the canonicalId for semantic interop.