> For the complete documentation index, see [llms.txt](https://docs.midasmarkets.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.midasmarkets.xyz/rewards-and-referrals/faqs.md).

# FAQs

Frequently asked questions about Midas accounts, AI actions, wallets, trading routes, rewards, referrals, and risk.

* **Accounts** — Midas uses Privy authentication and creates embedded wallets during server-side account sync.
* **Trading** — Trades are user-confirmed and route through Jupiter, Relay, or Hyperliquid depending on the action.
* **Rewards** — Rewards and referrals depend on eligible activity, live program settings, and payout rules.

## Account FAQ

Midas accounts are authenticated through Privy. Embedded wallet creation is coordinated with server-side account sync so addresses and backend signing paths stay consistent.

* Is my wallet self-custodial? Midas uses embedded wallet infrastructure; users should review available export and recovery controls in Settings.
* Can I use Midas without funding? Yes, users can browse public market surfaces, but account-specific actions require sign-in and funding.

## Trading FAQ

Ask Midas can prepare actions, but nothing executes until the user confirms. Trading routes depend on asset, chain, wallet balance, and venue support.

* Jupiter is used for supported Solana swaps.
* Relay is used for supported cross-chain and EVM routes.
* Hyperliquid is used for supported perpetual markets and protocol account actions.

## Risk FAQ

Crypto and perpetual trading involve risk. Prices can move quickly, bridges and venues can fail, and leveraged positions can be liquidated.


---

# 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://docs.midasmarkets.xyz/rewards-and-referrals/faqs.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.