nChain Identity
Back to All
  • nChain Identity user documentation
  • šŸ“‘INTRODUCTION
    • Introduction to nChain Identity
    • Why choose nChain Identity?
      • DiD differentiators
    • How does nChain Identity work?
      • Data flows
      • Use cases and applications
    • Standards and regulations
  • šŸ“„nChain Identity Issuers
    • What is an issuer?
    • How to become an issuer?
    • Operating an issuer
    • What do issuers do?
    • Issuer API
      • Overview
      • Getting Started
      • Examples
        • Issue an email credential
        • Revoke a claimed email credential
      • API Documentation
        • Credential Offers
        • Agent
        • Claims
  • šŸ“‘NCHAIN IDENTITY VERIFIER
    • What is a Verifier?
    • Operating a verifier
    • How to become a verifier?
    • Verifier API
      • Overview
      • Getting Started
      • Examples
        • Verify an email credential
      • API Documentation
        • Verifiable Presentation
        • Verifying
        • Agent
        • SIOP
        • Templates
  • šŸ“„NCHAIN IDENTITY WALLET
    • What is the wallet for?
    • How to receive a Verifiable Credential?
    • How to share a Verifiable Credential?
  • šŸ“‘Privacy and Security
    • Privacy and Security Measures: NChain Identity Services
    • Revocation and data deletion
  • šŸ—ƒļøSELF-SOVEREIGN IDENTITY KNOWLEDGE
    • Self-Sovereign Identity
    • Actors
    • Decentralized vs Self-Sovereign Identity
    • Key Principles of Self-Sovereign Identity
    • Self-Sovereign Identity – Use Cases
    • Digital Trust
    • Some of the critical components of Self Sovereign Identity
      • Trust over IP
    • Some of the critical components of Decentralise ID
      • A Blockchain Tailored for Decentralized Identity
      • Decentralise Identifiers (DiD)
      • Verifiable Credentials
      • Verifiable Presentations
  • šŸ“‘GLOSSARY
    • Glossary
  • šŸ“„FAQs / HELP
    • Help & FAQs
      • What is a digital identity?
      • What is nChain Identity, and how does it work?
      • How is blockchain used in nChain Identity?
      • Compatible Blockchains for nChain Identity.
      • How can my business sign up for nChain Identity?
      • How is nChain Identity different to other identity solutions in the market?
      • Can nChain Identity communicate with other identity solutions?
      • What is nChain Identity doing with my data, and does it act as a data processor or controller?
      • What measures does nChain Identity take to protect user data?
      • What support is available for nChain Identity?
      • Can nChain Identity be integrated into our existing systems?
      • How can I get started with nChain Identity?
      • What countries is nChain Identity available in?
Powered by GitBook
On this page
  • Background to Model
  • Trust Over IP Model
  1. SELF-SOVEREIGN IDENTITY KNOWLEDGE
  2. Some of the critical components of Self Sovereign Identity

Trust over IP

PreviousSome of the critical components of Self Sovereign IdentityNextSome of the critical components of Decentralise ID

The digital economy is based on confidence—specifically, how confident people feel about conducting their work and lives online. While our world is highly connected, our online confidence is low. Privacy has been eroded, and we do not easily trust the identities of others online, nor what they send us. We need to address these issues and build online confidence for individuals and businesses without compromising on User Experience.

Background to Model

  • Developer communities recognized this new trust model could underpin an entire layer of Internet-scale digital trust infrastructure.

  • Initial efforts focused primarily on proving the technology side of the stack.

  • But customers began to seek real-world solutions.

  • This is when attention turns to the ā€œother halfā€ of the stack—the practical governance and policy questions that will drive business, legal, and social acceptance.

  • The result of which is the dual stack shown in the illustration.

  • Early versions of the ToIP stack reflected historical origins—technology on the left — real-world experience showed that governance should come first.

  • Implementing ToIP-based solutions should begin with business requirements and then move to policy requirements transparently communicated in governance frameworks.

  • Only then should you choose the technology components required to implement those policies.

Trust Over IP Model

šŸ—ƒļø