> For the complete documentation index, see [llms.txt](https://resource-network.gitbook.io/resource-technical/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://resource-network.gitbook.io/resource-technical/05-protocol-and-network-governance/5.3-source-governance-token.md).

# 5.3 SOURCE Governance Token

SOURCE fulfils three essential functions within the ReSource Protocol:

1. Staked SOURCE carries a portion of the network’s risk, in return for staking rewards.
2. Staked SOURCE grants the owner voting rights on network decisions, as elaborated above.
3. Unstaked SOURCE may be used by members to pay network fees.

Unstaked SOURCE do not carry specific risks associated with credit lines, except the usual risks associated with the holding of assets of any kind.

The means and manner by which SOURCE is staked and by which risk is transferred to SOURCE Stakers is elaborated on in the chapters above. In short, initial risks are assumed by Underwriters, who stake SOURCE to verify credit lines. These risks, and the associated staking rewards, can then be shared with the public via a delegated staking mechanism.

To understand how the ReSource Network consumes and recirculates SOURCE, refer to chapter 4.4, “SOURCE Token Dynamics.”


---

# 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://resource-network.gitbook.io/resource-technical/05-protocol-and-network-governance/5.3-source-governance-token.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.