> For the complete documentation index, see [llms.txt](https://docs.novawallet.io/nova-wallet-wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novawallet.io/nova-wallet-wiki/wallet-management/hardware-wallets/polkadot-vault/derivation-paths/add-root-key.md).

# Add Root Key

## Root Key

The Root Key is the account generated from your seed phrase without any derivation path associated with it. By default, Polkadot Vault will assign a hard derivation path for each network that corresponds with the name of the chain. 

{% hint style="warning" %}
The following steps should be carried out on your Polkadot Vault device.
{% endhint %}

To add the Root Key:

1. `Create` or `Import` an account (**keyset**) into Polkadot Vault.
2. On your Polkadot Vault device, `select` the **+ icon** at the top right of the screen.
3. `Select` the **network** that you would like to add the root key for (note: if you cannot see your desired network then you have not correctly added the [chain specs](/nova-wallet-wiki/wallet-management/hardware-wallets/polkadot-vault/update-chain-specs-in-polkadot-vault.md) and [metadata](/nova-wallet-wiki/wallet-management/hardware-wallets/polkadot-vault/update-chain-metadata-in-polkadot-vault.md))
4. `Select` **Add Custom Derivation Path**.
5. In the Derivation Path Name field, you must `delete` **all the text**. The field will now display "Empty path = creating root"
6. `Select` **Done**.
7. You may now `input` a **name** for this derivation path, such as "root".
8. `Tick` the "**I have written down my derivation path name**" tick box and `select` **Done**.
9. Your Root Key has now been added to Polkadot Vault. If you select this key from the Derived Keys list, you will see that under the Derivation Path field, it states "Derivation Path is Empty" This indicates that this is indeed the root key.


---

# 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.novawallet.io/nova-wallet-wiki/wallet-management/hardware-wallets/polkadot-vault/derivation-paths/add-root-key.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.