> For the complete documentation index, see [llms.txt](https://doc.heresprotocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.heresprotocol.com/concepts/fees-limits-statuses.md).

# Fees, Limits, and Statuses

## Fees

Default repository configuration:

| Fee           | Default  | Purpose                                              |
| ------------- | -------- | ---------------------------------------------------- |
| Creation fee  | 0.05 SOL | Paid when creating a capsule.                        |
| Execution fee | None     | Distribution sends the full available vault balance. |

The creation fee is controlled by the on-chain fee configuration. Production deployments should display its current value before every signing step.

## Modification Limit

The web app retains a local modification counter for legacy flows. For new capsules, the stronger on-chain boundary is the inheritance seal: beneficiary shares and NFT assignments can be written while the capsule is a draft, but the program rejects every edit after sealing.

## 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                                                                                           |
| -------- | ------------------------------------------------------------------------------------------------- |
| Draft    | Capsule accounts exist, but commitment-bound arming did not complete. The capsule cannot execute. |
| Active   | Capsule can still be refreshed by the owner.                                                      |
| Expired  | Inactivity deadline has passed.                                                                   |
| Executed | Execution timestamp is set.                                                                       |

A finalized capsule has no live status account because finalization closes the Switch, BeneficiarySet, and Vault. The wallet can then create a fresh lifecycle.

## 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
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 following URL with the `ask` and `goal` query parameters:

```
GET https://doc.heresprotocol.com/concepts/fees-limits-statuses.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.