> For the complete documentation index, see [llms.txt](https://docs.aethir.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aethir.com/aethir-network/the-checker/proof-of-capacity-and-delivery.md).

# Proof of Capacity and Delivery

### **Proof of Capacity (Liveness)**

Recognizing and rewarding the readiness of node operators is paramount. Even when there's a dormant phase without active compute contribution, Aethir recognizes and rewards the availability of node operators. This mechanism promises a baseline level of compute so that end users always get the resources they need, even during demand spikes. Proof of Capacity checks are made by Checkers every 15 minutes.

### **Proof of Delivery**

Container performance is closely monitored to ensure quality. Checkers make sure that service requests are completed according to Aethir’s quality standards. This is an essential service that results in rewards and fees being paid to the resource owner or its stake being slashed. It also has an impact on future scheduling possibilities.


---

# 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://docs.aethir.com/aethir-network/the-checker/proof-of-capacity-and-delivery.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.
