LogoLogo
Back to All
  • TNG Identity user documentation
  • 📑INTRODUCTION
    • Introduction to TNG Identity
    • Why choose TNG Identity?
      • DID differentiators
    • How does TNG Identity work?
      • Data flows
      • Use cases and applications
    • Standards and regulations
    • Portal API
      • Overview
      • Getting Started
      • API Documentation
        • App
        • Auth
        • Mail
        • Organisation Profiles
        • User Profiles
        • PSP > Product Manager > Customer User Api Key
        • PSP > Product Manager > User Manager
  • 📄TNG 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
        • Info
        • Auth
        • Media
        • Credential Offer Claims
        • Credential Offer Collections
        • Credential Offers
        • Credential Templates
        • Claim
        • Agent
  • 📑TNG 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
        • Info
        • Auth
        • Verifiable Presentation
        • Agent
        • SIOP
        • Templates
  • 📄TNG 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: TNG 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 TNG Identity, and how does it work?
      • How is blockchain used in TNG Identity?
      • Compatible Blockchains for TNG Identity.
      • How can my business sign up for TNG Identity?
      • How is TNG Identity different to other identity solutions in the market?
      • Can TNG Identity communicate with other identity solutions?
      • What is TNG Identity doing with my data, and does it act as a data processor or controller?
      • What measures does TNG Identity take to protect user data?
      • What support is available for TNG Identity?
      • Can TNG Identity be integrated into our existing systems?
      • How can I get started with TNG Identity?
      • What countries is TNG Identity available in?
Powered by GitBook

Copyright © nChain Licensing AG 2024

On this page
  1. INTRODUCTION
  2. How does TNG Identity work?

Use cases and applications

See some examples in how SSI could help improve your business

PreviousData flowsNextStandards and regulations

Last updated 1 day ago

Here are some ideas on how and when it is valuable to use TNG Identity. Also, an insight into the future features and ideas we are planning to support in our products in the following versions.

Here are some ideas on how and when it is valuable to use TNG Identity. Also, an insight into the future features and ideas we are planning to support in our products in the following versions.

  • Single player view The single-player view is for the service to have the capacity of creating a single source of truth for issuing VCs attributes and status. (e.g., for iGaming, a player marker of harms shared between multiple gaming platforms), Allowing a single individual to have multiple certifications from different certificate authorities under the same identity or identifier. Also, allowing users to obfuscate data and selectively disclose the required information.

  • Verify once validate many.

    • Verify once validated, many are for issuers and VCs authorities to provide a certified attribute of the same individual to multiple businesses or organizations.

    • The method proposed that each individual create a secure secret that will be protected and linked to an individual unique identifier (Such as biometrics, MFA, or a pre-determined unique number or such requirements that will be local to each jurisdiction). Based on that requirement, the user is mapped with the root key. From this point onwards, the user can be issued Verifiable credentials based on the business case. The user software will create an access token and submit it to the corresponding KYC entity to issue a new Verifiable Credential, which associates the user KYC dataset with the public key. This information, then, when published on the blockchain, becomes a public registry of an individual's identity without revealing any private KYC data for that individual.

  • Single Patient view. The single patient view is for the service that can create a single source of truth for certification attributes and status. (e.g., for patients in hospitals, medical facilities, laboratories, and pharmacies shared between multiple gaming platforms. It allows a single individual to have multiple certifications from different certificate authorities under the same identity or identifier. Also, it allows users to obfuscate data and selectively disclose the required information.

  • Digital Twin. Digital Twin is intended for collectables and assets of value trading and certification. It creates a single source of truth for certification attributes and status (e.g., collectables, art, wine, cars, etc.), Allowing individuals and businesses to verify authenticity and ownership. It also allows the CA to obfuscate data if necessary and selectively disclose the required information.

  • On-chain notarisation The future roadmap also considers tracing individuals' certification usage with TNG Events, which provides data integrity to the data and documentation request, management, checking, and validation process. Events ES can certify and guarantee data integrity for identity verification, validation, and management. process, including tracking a particular identity's certificate history based on a use case. See TNG EVENTS


📑