ARCHIVE/xrpl-dev-portal
1
0
Fork 0
mirror of https://github.com/XRPLF/xrpl-dev-portal.git synced 2025-11-19 19:25:51 +00:00
Code Issues Packages Projects Releases Wiki Activity

improve did conceptual info

Browse Source
This commit is contained in:
Oliver Eggert
2024-04-12 10:20:39 -07:00
parent ad6637de37
commit 226fe2ff44
1 changed files with 4 additions and 43 deletions
Download Patch File Download Diff File Expand all files Collapse all files

47
docs/concepts/accounts/decentralized-identifiers.md
View File

@@ -17,7 +17,9 @@ The key principles of a DID are:
- **Decentralization:** No central issuing agency controls the DID, enabling the owner to update, resolve, or deactivate it. This also makes your identity highly-available, since DIDs are usually stored on a blockchain and always available for verification.
- **Verifiable Credentials:** Anyone can create a DID and falsify the information on it. To prove the authenticity of a DID, a user must provide a verifiable credential (VC). In the DID ecosystem, there are three parties: _user_, _issuer_, and _verifier_. The _user_ controls the DID, but needs a trusted _issuer_ to verify the information offline. The issuer provides a verfiable credential, which the user gives to _verifiers_ that need to confirm the user's identity. Verifiable credentials are cryptographically secure and tamper-evident.
- **Verifiable Credentials:** Anyone can create a DID and falsify the information on it. To prove the authenticity of a DID, a user must provide a verifiable credential (VC) that is cryptographically secure and tamper-evident.
In the DID ecosystem, there are three parties: _user_, _issuer_, and _verifier_. The _user_ controls the DID, but needs a trusted _issuer_ to verify the information offline. The issuer provides a verfiable credential, which the user gives to _verifiers_ that need to confirm the user's identity. To learn more about the DID ecosystem, see: [Ecosystem Overview](https://www.w3.org/TR/vc-data-model/#ecosystem-overview).
- **Interoperability:** DIDs are open to any solution that recognizes the W3C DID standard. This means a DID can be used to authenticate and establish trust in various digital transactions and interactions.
@@ -73,8 +75,6 @@ To learn more about the core properties of a DID document, see: [Decentralized I
- You can include any content in a DID document, but should limit it to verification methods and service points. Since DIDs on XRPL are publicly available, you shouldn't include any personal information.
- IPFS allows anyone to store content on the nodes in a distributed network. A common misconception is that anyone can edit that content; however, the content-addressability of IPFS means any edited content will have a different address from the original. While any entity can copy a DID document anchored with an XRPL account's `DIDDocument` or `URI` fields, they can't change the document itself unless they control the private key that created the corresponding `DID` object.
{% raw-partial file="/docs/_snippets/common-links.md" /%}
## Use Cases
@@ -88,43 +88,4 @@ DIDs enable many use cases, such as:
- Logging into websites.
## FAQs
### How are DIDs different from authorized trust lines?
A solution of issuing tokens using authorized trust lines doesn’t scale well regarding the resale of these issued tokens. Issuers must create a new trust line with any new party interested in acquiring the asset. The responsibility of setting up the authorized trust line is on the original issuer or the current asset holder.
If applications use DIDs, they could provide access to the application only to certain users with a specific verifiable credential that is shared off-chain.
### How did DIDs benefit a DeFi or institutional finance developer?
Build on XRPL - having a protocol native DiD means you can more easily onboard users by simply integrating with the DID, building your application, or adopting another application.
Create your own DID and verifiable credential (VC)focused application
Other developers throughout the XRPL ecosystem can integrate into your application; end users can onboard and interact with your application
Compliance when/where needed
### What is the DID ecosystem of issuers, holders, and verifiers?
For developers to successfully adopt the DID feature, the XRPL needs a healthy ecosystem of identity issuers, holders, and verifiers.
Issuers
Issuers do offline verification and issue a verified credential to a holder. This credential is sent to the user off-chain via a peer-to-peer (P2P) message through the application. For the identity ecosystem to work, the XRPL needs high-quality identity issuers to participate and provide verified credentials.
Holders
The user holds verified credentials issued by the identity issuer in their wallet.
Verifiers
These applications consume verifiable credentials issued by identity issuers and allow holders access to their applications based on the credentials provided.
Source: https://www.w3.org/TR/vc-data-model/#ecosystem-overview
### What has been built as part of XLS-40?
Built
A ledger object DID that goes on the XRPL
A DIDSet transaction to create/update the object
A DIDDelete transaction to delete the object
XRPL-JS, XRPL-PY and XRPL-Java SDK
In progress
DID Resolver library for XRPL
DID registry for XRPL
Recommended open-source library for verifiable credentials by the application
https://www.npmjs.com/package/@digitalcredentials/vc
{% raw-partial file="/docs/_snippets/common-links.md" /%}