> For the complete documentation index, see [llms.txt](https://docs.trover.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trover.tech/safety-and-controls/wallet-security.md).

# wallet security

## wallet security

trover routes authentication and supported wallet actions through privy. this limits direct credential handling, but no wallet or onchain system is risk-free.

### keep control of your wallet

* never share your seed phrase or private key
* confirm the active wallet address before every action
* read wallet prompts instead of signing automatically
* keep only the funds needed for the action in a delegated wallet
* review connected apps, approvals, and delegated permissions regularly
* disable x commands or delegation when you aren’t using them
* use a separate wallet for testing new routes or contracts

### manual and delegated wallets

an external wallet normally requires a user signature. an embedded user-owned wallet can be manual or delegated, depending on its capability and your account settings.

delegated execution is convenient, but it gives enabled automation more authority. keep limits narrow and disconnect or disable the capability when it’s no longer needed.

### suspicious messages

trover support will never need recovery material. don’t trust an x reply, dm, search ad, or lookalike domain that asks you to import a wallet, reveal a code, or “verify” by sending funds.


---

# 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.trover.tech/safety-and-controls/wallet-security.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.
