> For the complete documentation index, see [llms.txt](https://docs.hyphen.at/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyphen.at/concepts/hyphen-multi-sig-account.md).

# Hyphen Multi-Sig Account

All user accounts in Hyphen are multi-sig. Normally, multi-sig means that keys are shared among multiple parties, but Hyphen's Multi-Sig only involves multiple devices owned by the same user.

This is referred to as the **User Key**. It operates similarly to the Login Session in Web2 services, so users can manage their logged-in devices and add/remove them as desired. In situations where multiple device keys are needed, using **2FA** is a characteristic of Hyphen.

However, doing this every time can be inconvenient in terms of UX and decrease recoverability (risk of losing control of the account due to device loss). To solve this problem, we set a Server Key and a Recovery Key respectively. The Server Key is stored on Hyphen's server, while the Recovery Key is stored in a user-owned space (e.g., cloud, personal wallet).

Thanks to this well-balanced multisig structure, Hyphen can be a **Non-Custodial Wallet while not sacrificing UX and Security**.


---

# 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.hyphen.at/concepts/hyphen-multi-sig-account.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.