> For the complete documentation index, see [llms.txt](https://orbit-pilot.gitbook.io/orbit-pilot-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://orbit-pilot.gitbook.io/orbit-pilot-docs/product/wallets-and-signing.md).

# Wallets and signing

## Options

| Wallet             | Best for                                                       |
| ------------------ | -------------------------------------------------------------- |
| **Orbit embedded** | Passkeys, email + authenticator recovery, MCP / mobile confirm |
| **Freighter**      | Browser extension users on **Testnet**                         |

## Security model

* The AI **never** holds private keys
* Every money move requires **your** signature
* Embedded wallet: device share (browser) + server share (encrypted). Day-to-day signing needs both
* Recovery: verified email OTP + authenticator (TOTP). Passkeys are for login convenience, not sole recovery

## Freighter notes

* Network must be **Testnet**
* Mainnet Freighter connections are rejected
* Recovery / "set email + authenticator" prompts apply to the **Orbit** wallet, not Freighter

## MCP / mobile

Inside ChatGPT or Claude mobile plugins, Orbit may open **Open Orbit to confirm** in the system browser so passkeys work. Same rule: you sign; the host AI does not.


---

# 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://orbit-pilot.gitbook.io/orbit-pilot-docs/product/wallets-and-signing.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.