# Data Integrity

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.


---

# 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/data-integrity.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.