> For the complete documentation index, see [llms.txt](https://cifer.gitbook.io/cifer-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cifer.gitbook.io/cifer-docs/network-whitepaper.md).

# Network whitepaper

Cifer separates control, cryptographic processing, custody, and storage so that no single component is trusted with the entire security problem.

```mermaid
flowchart TD
    U["Cifer applications and SDKs"] --> C["Decentralized control plane"]
    U --> O["Cryptographic orchestration"]
    C --> O
    O --> T["Hardware-isolated execution"]
    T --> K1["Custody node 1"]
    T --> K2["Custody node 2"]
    T --> K3["Custody node 3"]
    T --> K4["Custody node 4"]
    T --> K5["Custody node 5"]
    U --> S["Encrypted or content-addressed storage"]
    C --> X["Verifiable audit records"]
```

### Decentralized control plane

The control plane records the state required to verify who owns a protected secret, who has delegated access, which network participants are authorized, and which security-relevant events occurred.

This layer does not need to hold plaintext user data or a universal decryption key. Its purpose is to make authorization and network state independently verifiable.

### Cryptographic orchestration

The orchestration layer coordinates key creation, fragment retrieval, policy verification, encryption, and decryption. Sensitive reconstruction and cryptographic operations are designed to occur inside hardware-isolated execution environments.

Cifer refers to the verifiable orchestration environment in which fragments are temporarily reconstructed as the **Blackbox**. A reconstructed key is an operation-time value, not a master key stored for later reuse.

### Distributed custody

Private decryption capability is split into five fragments. Any three are required for an authorized operation. Fewer than three fragments are insufficient.

### Storage

Encrypted content can remain in the storage system selected for the application. Cifer protects the cryptographic capability required to use it. Public key material and integrity commitments may use content-addressed or verifiable storage.

### Design outcome

The architecture reduces dependence on a single administrator, key-management server, database, or hardware module. It does not eliminate every possible risk; its guarantees depend on correct implementation, independent node operation, secure execution environments, and sound operational controls.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://cifer.gitbook.io/cifer-docs/network-whitepaper.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.