> For the complete documentation index, see [llms.txt](https://xircus-developer.gitbook.io/developer-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://xircus-developer.gitbook.io/developer-hub/getting-started/wallet-and-authentication.md).

# Wallet & Authentication

### Authentication

Xircus uses a signature base wallet authentication where users need to sign a message with their wallet provider, a server provided nonce is attached to the message for entropy. The signature message is sent back to the server to recover the signer and validate the wallet address and issue a JWT (JSON Web Token) token on success. New nonce is issued on every authentication request to make each signature message unique.

###

### Wallet Providers

Based on the wallet provider used,

###

### Registry Authentication

This Authentication API doesn't require to pass an App ID

### Provider Authentication

This Authentication API requires an App ID


---

# 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://xircus-developer.gitbook.io/developer-hub/getting-started/wallet-and-authentication.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.