> For the complete documentation index, see [llms.txt](https://docs.talus.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talus.network/talus-docs-v2.1.0/guides/vision-explorer/leaders.md).
# Vision Leaders
{% hint style="info" %}
**Audience:** Anyone asking who dispatches work on this network and what is staked behind them.
**Goal:** Read the leader directory, a leader's page, and the priority-fee vault that pays them.
{% endhint %}
A **leader** is the only party that can dispatch a task occurrence into an execution; the `$US` staked behind it is an economic eligibility and accountability signal, not proof that a Tool result is true. When your run sits at **Advertised**, a leader is what it is waiting for. Vision's leader surface is read-only — staking and unstaking need capabilities a browser does not hold. Result truth comes from the selected verifier mode and its evidence; start with [Verifiers and Result Trust](/talus-docs-v2.1.0/concepts/04-verifiers-and-result-trust.md).
### The directory
**Network → Leaders** enumerates the whole leader registry (like [Tools](/talus-docs-v2.1.0/guides/vision-explorer/checking-tools.md), no paging — filters run over the complete set):
* **Stat cards** — **Registered leaders**, **Total staked** (`$US`), **Unbonding**.
* **Search** — name, region, or capability id; **Filter by status** — **Active** / **Inactive**; **Sort** — **Stake**, **Earnings**, **Delegators**, **Id**.
Each row: the published provider name and region, status (**Active** / **Suspended** / **Slashed**), the `$US` pooled behind it, the number of distinct stake positions (1 = self-staked only), any retained/deployment-specific priority-fee share or US-exposure display, and a marker when the stake is **below the registry's configured minimum**. The protocol does not expose a generic claimable-SUI field on the Leader record.
Two `0` values are *unset*, not zero, and render as **Unconfigured**: a minimum stake of 0 (so no leader is marked eligible against a threshold nobody set) and an exchange rate of 0 (see the vault below). An unbonding duration of 0 is a genuine "no delay".
The Leaders tab, with the priority-fee vault section below the directory.
#### The leader page
`/explorer/leader/` is routed by the leader's capability id — a leader is identified by a capability object, not by an object of its own.
* **Identity** — **Capability id**, **Status**, **Eligibility**.
* **Published metadata** — what the leader provider published about its public record.
* Stake — **Staked pool** (`$US`), **Total shares**, **Share value**, **Unbonding delay**, and any retained/deployment-specific priority-fee share or US-exposure display. Pool and shares are separate on purpose: slashing cuts the pool and leaves shares untouched, so a pool worth less per share than it started is labelled **Pool devalued by slashing**. Shares do not by themselves authorize a withdrawal; a matching registered Leader capability and the vault’s withdrawal conditions are required.
* **Staking history** — **Stake deposited**, **Unstake requested**, **Unstake claimed**, **Stake slashed**, newest first, with `$US` and shares as *separate* columns. An unstake request shows shares but no `$US` (the amount is fixed only on claim); a slash shows `$US` but no share movement. The observed pool is the same number whether it shrank from an unstake or a slash; only this history says which.
#### The priority-fee vault
Below the leaders list sits the **Priority-fee vault**: the SUI deposited as priority fees, the **`$US` liquidity**, the **Exchange rate** (`$US` atomic units per 1,000,000 MIST — **Unconfigured** on Testnet, meaning the swap is closed until a rate is set, not free), and the vault object itself. A retained deployment may show a claimable-fees card, but it is not a generic SUI balance on the Leader record; the withdrawal path returns proportional US only after SUI liquidity reaches zero and a matching registered Leader capability authorizes it. Its activity — **Fee deposited**, **Fee withdrawn**, **Rate configured**, swaps — is listed beneath. An unreadable vault says so; it is never rendered as a network where nobody gets paid.
---
# 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://docs.talus.network/talus-docs-v2.1.0/guides/vision-explorer/leaders.md?ask=&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.
