> For the complete documentation index, see [llms.txt](https://ura-labs-1.gitbook.io/ura-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ura-labs-1.gitbook.io/ura-documentation/capacity-protocol/relay-club.md).

# Relay Club

Relay Club is the provider-facing participation experience for the Capacity Protocol.

It is designed to make the authorization understandable before signing:

* NIGHT stays in the provider's wallet.
* No NIGHT transfer is required.
* The future DUST receiver is explicit.
* The provider reviews the action before wallet approval.

## Relationship to the protocol

Relay Club is not a separate token and Ura is not planning a token launch. It is the participation layer through which providers can contribute capacity and later receive transparent accounting or fee allocations.

## Current status

The Preprod interface exists, but generalized provider onboarding is wallet-blocked. Any delegator count or participation display must distinguish test data from live, signed providers.


---

# 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://ura-labs-1.gitbook.io/ura-documentation/capacity-protocol/relay-club.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.