> For the complete documentation index, see [llms.txt](https://docs.adena.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adena.app/user-guide/sign-in/connect-hardware-wallet.md).

# Connect Hardware Wallet

## What is a hardware wallet?

A hardware wallet is a device that generates and stores your private keys in an offline environment. Hardware wallets mitigate attack vectors by protecting your keys from hackers attempting to steal your funds by remotely penetrating your vulnerable, internet-connected devices. It is essentially a physical vault that stores your private key.

Once you create an account on your hardware wallet, it is extremely important to NOT directly enter its private key into software wallets such as web extension wallets, smartphone wallets, or desktop wallets, to ensure that it never leaves your hardware wallet.

## How do I sign a transaction with a hardware wallet?

While hardware wallets have the ability to sign transactions using the stored private keys, they cannot directly send transactions to the blockchain due to their offline setup. This means you need a separate PC that is connected to the internet with an app like Adena installed to broadcast the signed transactions. To exchange the data for signed transaction files with the PC, hardware wallets use USB cables or Bluetooth to avoid direct internet connections.

Refer to [this section](broken://pages/kzEWehAJ2IRfsxQDnsSN) on how to send transactions with Ledger accounts on Adena.

## Which hardware wallets are supported by Adena?

Adena currently only supports [Ledger](https://www.ledger.com/), with plans to integrate with [Keystone](https://keyst.one/) soon. We will add support for other hardware wallets that are compatible with Cosmos to offer a wide range of selections for users.


---

# 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.adena.app/user-guide/sign-in/connect-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.