Skip to main content
Knowledge mapIdentity, permission and a way outIndustry 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.
← Blockchain and shared state

Learning path

Identity, permission and a way out

Eight questions about accounts, credentials, delegation, recovery and migration.

Signing in does not permit every action. Exporting data does not guarantee it can be used elsewhere. Follow accounts, eligibility, status, privacy, delegation, recovery and exit to examine which controls users actually retain.

This path develops Chapters 4–5 of 《区块链实战》, keeping its interest in user control while checking boundaries against later standards. Read each lesson independently, or start with identity and credentials if DIDs and credentials are new to you.

Along this path

  1. Why can one DID lead to two accounts?

    A shared identifier does not merge application records or permissions.

  2. Why trust an issuer?

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

  3. Does a valid signature mean a credential is still usable?

    Check validity periods, suspension and revocation separately.

  4. Why share a whole record to prove one qualification?

    Check disclosed fields, correlation, retention and the proof mechanism.

  5. How can an assistant act without your main key?

    Bound delegated work by resource, action, duration and revocation.

  6. Can a DID always be recovered after losing a key?

    Recovery depends on the method and the control arrangements already in place.

  7. Are dApps and Blocklets the same thing?

    Separate decentralization properties from application packaging and execution.

  8. What remains usable when a service closes?

    Separate exporting, verifying, continued access and running a replacement.