> For the complete documentation index, see [llms.txt](https://docs.citadelwallet.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.citadelwallet.io/wallet-spec/mechanical-spec/buttons.md).

# Buttons

Citadel Wallet integrates two physical push buttons to control power and approve transaction functions. More information on each button can be found below:

## Power Button:

The Power Button is responsible for turning the Citadel Wallet hardware on and off. When the device is completely off, the internal rechargeable battery is completely isolated from the electronics to prevent draining. To use the device, the user must press and hold the Power button for at least 2 seconds. Once the LCD backlight turns on, the button can be released and the device will boot up.

## Approve Button:

To approve a transaction using the Citadel Wallet, a user must first read the transaction information displayed on the wallet's screen. The approval process can then be initiated by pressing and holding the Approve Button for a few seconds. This button is responsible for approving transactions that are submitted to the wallet by a software wallet or dApp connected via USB, BLE, or NFC interfaces. By following these steps, users can easily and securely process transactions through the Citadel Wallet.


---

# 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.citadelwallet.io/wallet-spec/mechanical-spec/buttons.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.