# Protection From Common Attacks

Keeta has taken extensive measures to ensure that the network is built to be secure against common blockchain attacks.

**Sybil attack**

One of the predominant concerns in decentralized systems is the Sybil attack, where a single adversary controls multiple [nodes](/components/nodes.md) on the network, effectively trying to subvert the network’s functionality. Such an attack can disrupt honest nodes from achieving consensus or facilitate malicious activities.

To counteract this, Keeta Network employs the use of X.509 certificates for certifying endpoints for representatives. This certification process ensures that each representative on the network is authenticated and can be trusted. X.509 certificates provide a standardized way of verifying the identity of participants and tying them to a public key infrastructure (PKI), making it computationally expensive and logistically challenging for an attacker to create a significant number of Sybil nodes.

By relying on the trusted certification process, not only does Keeta Network dramatically reduce the potential for Sybil attacks, but it also establishes an added layer of trust among participants. This approach ensures that network nodes represent unique, authenticated entities, effectively fortifying the network’s resilience against such threats

**51% attack**

In blockchain system, a 51% attack refers to a situation where a single entity or coalition controls more than half of the computational power (for Proof of Work systems) or more than half of the authority (in Proof of Stake systems), enabling them to doublespend coins, prevent transaction confirmations, or halt the creation of new blocks. Such dominance poses a severe threat to the integrity and trustworthiness of the network.

Keeta Network implements a proactive voting system to mitigate this threat. If a single representative amasses more than 50% of the voting weight, the Keeta Network protocol automatically adjusts the normal threshold for voting. This adaptive mechanism ensures that at least onetwo other representatives are required to reach a consensus, regardless of how much voting weight the dominant representative holds.

This safeguard not only ensures that no single representative can unilaterally dictate the network’s decisions but also promotes a decentralized and democratic ethos within Keeta Network. Such a mechanism reinforces the network’s resilience against centralized threats, preserving the foundational principles of decentralization and security that Keeta Network upholds.

**Spam attack**

In the decentralized environment of blockchain systems, spam attacks often manifest as an influx of legitimate yet superfluous transactions. These transactions, while valid in their structure, are intentionally designed to flood the network, causing bottlenecks, delays, and inefficiencies.

Keeta Network employs a strategic approach to counter such spamming tactics. Firstly, the network’s design incorporates a two-phase voting process, which acts as an initial filter to mitigate the volume of these transactions. However, in situations where an actor is persistent in dispatching a large number of genuine but unnecessary transactions, representatives on Keeta Network have the agency to respond. Representatives can observe transaction patterns and, upon identifying an attempt to spam the network, have the discretion to adjust transaction fees.

By ratcheting up these fees in response to abnormal transactional activity, Keeta Network introduces a financial deterrent. This increased cost makes it prohibitively expensive for malicious entities to continue their spamming efforts. Furthermore, representatives can also choose to decline voting for these transactions entirely, effectively blocking them from being added to the blockchain. This dual-layered approach ensures that Keeta Network remains resilient against transactional spam, ensuring smooth operations and preserving network integrity.

**Denial of service attack**

A Denial of Service (DoS) attack aims to render a service unavailable by overwhelming it with traffic or exploiting specific vulnerabilities. In blockchain contexts, DoS attacks can severely hamper network operations, affecting all users connected to the network.

Keeta Network’s design incorporates preemptive measures against DoS attacks. The aforementioned twophase voting process not only helps against spam attacks but is also effective in mitigating the impact of DoS attacks. By utilizing HTTPS in the voting process, Keeta Network can employ existing DDoS and DoS prevention mechanisms to safeguard the network.

Additionally, representatives observing abnormal traffic or suspicious patterns indicative of a DoS attack can start imposing fees on suspected malicious actors. This proactive stance not only helps to minimize the impact of DoS attacks but also empowers the representatives to maintain the network’s integrity actively.

\ <br>


---

# 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/security/protection-from-common-attacks.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.