···

       
10
       
 
       


     

       
11
       
 
       
## Motivation

     

       
12
       
 
       


     

       
13
       
-
       
[Bluesky PBC](https://blueskyweb.xyz/) developed DID PLC when designing the [AT Protocol](https://atproto.com) (atproto) because we were not satisfied with any of the existing DID methods. We wanted a strongly consistent, highly available, recoverable, and cryptographically secure method with fast and cheap propagation of updates.

     

       
14
       
 
       


     

       
15
       
 
       
We originally titled the method "placeholder", because we didn't want it to stick around forever in its current form. We are actively hoping to replace it with or evolve it into something less centralized - likely a permissioned DID consortium. That being said, we do intend to support `did:plc` in the current form until after any successor is deployed, with a reasonable grace period. We would also provide a migration route to allow continued use of existing `did:plc` identifiers.

     

       
16
       
 
       


     

···

       
10
       
 
       


     

       
11
       
 
       
## Motivation

     

       
12
       
 
       


     

       
13
       
+
       
[Bluesky PBC](https://bsky.social/) developed DID PLC when designing the [AT Protocol](https://atproto.com) (atproto) because we were not satisfied with any of the existing DID methods. We wanted a strongly consistent, highly available, recoverable, and cryptographically secure method with fast and cheap propagation of updates.

     

       
14
       
 
       


     

       
15
       
 
       
We originally titled the method "placeholder", because we didn't want it to stick around forever in its current form. We are actively hoping to replace it with or evolve it into something less centralized - likely a permissioned DID consortium. That being said, we do intend to support `did:plc` in the current form until after any successor is deployed, with a reasonable grace period. We would also provide a migration route to allow continued use of existing `did:plc` identifiers.

     

       
16
       
 
       


     

···

       
86
       
 
       


     

       
87
       
 
       
<footer class="container-fluid">

     

       
88
       
 
       
	<div class="container">

     

       
89
       
-
       
    <small>Developed by <a href="https://blueskyweb.xyz">Bluesky PBC</a> for <a href="https://atproto.com">atproto</a></small>

     

       
90
       
 
       
  </div>

     

       
91
       
 
       
</footer>

     

       
92
       
 
       
{% endblock -%}

     

···

       
86
       
 
       


     

       
87
       
 
       
<footer class="container-fluid">

     

       
88
       
 
       
	<div class="container">

     

       
89
       
+
       
    <small>Developed by <a href="https://bsky.social">Bluesky PBC</a> for <a href="https://atproto.com">atproto</a></small>

     

       
90
       
 
       
  </div>

     

       
91
       
 
       
</footer>

     

       
92
       
 
       
{% endblock -%}