Keeta Network
  • Introduction
    • Start Developing
    • Create Your First Account
    • Send a Transaction
  • Architecture
    • Data Structure
    • Consensus
      • Voting Power
      • Votes
      • Vote Stapling
  • Components
    • Ledger
      • Get Ledger History
    • Blocks
      • Create a Block
      • Operations
        • Send
        • Receive
        • setInfo
        • modifyTokenSupply
        • modifyTokenBalance
        • updatePermissions
    • Nodes
      • Ledger Pruning
    • Accounts
      • Permissions
      • Storage Accounts
        • Create a Storage Account
        • Single-Token Storage Account
    • 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
      • Token Creation
        • Mint Tokens
        • Burn Tokens
        • Set Permissions
      • Built-in Rules Engine
    • Anchors
      • Creating an Anchor
  • Applications
    • Public Network
    • Private Sub Network
  • Industry Comparison
    • Keeta Network's Advantage
    • Resolving the Blockchain Trilemma
  • Guides
    • Tokenizing Real-World Assets
  • Other Documentation
    • Official Links
    • Tokenomics
    • Roadmap
Powered by GitBook
On this page
  1. Components
  2. Key Pairs

Storing Key Pairs

PreviousKey PairsNextCertificates
CtrlK

Keeta provides multiple options for key storage to cater to different security needs and use cases. For high-security applications, Hardware Security Modules (HSMs) can be used to store private keys, providing an additional layer of protection against unauthorized access. For more consumer-oriented applications, on-device storage solutions can be utilized.

For example, a secure financial app on iOS could store private keys within the Secure Enclave on the user's device, giving them immediate access to their accounts and transactions. This approach ensures that sensitive data remains protected by hardware-level security, while still allowing for quick and convenient user interactions with their financial information.