Fork of github.com/did-method-plc/did-method-plc

update Bluesky PBLLC to PBC (Public Benefit Corporation) (#46)

Changed files
+2 -2
+1 -1
README.md
···
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.
-
Moving governance of the `did:plc` method, and operation of registry servers, out of the sole control of Bluesky PBLLC is something we are enthusiastic about. Audit log snapshots, mirroring, and automated third-party auditing have all been considered as mechanisms to mitigate the centralized nature of the PLC server.
The size of the `verificationMethods`, `alsoKnownAs`, and `service` mappings/arrays may be specifically constrained. And the maximum DAG-CBOR size may be constrained.
···
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.
+
Moving governance of the `did:plc` method, and operation of registry servers, out of the sole control of Bluesky PBC is something we are enthusiastic about. Audit log snapshots, mirroring, and automated third-party auditing have all been considered as mechanisms to mitigate the centralized nature of the PLC server.
The size of the `verificationMethods`, `alsoKnownAs`, and `service` mappings/arrays may be specifically constrained. And the maximum DAG-CBOR size may be constrained.
+1 -1
package.json
···
"name": "did-method-plc",
"version": "0.0.1",
"repository": "git@github.com:bluesky-social/did-method-plc.git",
-
"author": "Bluesky PBLLC <hello@blueskyweb.xyz>",
"license": "MIT",
"private": true,
"engines": {
···
"name": "did-method-plc",
"version": "0.0.1",
"repository": "git@github.com:bluesky-social/did-method-plc.git",
+
"author": "Bluesky PBC <hello@blueskyweb.xyz>",
"license": "MIT",
"private": true,
"engines": {