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. Security

Data Integrity

PreviousPost Quantum ReadinessNextProtection From Common Attacks
CtrlK

Ensuring data integrity is fundamental to the operation and trustworthiness of any blockchain system. In the context of Keeta Network, where transactions are validated through a meticulous two-phase voting process, the preservation of untampered data becomes even more vital.

Append-only Ledger: Once a transaction has been validated and appended to the blockchain, it becomes an immutable record. This means that it cannot be altered or deleted without a consensus from a quorum of the network’s representatives. This feature ensures that historical data remains consistent.

Cryptographic Hashing: Keeta Network employs SHA3-256 hashing for its records. This cryptographic hashing ensures that no alteration can take place within any record without affecting this record.

Chain Consistency: Every block on Keeta Network's blockchain contains a reference to the previous block through its cryptographic hash. This chaining mechanism ensures that the blocks are in the correct sequence, and any attempt to modify a block would not only affect that block but also every subsequent block, making unauthorized changes easily detectable.

Use of TLS for Non-repudiation: Keeta Network relies on Transport Layer Security (TLS) not just for encryption but importantly for non-repudiation. By utilizing HTTPS for all communication, it is possible to ensure that requests are being directed and delivered to the desired representatives.

By implementing these mechanisms into its core, Keeta Network ensures the integrity of its data. This trustworthiness is foundational for the platform’s wide adoption and the overall security of the network.