> For the complete documentation index, see [llms.txt](https://docs.nomic.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nomic.io/network/key-management.md).

# Key Management

If your node is in the validator set or signatory set, you have an important responsibility to keep signing so that the network can remain live. Also, if these keys are stolen the security of the bridge is at risk.

## List of Keys

* **Consensus key (validators)**
  * `~/.nomic-stakenet-3/tendermint/config/prev_validator_key.json`
  * Used to sign blocks on the Nomic blockchain.
* **Signatory key (signatories)**
  * `~/.nomic-stakenet-3/signer/xpriv`
  * Used to sign Bitcoin transactions for the bridge.
* **Wallet key (all nodes)**
  * `~/.orga-wallet/privkey`
  * Used to sign transactions created through the Nomic CLI (declaring a validator, transferring tokens, etc.)

*On testnet, the path will instead start with `~/.nomic-testnet-4d`*

## Backing Up

It is important to make backups of these keys, since losing them can be hard to recover from.

When backing up, ensure your keys are copied somewhere other than where you run your nodes - preferably on an offline machine, encrypted with a passphrase, or stored on other medium not vulnerable to malware such as paper.

## Migrating Validator Nodes

Sometimes it is necessary to move your keys to a different machine to start operating your node there. When you do this, make sure to transfer all the keys as listed above into their respective paths.

Additionally, make sure to transfer `~/.nomic-stakenet-3/tendermint/data/priv_validator_state.json`. This file ensures your node will not accidentally cause a double-sign, which is a slashable offense that will jail your validator.


---

# 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.nomic.io/network/key-management.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.