Keeta Network
  • Introduction
  • Architecture
    • Data Structure
    • Consensus
      • Voting Power
      • Votes
      • Vote Stapling
  • Components
    • Ledger
    • Blocks
    • Nodes
      • Ledger Pruning
    • Accounts
      • Permissions
    • Key Pairs
      • Storing Key Pairs
    • Certificates
      • Creating and Attaching Certificates
  • Security
    • Digital Signatures
    • Post Quantum Readiness
    • Data Integrity
    • Protection From Common Attacks
  • Scalability
    • Benchmarks and Performance Metrics
    • Seperating Nodes from Hardware
    • Eliminating Mempools
  • Features
    • Identity Profiles
      • Utilizing Identity Profiles
    • Native Tokenization
      • Creating Tokens
      • Built-in Rules Engine
    • Anchors
      • Creating an Anchor
  • Applications
    • Public Network
    • Private Sub Network
  • Industry Comparison
    • Keeta Network's Advantage
    • Resolving the Blockchain Trilemma
  • Other Documentation
    • Official Links
    • Tokenomics
Powered by GitBook
On this page
  1. Components
  2. Certificates

Creating and Attaching Certificates

PreviousCertificatesNextDigital Signatures

Last updated 3 months ago

Certificate Authorities (CAs) on Keeta Network are entities that issue and manage digital , serving as validators of identity and attributes for network participants. Each CA is responsible for verifying information, issuing certificates tied to users' public keys, and managing the lifecycle of these certificates. Any party can become a CA, but certificates that are provided by trusted CAs will inherently be more widely accepted than certifcates provided by unknown parties.

A client initiates the process of getting a certificate by generating a key pair and requesting a specific certificate from a CA, providing the necessary information and their public key. The CA then verifies this information and generates a certificate restricted to the user's public key. The user requests the attachment of this certificate to their account, which the Network promptly executes. With this verified credential, the user's information can now be verified across multiple parties instantly without repeating the verification process. The certificate can be provided to any relevant party on the network.

This streamlined process creates a single, verifiable identity with associated certificates usable across multiple actions within the Keeta ecosystem. The user's , securely stored on their device, links directly to their identity, enabling instant verification for each new service interaction.

certificates
key pair