> 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-legacy/add-public-key-for-a-network.md).

# Add Public Key for a Network

In Polkadot Vault after you add the chain specs and metadata for a network, you then need to add your Public Key for that network so that you can conduct transactions:

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

1. Ensure that you have added the desired network chain specs and metadata as described above.
2. `Select` the **Key Sets** tab.
3. `Select` the plus **+** icon at the top right of the screen.
4. `Select` the **Network** field and then `Select` your desired **network** in the list.
5. `Input` your desired account derivation path and then `Select` **Done**.
6. `Select` **Create Derived Key**.
7. Review the message about writing down your Derivation Path and 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 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-legacy/add-public-key-for-a-network.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.