> For the complete documentation index, see [llms.txt](https://thesanctum.gitbook.io/thesanctum-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://thesanctum.gitbook.io/thesanctum-docs/mechanics/fee-sharing.md).

# Fee Sharing & Epochs

The shrine's economic promise is simple: **fees generated on-chain by the vessels are shared, equally, with every imprinted wallet, at the end of every weekly epoch, forever.**

## Cadence

* **Epoch length:** one week.
* **Close:** at the end of each epoch, the operator triggers the close from the admin surface (a `/api/public/hooks/close-epoch` endpoint).
* **Distribution:** after close, the payout batch is prepared and signed by a **Ledger hardware wallet**. Nothing is automated end-to-end.

## Formula

Let:

* `F` = total fees attributable to the vessels during the epoch (in SOL).
* `N` = number of imprinted wallets eligible for the epoch.

Then each eligible wallet receives:

```
share = F / N
```

That is: **equal split, no tiers, no weights**. Being imprinted first does not increase your share; being imprinted last does not decrease it.

## Eligibility

A wallet is eligible for an epoch if it was imprinted before the epoch's close timestamp. Wallets imprinted after close roll into the next epoch.

## Where distributions appear

Every distribution shows up on the [Ledger](/thesanctum-docs/surfaces/ledger.md) page as a set of Solscan-linked signatures. There is no off-chain "paid" flag; the ledger is the source of truth.

## Failure modes

* **No fees this epoch** — the epoch closes with `F = 0` and no distribution is made. The epoch is still marked closed.
* **No imprints yet** — the epoch closes with `N = 0` and no distribution is made.
* **RPC unavailable at close** — the close is retried; the operator will not sign a batch against stale data.


---

# 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://thesanctum.gitbook.io/thesanctum-docs/mechanics/fee-sharing.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.