# Technical Highlight

### 1. Disaster Recovery Guarantee

The **Proof of Data Reduplication and Recovery (PoDR²)** protocol is designed to ensure the validity and availability of stored data by challenging storage nodes regularly. To prevent data loss and maintain data integrity in any situations, such as when some storage nodes are offline or even if a disaster occurs in part of the internet or data centers, the data files and can be recovered because of the redundant and recovery mechanism.

### 2. Verifiable Unused Storage

The **Proof of Idle Space (PoIS)** is designed to verify whether storage nodes have honestly contributed available storage resources to the CESS network, which will be used to store user data. Storage nodes can also exchange their storage contributions for incentives.

### 3. Smart Space Management

The CESS network aggregates storage space contributed by storage nodes from around the world in what we call Smart Space Management. For storage nodes, the committed storage space will be flexibly allocated and used by the CESS network. For users, it makes the CESS network like cloud storage, with features of horizontal scalability, elasticity, and durability.

### 4. Unified Storage Price

Unlike the storage space bidding of alternative decentralized storage protocols, CESS users only need to bid on a single price point on CESS storage. CESS middle layer has a pricing mechanism to calculate an optimized price point for storage users while balancing the incentives of storage providers.

### 5. IPFS Compatiblity

{% hint style="info" %}
Will be launched in 2026 Q4
{% endhint %}

CESS is compatible with IPFS standard and allows developers to integrate their dApps with an array of storage solutions that utilize IPFS. Data stored on CESS can also be addressed with cryptographic hashes, making the content immutable and tamper-resistant.

### 6. Secure Data Access

{% hint style="info" %}
Will be launched in 2026 Q3
{% endhint %}

**Proxy Re-encryption Technology (PReT)** is built on top of Public Key Encryption to allow users to authorize decryption permissions to others without disclosing the data's contents. User data is also processed and accessed in [Trusted Execution Environment](https://en.wikipedia.org/wiki/Trusted_execution_environment) (TEE) within the storage nodes.

### 7. Fast Data Retrieval

Data indexing and Content Decentralized Delivery Network (CD²N) improve searching and download speed from user endpoints. Consensus mechanism has been iterated on top of [Polkadot GRANDPA](https://wiki.polkadot.network/docs/learn-consensus#finality-gadget-grandpa) to achieve low gas fees and high transaction throughput.

### 8. Data Ownership Traceability

{% hint style="info" %}
Will be launched in 2026 Q4
{% endhint %}

Data ownership can be verified with **Multi-format Data Rights Confirmation technology (MDRC)**. This protocol extracts fingerprints from all data and permanently stores them on-chain for traceability.

### 9. CESS AI-LINK

{% hint style="info" %}
Will be launched in 2025 Q4
{% endhint %}

Various organizations possess private data, some of which is sensitive or restricted by national laws, hindering its sharing for AI development. The CESS network offers a solution by facilitating the exchange of encrypted parameters and models through **CESS AI-LINK**, ensuring compliance with privacy regulations. This enables the creation of a global model where data remains secure and local, yet contributes to a broader industry or global AI framework without compromising privacy or regulatory compliance.


---

# 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://doc.cess.network/readme/technical-highlight.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.
