did:me is a decentralized identifier method with authoritative state defined by signed canonical DAG-CBOR core snapshots and deterministic lifecycle rules.

Is did:me compatible with EU Digital Identity Wallet ecosystems?

did:me is designed for interoperability with eIDAS 2.0 and EU Digital Identity Wallet ecosystems through standards-aligned DID and credential workflows, including OpenID4VC patterns.

did:me

Decentralized Identifier Method

did:me — Stable identifiers with deterministic lifecycle control.

did:me is a decentralized identifier method for long-lived identifiers in high-assurance environments. It defines a lifecycle-controlled DID model without requiring a global consensus layer. Authoritative state is defined by a signed canonical core chain, while JSON documents are derived projections. This establishes clear verification boundaries for key rotation, multi-controller governance, and credential ecosystems aligned with eIDAS 2.0 and EU Digital Identity Wallet deployments.

Read Specification v1 Open JSON-LD Context

Why did:me

did:me is designed for deployments that require:

Durable identifiers
Deterministic lifecycle and cryptographic state transitions
Privacy-preserving verification across issuers, wallets, and relying parties
Compatibility with regulated trust frameworks

Canonical Core + Merkle / ZK Ready

Authoritative state is defined by canonical core bytes addressed by CID. Those bytes can be committed into Merkle structures for batch attestations and zero-knowledge circuits without altering authoritative DID semantics.

Proof Layer Separation

did:me separates authoritative core signatures from optional Data Integrity proof envelopes. This preserves canonical state integrity while enabling interoperability profiles and transport-layer compatibility.

Governance and Rotation

did:me supports:

Single or multiple controllers
Deterministic identifier lifecycle transitions
Policy-based update constraints for organizations, groups, and delegated operational models

Compatibility and Trust Frameworks

did:me interoperates with OpenID4VCI and OpenID4VP credential flows and EU Digital Identity Wallet architectures.

did:me provides:

Stable identifier continuity across key rotation and cryptographic upgrades.
Clear separation between canonical authority and projection formats.
Hybrid classical and post-quantum cryptographic support.
Support for SD-JWT and zero-knowledge verification workflows.
Controller models for both individual wallets and organizational governance.

DID owners may optionally publish DID Documents to public directory services for additional discoverability. Directory publication does not affect method validity, which is derived solely from the signed canonical core chain.

Normative Resources

Specification (v1)

https://did-me.org/spec/v1/

Normative method definition and conformance requirements.

JSON-LD Context (v1)

https://did-me.org/ns/did-me/v1

Normative term definitions for method extensions.

Method Repository

https://github.com/me-id/didme-spec

Source, release history, and issue tracking.