# Fees, Limits, and Statuses

## Fees

Default repository configuration:

| Fee           | Default                 | Purpose                                        |
| ------------- | ----------------------- | ---------------------------------------------- |
| Creation fee  | 0.05 SOL                | Paid when creating a capsule.                  |
| Execution fee | 300 basis points, or 3% | Deducted during distribution where configured. |

Fee values are controlled by on-chain fee configuration and application constants. Production deployments should display current fee values before every signing step.

## Modification Limit

The web app tracks a default maximum of 3 capsule modifications per wallet in local state. Production deployments should clarify whether modification limits are enforced only by the client or also by protocol logic.

## Inactivity Period

The inactivity period controls when a capsule becomes eligible for execution. Defaults are configured in the app:

| Setting           | Default  |
| ----------------- | -------- |
| Inactivity period | 365 days |
| Delay days        | 30 days  |

Devnet builds may expose minute-based testing to make demos easier.

## Capsule Statuses

| Status   | Meaning                                      |
| -------- | -------------------------------------------- |
| Active   | Capsule can still be refreshed by the owner. |
| Expired  | Inactivity deadline has passed.              |
| Executed | Execution timestamp is set.                  |
| Inactive | Capsule is not active.                       |

## Delivery Statuses

| Status     | Meaning                                                |
| ---------- | ------------------------------------------------------ |
| Pending    | Delivery has not yet completed.                        |
| Dispatched | Delivery request was sent to CRE.                      |
| Delivered  | CRE reported successful message delivery.              |
| Failed     | Delivery failed and may need retry or operator review. |


---

# 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.heresprotocol.com/concepts/fees-limits-statuses.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.