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
    • Keeta vs. Ethereum
    • Keeta vs. Ripple
    • Keeta vs. Solana
  • Other Documentation
    • Official Links
    • Tokenomics
Powered by GitBook
On this page
  1. Scalability

Eliminating Mempools

PreviousSeperating Nodes from HardwareNextIdentity Profiles

Last updated 1 month ago

A key feature of Keeta Network is the elimination of memory pools, or "mempools." In traditional blockchain networks, mempools serve as waiting areas for transactions before they're added to a block. This can lead to delays and increased transaction fees during periods of high network activity. Keeta's architecture bypasses this issue entirely. By leveraging the DAG structure and advanced consensus mechanism, transactions can be quickly validated and incorporated into the network without the need for a mempool intermediary. The result is fast transaction processing and significantly reduced fees.

Traditional blockchains utilize mempools as waiting areas for transactions.