Keeta Network is a blockchain system designed to serve as a common layer for various payment networks and assets, aiming to bridge traditional financial institutions and decentralized technologies. It is engineered as a cloud-scale, cloud-native solution focused on high transaction throughput, low latency, and built-in features for compliance and tokenization.
Keeta Network was developed as an engineering company building resilient and scalable solutions for the financial community. The project aims to provide a link between traditional financial institutions and decentralized blockchain-based technologies. KeetaNet, the underlying blockchain system, implements a distributed ledger with native multi-token support, an extensible permissions system, and capabilities designed to meet the requirements of a regulated ledger for handling complex financial transactions. It builds upon concepts from other projects to achieve high transaction volume while maintaining low latency. KeetaNet is designed to scale linearly with hardware utilization, leveraging cloud computing technologies.
The system distinguishes itself through a unique hybrid Directed Acyclic Graph (DAG) design where each account has its own chain, a client-directed transaction validation process, and a cloud-scale architecture built atop common protocols like HTTP and WebSockets. Beyond scalability, KeetaNet incorporates features essential for a reliable digital economy, including compliant handling of Know Your Customer (KYC) and Anti-Money Laundering (AML) information, extensibility for network participants to define policies, native token support for asset representation, atomic swaps for direct token exchange, and adaptable permissions for asset issuers to control interactions.
History
Keeta was founded as an engineering company focused on creating scalable solutions for the financial sector. The KeetaNet whitepaper, detailing the system's architecture and protocols, was published on March 12, 2025 [1]. The project came out of stealth mode in March 2025 with the launch of its native token, KTA [2]. A testnet was released in April 2025 [2]. In May 2025, Keeta announced a partnership with FootPrint as the first KYC provider on the network and revamped its test network wallet and explorer [2].
Keeta Network is designed with several core features aimed at enabling a unified network for payments and asset transfers:
- Cross-Chain Asset Movement: Keeta acts as a unifying layer to facilitate direct cross-chain transactions and interactions across multiple blockchains [3].
- Real-World Asset Tokenization: The network supports the creation of tokens to represent any asset, enabling trading and unlocking liquidity [3].
- Built-in Compliance: Keeta incorporates features for regulatory compliance and digital identity verification, allowing trusted KYC providers to issue secure digital certificates for user accounts. These certificates enable instant verification while maintaining privacy and security [3] [1].
- Scalability: The system is designed for high performance, aiming for 10 million transactions per second (TPS) and 400ms settlement times [3] [4].
- Built-in Tokenization and Rule Engines: The protocol natively integrates engines for creating and managing digital or real-world assets with built-in control and compliance [3].
Eric Schmidt, former CEO of Google and a Keeta investor, has commented on the network's performance:
"Keeta is orders of magnitude more scalable and efficient than existing solutions." [3]
KeetaNet is built as a distributed ledger system with a unique architecture and consensus mechanism.
KeetaNet functions as a distributed database, modeling itself as an interface to its underlying ledger. Its design draws parallels to both contemporary database systems and modern web backend design, leveraging best practices from these fields for scalability [1].
Key architectural aspects include:
- Hybrid DAG Design: The primary data structure is a directed acyclic graph (DAG), but implemented as a "virtual DAG". Each account forms the basis of its own chain, and inter-account interactions are virtual links between these chains. This differs from monolithic blockchain structures [1].
- Client Directed: Changes to the ledger are validated through a two-step process directed by the entity requesting the change. This process assumes non-conflicting transactions initially [1].
- Cloud-Scale: The system is built atop common protocols like HTTP and WebSockets to take advantage of the scaling capabilities of cloud providers using technologies such as serverless processing [1].
KeetaNet utilizes an enhanced Delegated Proof of Stake (dPoS) consensus mechanism. Accounts can delegate their balance of the base token to a representative, which grants the representative "voting power" proportional to the total delegated balance. Representatives are actors within the system that vote on the permissibility of blocks [1].
The voting power required for a quorum is adaptive, increasing if a single representative holds a disproportionate amount of power to ensure consensus requires multiple representatives [1].
Transaction validation is handled by representatives through a two-phase voting mechanism directed by the client [1].
- Temporary Votes: A client requests temporary votes from a quorum of representatives for a set of blocks. Representatives issue temporary votes based on the validity of the blocks at that time. This phase establishes a primary consensus and determines the quorum [1].
- Permanent Votes: Upon receiving a quorum of temporary votes, the client requests permanent votes from the subset of representatives who provided temporary votes. Permanent votes are cast only after the quorum is determined, preventing premature approval [1].
Once permanent votes from a quorum are obtained, the votes and blocks are broadcast to the network as a consolidated package called a vote staple [1].
KeetaNet employs a data storage model designed for high-performance read and write operations while maintaining data integrity and supporting concurrent operations [1].
- Concurrency Control: Managed through an Optimistic Concurrency Control (OCC) mechanism. Transactions are initially assumed non-conflicting and proceed without locks. Conflicts are detected and addressed afterward, reducing latency [1].
- Consistency: Provides different levels of consistency:
- Fully Consistent Writes: Achieved by obtaining a quorum of representatives, ensuring data is consistently replicated [1].
- Eventually Consistent Reads: Permitted from any representative, optimizing for latency [1].
- Fully Consistent Reads: For critical operations, confirmation from a quorum of representatives is obtained [1].
- Ordering: Implements partial ordering of transactions, meaning transactions are ordered only in relation to those required by ledger constraints. This contrasts with total global ordering and enables parallel processing [1].
The system defines specific data formats for its components [1].
- Accounts: Refer to either the public key of a key-pair (Keyed accounts) or deterministically generated addresses (Generated accounts). Each account has a separate ordered blockchain within the DAG. Generated accounts include Network accounts, Storage accounts, and Token accounts [1].
- Operations: High-level instructions to modify the ledger state, limited to a predefined set (e.g., SEND, SET REP, CREATE IDENTIFIER). Operations are self-contained within a block [1].
- Blocks: The fundamental mechanism for ledger updates, containing an ordered set of operations performed by a specific account. Blocks are encoded in ASN.1 DER and are versioned and dynamic in size [1].
- Votes: Encoded as X.509 certificates, used by representatives to communicate their intention to add blocks to their ledger. Votes can be temporary or permanent and contain issuer, serial, block hashes, timestamps, and a signature [1].
- Staples: Also known as Vote Staples, these bundle multiple blocks and votes together for simultaneous voting and publication. Staples are the fundamental unit of exchange and function as journaled updates. If any block in a staple is invalid, the entire staple is rejected [1].
- Bootstrapping: A protocol for new or offline nodes to bulk-fetch missed ledger changes by requesting staples after a given timestamp via HTTP [1].
- Permissions: Uses "base permissions" (symbolic names with specific values) and "external permissions" (arbitrary flags managed externally), encoded as bit-fields. Permissions are managed via an Access Control List (ACL) with a defined hierarchy [1].
- Account Certificates: X.509 certificates associated with accounts to authenticate and verify identity without storing Personally Identifiable Information (PII) on the ledger. Certificates are signed by a Certificate Authority (CA) and must share the same public key as the account [1].
The network is initialized using an "initial trusted account" with exclusive permission to create valid votes when there is no delegated weight. This account funds initial accounts and delegates weight to representatives, bypassing permission requirements for initial blocks and the base token's chain [1].
KeetaNet incorporates several security measures to protect the network and data [1].
- Digital Signatures: Supports ECDSA (with secp256k1 and secp256r1) and Ed25519. The system is extensible to support additional algorithms, including post-quantum cryptography (PQC) [1].
- Hashing: Uses SHA3-256 for cryptographic hashing [1].
- Use of Cryptosystems: Digital signatures are used for signing blocks and votes, and cryptographic hashing is used for referencing blocks [1].
- Append-only Ledger: Once validated and appended, transactions are immutable and cannot be altered or deleted without a quorum consensus [1].
- Cryptographic Hashing: SHA3-256 hashing ensures any alteration to a record changes its hash, making tampering detectable [1].
- Chain Consistency: Each block references the previous block via its hash, guaranteeing correct ordering and making unauthorized modifications apparent [1].
- Use of TLS: Leverages Transport Layer Security (TLS) for encryption, authentication, and message integrity, enforcing HTTPS for communications [1].
KeetaNet aims to overcome common scalability limitations found in existing blockchain systems [1].
- Validation Architectures: Unlike linear chain structures (e.g., Bitcoin, Ethereum), KeetaNet's hybrid DAG design with per-account chains allows for more parallelism [1].
- Transaction Distribution: Employs "client directed" transaction distribution, where unconfirmed blocks are not exposed to the wider network but limited to voting representatives. Only fully accepted blocks are broadcast, reducing peer-to-peer network traffic [1].
- Protocols: Uses standard protocols like HTTP for consensus-related actions and WebSockets for peer-to-peer traffic, enabling integration with existing scaling solutions and cloud computing providers [1].
Benchmark tests have shown high throughput results. A Maximum TPS Throughput Test conducted on GCP Spanner on July 12, 2022, recorded 13 million TPS [1]. The network aims for 10 million TPS and 400ms settlement [3] [4].
KeetaNet is designed as a base layer for a cryptocurrency economy, suitable for various real-world applications [1].
- Cryptocurrency Central: With native tokenization, atomic swaps, and support for metadata, KeetaNet can act as a "Layer 2" for other cryptocurrencies by allowing high-throughput, low-latency transfers of wrapped tokens. Its compliance features enable compliance-based onboarding and off-boarding, positioning it as a "network of networks" [1].
- Blockchain Banking: Support for regulatory compliance primitives, such as limiting transactions based on appropriately issued certificates, makes KeetaNet suitable for a blockchain-based banking system. Its permissioning model allows for the creation and operation of stablecoins representing fiat currencies by regulated financial institutions [1].
- Digital Identity: By supporting identity verification using Public Key Infrastructure (PKI) and X.509 certificates, KeetaNet enables decentralized, user-controlled verification of attributes. Users maintain control over private information disclosure, and certificates can encode private attributes verified by trusted Certificate Authorities (e.g., KYC providers) without revealing the information publicly [1].
Keeta (KTA) is the native token of the Keeta Network. It serves as the base token for the network.
- Total Supply: 1,000,000,000 KTA [5].
- Max Supply: 1,000,000,000 KTA [5].
The circulating supply includes tokens available for trading, while the remaining supply is allocated to Team Vesting, Early Investors, Foundation Treasury, and Community/Ecosystem Reserve [5].
KTA tokens are traded on various decentralized and centralized exchanges. Popular exchanges for trading KTA include Aerodrome (Base), XT.COM, Uniswap V3 (Base), and LCX Exchange [6].
The KeetaNet whitepaper lists the following authors: Roy Keene, Tanveer Wahid, Ezra Ripps, and Ty Schenk [1]. Ty Schenk is also identified as the CEO of Keeta [7].
Keeta has announced a partnership with FootPrint, which serves as the first KYC provider on the Keeta Network. This partnership supports the network's built-in compliance features [2].