Fwd: Bluesky spins out an entity for did:plc

Quite interesting to see how bluesky are using did:plc, which is very
similar and compatible with did:nostr

curl -s "https://plc.directory/did:plc:ewvi7nxzyoun6zhxrhs64oiz" | jq .
{
  "@context": [
    "https://www.w3.org/ns/did/v1",
    "https://w3id.org/security/multikey/v1",
    "https://w3id.org/security/suites/secp256k1-2019/v1"
  ],
  "id": "did:plc:ewvi7nxzyoun6zhxrhs64oiz",
  "alsoKnownAs": [
    "at://atproto.com"
  ],
  "verificationMethod": [
    {
      "id": "did:plc:ewvi7nxzyoun6zhxrhs64oiz#atproto",
      "type": "Multikey",
      "controller": "did:plc:ewvi7nxzyoun6zhxrhs64oiz",
      "publicKeyMultibase":
"zQ3shunBKsXixLxKtC5qeSG9E4J5RkGN57im31pcTzbNQnm5w"
    }
  ],
  "service": [
    {
      "id": "#atproto_pds",
      "type": "AtprotoPersonalDataServer",
      "serviceEndpoint": "https://enoki.us-east.host.bsky.network"
    }
  ]
}

---------- Forwarded message ---------
Od: Otto Mora <omora@privado.id>
Date: pá 19. 9. 2025 v 19:56
Subject: Bluesky spins out an entity for did:plc
To: W3C Credentials CG (Public List) <public-credentials@w3.org>


Hey All,

Fresh news today from Bluesky. They are spinning out a Swiss Non Profit to
govern the did:plc method and associated technology.

https://docs.bsky.app/blog/plc-directory-org

It seems maybe "PLC" doesn't mean placeholder anymore , they are
recognizing that the identity network might have further application
outside of the Bluesky social network.

Cheers,

 Otto Mora
 Standards Architect / Product Evangelist
otto@privado.id
privado.id

* <https://x.com/PrivadoID>*   <https://www.linkedin.com/company/privado-id>
   <https://www.youtube.com/@PrivadoID>