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

# Delegators

#### Becoming a Delegator

* Choose a Validator — Review available validators by performance, uptime, and reputation.
* Delegate $NB — Stake tokens to your chosen validator through the Nubila portal.
* Confirm Participation — Once delegated, your stake is active and you begin earning rewards.

#### Responsibilities

* Select validators wisely based on track record and community reputation.
* Monitor your delegated stake and re-delegate if necessary.
* Participate in governance with your $NUBI tokens when proposals arise.

#### Rewards

* Earn a share of validator rewards, proportional to the size of your delegated stake.
* Rewards are distributed automatically, minus validator commission.
* Unbonding periods apply before funds can be withdrawn.

#### Monitoring & Performance

* Use the Nubila portal to track your delegated stake, rewards history, and validator performance.
* Review validator metrics such as uptime, consensus participation, and honesty score.


---

# 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://nubila.gitbook.io/nubila/nubila-network/delegators.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.