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

# Derivation Paths – Add Root Key

Polkadot Vault allows you to manage Derived Accounts. This allows you to manage several accounts on a network using the same seed. You can think of derived accounts as child accounts of the root account created using the original mnemonic seed phrase. There are different types of account derivation – hard or soft derivation.

When you add a network to an account on your Polkadot Vault device, you must provide your desired derivation path. 

## / Soft Derivation

 A soft derivation allows someone to potentially "go backwards" to figure out the initial account's private key if they know the derived account's private key. It is also possible to determine that different accounts that are generated from a seed are linked to that seed.

## // Hard Derivation

A hard derivation path does not allow either of those things – even if you know a derived private key, it is not feasible to figure out the private key of the root address, and it is impossible to prove that the first account is linked with the second.

## /// Password Derivation

In this type of derivation, if the mnemonic phrase would leak, accounts cannot be derived without the initial password. In fact, for soft- and hard-derived accounts, if someone knows the mnemonic phrase and the derivation path, they will have access to your account. For password-derived accounts, the password is applied on the derivation path. You can know the mnemonic phrase and the derivation path, but without the password, it is not possible to access the account. In mathematical terms, if we have a written derivation path and a password, we can calculate the real derivation path as f(written derivation path, password); where f is a function. We can then calculate the account key pair using f(seed, real derivation path). Note that 

{% hint style="info" %}
Unlike hard and soft derivations that can be mixed, only a single password should be specified per derivation.
{% endhint %}

## Root Key

The Root Key is basically the account generated by your seed without any derivation path associated with it. To add the Root Key you should:

{% hint style="warning" %}
The following steps need to be carried out on your **Polkadot Vault Device**.
{% endhint %}

1. Create or import an account into Polkadot Vault as detailed above.
2. Select the **Key Sets** tab.
3. Select your desired **account**.
4. Select the plus **+** icon at the top right of the screen.
5. Select the **Network** field and then Select your desired **network** in the list.
6. In the **Derivation Path** field delete all data, including any / and then Select **Done**.
7. Select **Create Derived Key**.
8. Review the message about writing down your Derivation Path then Select the **I have written down my derivation path name** field and then Select **Done** and complete the PIN / Biometry confirmation if prompted.


---

# 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.novaspektr.io/wallet-management/polkadot-vault-wallet-legacy/derivation-paths-add-root-key.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.