> 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/decentralization-and-caps.md).

# Decentralization and CAPS

Cifer is designed as a fully decentralized security network rather than a privacy application backed by one private server.

### Network roles

| Participant  | Role                                                                                                  |
| ------------ | ----------------------------------------------------------------------------------------------------- |
| Operators    | Run authorized network infrastructure and lock `$CAPS` as economic commitment.                        |
| Delegators   | Delegate `$CAPS` to participating operators and share in network participation under published rules. |
| Applications | Request Cifer encryption and access-control operations.                                               |
| Users        | Use Cifer-enabled products without needing to understand the underlying token mechanics.              |

The security economy follows a delegated-proof-of-stake-style model: operators lock `$CAPS`, while delegators can support selected operators. Exact rewards, slashing conditions, admission rules, and governance parameters require separate published specifications before they should be treated as live commitments.

### CAPS consumption

`$CAPS` is the network utility used for Cifer operations. Encryption activity consumes `$CAPS` according to the network's configured fee model. This connects application usage to network demand.

{% hint style="warning" %}
This page explains intended network utility. It is not an investment promise and does not imply a guaranteed token price, return, reward rate, or yield.
{% endhint %}

### Verify the network

Use the [Cifer Network Explorer](https://explorer.cifer-security.com/) to inspect the state currently exposed by the public indexer. Explorer data should be treated as the authoritative public view only for the fields it actually displays.


---

# 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/decentralization-and-caps.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.