> 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/welcome/how-heres-protocol-works.md).

# How Heres Protocol works

Protocol Mechanics: Continuous Monitoring and Automated Distribution

Heres Protocol monitors your routine on-chain activity to determine your liveness, and only moves your assets according to strictly controlled procedures when specific conditions are met.

The entire lifecycle consists of 3 straightforward steps:

{% stepper %}
{% step %}

### **Setup & Encapsulation**

You create a unique, personal smart contract Vault on the protocol and deposit the assets you want to protect.

You "encapsulate" these assets by setting the wallet addresses of your Heirs, the distribution weights, and a 'Silence Limit' the threshold that determines your absence.
{% endstep %}

{% step %}

### **Liveness Monitoring (Passive Heartbeat)**

Once the Capsule is active, the protocol continuously observes your main wallet for on-chain transactions (swaps, staking, simple transfers, etc.).

We call this a **Passive Heartbeat**. You don't need to press any manual "I'm alive" buttons; simply using your wallet as you normally do will extend the safety of your vault.
{% endstep %}

{% step %}

### **Trigger & Distribution**

If not a single valid transaction occurs from your wallet within the Silence Limit you set, the protocol considers you absent.

Once the Capsule fires, the smart contract can immediately unlock and distribute your assets to your designated heirs according to your exact preset ratios.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Create Capsule now: <https://www.heresprotocol.com/create>
{% endhint %}


---

# 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/welcome/how-heres-protocol-works.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.