# Keeta vs. Ripple

Ripple has long faced criticism over centralization concerns due to its consensus mechanism, which depends on a limited number of trusted validators—fewer than 35—to maintain the ledger. With Ripple Labs operating many of these validators and holding significant influence over the network, it forces a centralized structure, increasing the risk of manipulation and governance issues. In contrast, Keeta offers a completely decentralized version of the network. By employing Delegated Proof of Stake (dPoS) and a Directed Acyclic Graph (DAG) structure, Keeta allows for a broader, more decentralized set of validators to govern the network and enables the network participants to choose these validators. Keeta also provides the ability to launch subnets, which are private versions of the network that can be utilized for a variety of use cases, allowing operations to be completed outside of the main blockchain and in a centralized environment, but with the same performance.

Ripple's XRP Ledger lacks capabilities in tokenization, built-in rules, identity management, and flexibility for handling diverse use cases. Its functionalities are largely limited to payment-related operations, restricting its versatility. Although Ripple is developing more advanced programmability—such as Ethereum Virtual Machine (EVM)-compatible sidechains to enable smart contracts—these efforts are still in progress and may inherit issues similar to Ethereum, including scalability challenges and high transaction costs.

Keeta, on the other hand, eliminates the need for external smart contracts by incorporating a built-in rule engine and tokenization system that covers most of the real-world use cases. By avoiding the complexities of general-purpose smart contracts, Keeta inherently provides functionalities like data access, identity management, and customizable rules within the platform.

<table data-full-width="true"><thead><tr><th>KEETA</th><th>RIPPLE</th></tr></thead><tbody><tr><td>10,000,000 TPS</td><td>1,500 TPS</td></tr><tr><td>400 MS settlement times</td><td>3000 - 5000 MS settlement times</td></tr><tr><td>≈ $0.00005 transaction fee</td><td>≈ $0.0002 transaction fee</td></tr><tr><td>Delegated Proof-of-Stake</td><td>Ripple Consensus Algorithm</td></tr><tr><td>Native Token Implementation</td><td>Lacks Sophisticated Programmable Contract Capabilities</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.keeta.com/industry-comparison/keeta-vs.-ripple.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.