You are here. See how this question connects to other ideas.
Select a node to open its page · Expand to read within the map
Learning path
From presenting a credential to accessing a resource
Follow an upload request through identity, evidence, trust and permission.
Imagine an application asking to upload to your space. Follow this path to distinguish who requests the operation, what evidence they present, whose claims the service accepts and which action it permits. Successful presentation is one step in the interaction.
After reading, ask whether an upload should still be allowed when a credential passes its signature check but ownership has changed. The answer depends on current state and service authorization rules, not only the card in a wallet.
Along this path
- Does control prove real-world identity?
Proving control of an identifier and establishing a real-world identity are different tasks.
- Can every key in a DID document serve every purpose?
Separate a verification method from its permitted verification relationship.
- What does a verifiable credential make verifiable?
Check authorship and integrity, then decide whether to accept the claim.
- Must a credential’s subject also be its holder?
Separate who makes a claim, who it describes, who presents it and who verifies it.
- Why trust an issuer?
Checking a credential protection mechanism differs from deciding whether to trust its issuer.
- Does a valid signature mean a credential is still usable?
Check validity periods, suspension and revocation separately.
- What does DID Connect connect?
Understand the exchange between an application request and the user’s identity tool.
- Does presenting a Passport transfer it?
Proving eligibility and transferring an asset are different operations.
- How does a resource NFT relate to access?
A rights object supplies evidence; a service decides which operation it permits.