> For the complete documentation index, see [llms.txt](https://docs.vultisig.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vultisig.com/infrastructure/what-is-vultisigner/how-does-vultisigner-work.md).

# How a Vultisig Fast Vault works

How a Vultisig Fast Vault is created and signed. 2-of-2 keygen with Vultiserver, where the server share is stored, and what to do if the server is offline.

## Set Up

### 2-of-2 Fast Vault

In this setup, the Vault is created together with a user's device and the Vultisigner server.\
The user registers a keygen request with the Vultisigner server, which creates a new Vault that records the connection to the user's device. A keygen ceremony is then executed, which creates the Vault shares on the user's device and on the Vultisigner server. \\

## Vault Share storage

The Vultiserver vault share is stored on a dedicated server and encrypted with the Fast Vault password. During setup, a backup of that share is emailed to you. Configurable transaction policies are [not in the apps yet](/infrastructure/what-is-vultisigner/what-can-be-configured.md).\\

For security reasons, the Vultisigner's Vault share is password encrypted and the user must provide an email address to which the Vault share will be sent during setup, for backup and independent access.

<figure><img src="https://644481292-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfSRUQVZENEfvoqS6R0GO%2Fuploads%2Fgit-blob-f193a1dc24c9116feebbbb5ffc245dbdc0cd5a35%2FVultisigner%20storage%202-2.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

## Transaction Signing

When you approve a transaction on your device, the request is sent to Vultiserver. The server joins the keysign with its share. You still have to approve on the device. Configurable policies are not applied today.

<figure><img src="https://644481292-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfSRUQVZENEfvoqS6R0GO%2Fuploads%2Fgit-blob-a086583bdee2dc072fad82cb0ce384149d2ebf6c%2Fdefault%20vultisigner.png?alt=media" alt=""><figcaption><p>Vultisigner Flowchart</p></figcaption></figure>

{% hint style="info" %}
In case the Vultisigner server is offline and unable to sign, the user needs to import the Vultisigner share received via email into another device and sign like a normal Keysign.
{% 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.vultisig.com/infrastructure/what-is-vultisigner/how-does-vultisigner-work.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.