Skip to content

Add alsoKnownAs cross-chain identity linking#39

Open
chongkan wants to merge 1 commit into
w3c-ccg:mainfrom
chongkan:also-known-as-linking
Open

Add alsoKnownAs cross-chain identity linking#39
chongkan wants to merge 1 commit into
w3c-ccg:mainfrom
chongkan:also-known-as-linking

Conversation

@chongkan

Copy link
Copy Markdown

Summary

Adds a new Cross-Chain Identity Linking via alsoKnownAs section, enabling did:pkh to serve as a cryptographic bridge to richer DID methods.

New content

  • 3 discovery mechanisms: reverse name service lookup (ENS/SNS), companion registry, verifier-provided hints
  • Bidirectional verification: both sides must reference each other for trusted linking
  • Example: linked DID Document with did:pkh:solana:...:CKg5d12J...did:sns:alice.sol
  • Upgrade path integration: connects to existing "Combination with other DID methods" section

Design philosophy alignment

This does NOT change did:pkh's generative, read-only nature. The alsoKnownAs property is populated during resolution (not stored) via external lookups. The core DID Document generation remains deterministic.

Related: #38 | W3C tracking

Signed-off-by: Eduardo Chongkan e.chongkan@gmail.com

New section defining:
- alsoKnownAs discovery during resolution (reverse name lookup, companion registry, verifier hints)
- Bidirectional verification protocol
- Example linked DID Document (did:pkh:solana → did:sns)
- Relationship to existing upgrade paths

Addresses w3c-ccg#38

Signed-off-by: Eduardo Chongkan <e.chongkan@gmail.com>
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

Successfully merging this pull request may close these issues.

1 participant