commit 4d5d01799a3a9b6cafde52373ae07c4942ee7a68 · edouard.paris/did-method-plc

+1 -1

LICENSE

···

       1
       1
        
       Dual MIT/Apache-2.0 License

     

       2
       2
        
       

     

       3
       3
       -
       Copyright (c) 2022-2024 Bluesky PBC

     

       3
       3
       +
       Copyright (c) 2022-2025 Bluesky Social PBC

     

       4
       4
        
       

     

       5
       5
        
       Except as otherwise noted in individual files, this software is licensed under the MIT license (<http://opensource.org/licenses/MIT>), or the Apache License, Version 2.0 (<http://www.apache.org/licenses/LICENSE-2.0>), at your option.

+2 -2

README.md

···

10
10

11
11

## Motivation

12
12

13
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.

13
13
+
[Bluesky Social 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
14

15
15

PLC stands for "Public Ledger of Credentials". We expect to evolve the system (in a backwards-compatible manner) 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
16

···

389
389

390
390

We welcome proposals for small additions to make `did:plc` more generic and reusable for applications other than atproto. But no promises: atproto will remain the focus for the near future.

391
391

392
392
-
We are enthusiastic about the prospect of moving governance of the `did:plc` method, and operation of registry servers, out of the sole control of Bluesky PBC. Audit log snapshots, mirroring, and automated third-party auditing have all been considered as mechanisms to mitigate the centralized nature of the PLC server.

392
392
+
We are enthusiastic about the prospect of moving governance of the `did:plc` method, and operation of registry servers, out of the sole control of Bluesky Social PBC. Audit log snapshots, mirroring, and automated third-party auditing have all been considered as mechanisms to mitigate the centralized nature of the PLC server.

393
393

394
394

The size of the `verificationMethods`, `alsoKnownAs`, and `service` mappings/arrays may be specifically constrained. And the maximum DAG-CBOR size may be constrained.

395
395

+1 -1

package.json

···

       2
       2
        
         "name": "did-method-plc",

     

       3
       3
        
         "version": "0.0.1",

     

       4
       4
        
         "repository": "git@github.com:did-method-plc/did-method-plc.git",

     

       5
       5
       -
         "author": "Bluesky PBC <hello@blueskyweb.xyz>",

     

       5
       5
       +
         "author": "Bluesky Social PBC <hello@blueskyweb.xyz>",

     

       6
       6
        
         "license": "MIT",

     

       7
       7
        
         "private": true,

     

       8
       8
        
         "engines": {

+1 -1

website/spec/v0.1/did-plc.md

···

       381
       381
        
       

     

       382
       382
        
       We welcome proposals for small additions to make `did:plc` more generic and reusable for applications other than atproto. But no promises: atproto will remain the focus for the near future.

     

       383
       383
        
       

     

       384
       384
       -
       We are enthusiastic about the prospect of moving governance of the `did:plc` method, and operation of registry servers, out of the sole control of Bluesky PBC. Audit log snapshots, mirroring, and automated third-party auditing have all been considered as mechanisms to mitigate the centralized nature of the PLC server.

     

       384
       384
       +
       We are enthusiastic about the prospect of moving governance of the `did:plc` method, and operation of registry servers, out of the sole control of Bluesky Social PBC. Audit log snapshots, mirroring, and automated third-party auditing have all been considered as mechanisms to mitigate the centralized nature of the PLC server.

     

       385
       385
        
       

     

       386
       386
        
       The size of the `verificationMethods`, `alsoKnownAs`, and `service` mappings/arrays may be specifically constrained. And the maximum DAG-CBOR size may be constrained.

     

       387
       387

+1 -1

website/templates/base.html

···

       86
       86
        
       

     

       87
       87
        
       <footer class="container-fluid">

     

       88
       88
        
       	<div class="container">

     

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

     

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

     

       90
       90
        
         </div>

     

       91
       91
        
       </footer>

     

       92
       92
        
       {% endblock -%}

+1 -1

website/templates/home.html

···

       10
       10
        
       

     

       11
       11
        
         <p>PLC is a method which implements the W3C Decentralized Identifier (DID) standard. This means it is interoperable and reusable by other applications and organization.</p>

     

       12
       12
        
       

     

       13
       13
       -
         <p>Bluesky PBC developed DID PLC when designing the AT Protocol (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.</p>

     

       13
       13
       +
         <p>Bluesky Social PBC developed DID PLC when designing the AT Protocol (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.</p>

     

       14
       14
        
       

     

       15
       15
        
         <p>PLC stands for "Public Ledger of Credentials". The system has been in production use for several years, with over twelve million registered DIDs in the atproto network as of October 2024. We feel that the existing system provides value and is worth consideration as a persistent identifier for other applications. The system may evolve to add functionality or improve security, but will do so in a backwards-compatible manner so that existing DIDs will continue to resolve.</p>

     

       16
       16