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