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. Why choose TNG Identity?

DID differentiators

Our unique difference

DID Method

Discover TNG's innovative digital identity solution on the BSV blockchain, featuring a secure data registry and a unique signature structure. Elevate your digital identity while enjoying the flexibility to revoke Verifiable Credentials (V.C.) and Decentralized Identifiers (DiDs) independently, all without compromising privacy. Our solution also supports the seamless designation of one or multiple issuers or verifiers from a single entity, providing you with unparalleled control over your identity experience.

DID Revocation

Our unique design approach supports a future-proof method to revoke V.C and DIDs. This process preserves privacy in PII information when revoking and verifying V.Cs and revoking and verifying DID status.

Key Rotation

The solution design includes the capability to rotate the cryptographic keys should the need arise. The UTXO associated with the DID Document presents a snapshot of the current DID Document.

If there is a requirement to change keys to either the DID Controller or Subject – the latest UTXO can be spent. This will create a new transaction – publishing the latest version of the DID with newly rotated keys.

DID Signatures

The TNG design utilizes the presence of Digital Signatures in blockchain transactions to bind the Subject and Controller keys to the credentials they publish.

This ensures that only the holder of the identity can bind these keys to the credentials. In addition, these keys can be considered legally binding as they fulfil the requirement for the digital signing process.

PreviousWhy choose TNG Identity?NextHow does TNG Identity work?

Last updated 2 days ago

📑