Skip to main content
Knowledge mapUnderstand identity and credentialsIndustry concepts and standards

You are here. See how this question connects to other ideas.

Select a node to open its page · Expand to read within the map

Knowledge mapFollow a connection. Understand a question.
← Identity and credentials

Learning path

Understand identity and credentials

Distinguish identifiers, control, claims and application requests.

This path offers a suggested order, not a mandatory course. Skip familiar questions or open any node directly from the map.

After reading, sketch an application you use. Locate its identities, credentials and data, and identify who decides access. Mark uncertainties as questions and return to the relevant node instead of using one term to explain the whole system.

Along this path

  1. What does a DID identify?

    Distinguish the identifier, its document and its subject.

  2. Does control prove real-world identity?

    Proving control of an identifier and establishing a real-world identity are different tasks.

  3. What does a verifiable credential make verifiable?

    Check authorship and integrity, then decide whether to accept the claim.

  4. Why trust an issuer?

    Checking a credential protection mechanism differs from deciding whether to trust its issuer.

  5. What does Arc Wallet do in an identity flow?

    The wallet manages identities and credentials; applications still evaluate requests.

  6. What does DID Connect connect?

    Understand the exchange between an application request and the user’s identity tool.

  7. How does did:abt relate to DID Core?

    DID Core supplies a shared model; each method supplies its own rules.

  8. What does DID Motif help you recognize?

    A visual identifier helps recognition; it is not proof of control.

  9. What does DID Names manage?

    Domain management and DID methods belong to different layers.