> 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/app-guide/vault-management/vault-upgrade.md).

# Upgrade a Vultisig vault to DKLS23

Upgrade a GG20 Vultisig vault to DKLS23. Faster signing. Same addresses. Export new backups after.

{% hint style="info" %}
Upgrades are only available for vaults created with the GG20 protocol.
{% endhint %}

***

## What is Upgrading?

Upgrade moves the vault from GG20 to DKLS23.

* Faster signing
* Required for the [Vultisig Extension](/ecosystem/vultisig-extension.md)
* Same addresses. You do not move funds.

Protocol pages: [Security and TSS](/security-and-technology/overview.md).

***

## How to Upgrade

The upgrade can be initiated from:

* The banner on the home screen
* **Settings** → **Vault Settings** → **Upgrade**

<div><figure><img src="https://644481292-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfSRUQVZENEfvoqS6R0GO%2Fuploads%2Fgit-blob-b9fb64cd70428fc34e25465d64c27f84706d29fb%2Fimage%20(2).png?alt=media" alt=""><figcaption><p>Settings option</p></figcaption></figure> <figure><img src="https://644481292-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfSRUQVZENEfvoqS6R0GO%2Fuploads%2Fgit-blob-8a0f14b7dae4c7d12076e6002ac6217fab6bca4b%2FUpgrade.png?alt=media" alt=""><figcaption><p>Home banner</p></figcaption></figure></div>

### Requirements

* All original devices from vault creation must be present
* This is a full keygen ceremony (similar to creating a new vault)

### Steps

1. Start the upgrade on one device
2. Join with every original device
3. Wait until keygen finishes on all of them
4. **Export a new backup from every device**

***

## Backup After Upgrade

{% hint style="warning" %}
New vault shares are created during upgrade. Store them with the same security precautions as original shares.
{% endhint %}

### Distinguishing Backups

| Protocol | File naming                 |
| -------- | --------------------------- |
| GG20     | `vault-xxxx-part1of2.vult`  |
| DKLS23   | `vault-xxxx-share1of2.vult` |

***

## Upgrading Active Vaults

{% hint style="info" %}
Active Vaults are a discontinued feature with a different upgrade procedure.
{% endhint %}

To upgrade an Active Vault:

1. Import the server share onto a third device
2. Initiate upgrade from other devices
3. Join with all three devices
4. Complete upgrade

The result is a standard [Secure Vault](/app-guide/creating-a-vault/secure-vault.md) without Vultiserver involvement.

{% hint style="info" %}
If Fast signing is still desired, create a new [Fast Vault](/app-guide/creating-a-vault/fast-vault.md) after upgrading.
{% endhint %}

***

## Related

* [TSS Protocols](/security-and-technology/overview.md) - Technical details
* [Vultisig Extension](/ecosystem/vultisig-extension.md) - Requires DKLS23


---

# 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 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/app-guide/vault-management/vault-upgrade.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 `automate deployments from our CI pipeline` 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.
