> 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/surfaces/ledger.md).

# Ledger

The Ledger is where the shrine's economic promise is kept in public: a running record of **fee-share epochs** and the **distributions** made to imprinted wallets at the end of each one.

![Ledger](/files/Mx3HRj5IQtpLdy9f1gpQ)

## Epochs

* **Cadence:** weekly.
* **Signing:** every distribution is signed by a Ledger hardware wallet and executed manually. Nothing is automated.
* **Fee share formula:** at epoch close, fees generated on-chain by the vessels' activity are split **equally** across all imprinted wallets.

Each epoch card on the page shows:

* The epoch window (start → end).
* Total fees accrued to the vessels during that window.
* Number of imprinted wallets eligible for that epoch.
* The per-wallet share.
* The list of distribution signatures, each linked to Solscan.

## Statuses

An epoch on the Ledger appears in one of three states:

1. **Accruing** — the current, open epoch. Fees are still adding up.
2. **Pending distribution** — the epoch has closed; the operator has not yet signed the payout batch.
3. **Distributed** — payouts are on-chain. Each signature is public.

## Why manual signing

Manual, hardware-signed distribution keeps the shrine honest in the simplest possible way: there is no hot key on a server that could be exfiltrated, and no automated flow that could quietly drain the treasury. Every payout is a deliberate human act.

For the deeper formula, see [Fee Sharing & Epochs](/thesanctum-docs/mechanics/fee-sharing.md).


---

# 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/surfaces/ledger.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.