> For the complete documentation index, see [llms.txt](https://docs.native.org/native-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.native.org/native-whitepaper/introduction/self-custody/hardware-wallet.md).

# Hardware Wallet

Hardware wallets keep a crypto user’s private keys offline, meaning they are not connected to the internet, except when a user must briefly connect them to a computer to complete a transaction.

Hardware wallets are offline, so they are considered one of the safest ways to safeguard private keys. However, a hardware wallet doesn’t replace the usual crypto safety practices. If a user is careless with their keys or seed phrase, it won’t matter what kind of wallet they use.

Users can use a hardware wallet as the Treasury of the pool created with Native. No private keys are shared with Native. The only connection between the hardware wallet and the Native pool contracts is the allowance given by the user.

## Common hardware wallets

1. Trezor 
2. Ledger 
3. Safepal

{% hint style="info" %}
Use a different hardware wallet from your main wallet where you store all your assets for the Treasury of your Native pool for better security 
{% endhint %}


---

# 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.native.org/native-whitepaper/introduction/self-custody/hardware-wallet.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.