# Configure provider key pair · Chromia Docs (concept)

> On the Chromia network, key pairs have different meanings and responsibilities.

Source: https://docs.chromia.com/ecosystem/providers/nodes/provider-keypair/

# Configure provider key pair

On this page

* [Provider key pair](#provider-key-pair)
* [Generate or migrate your provider key pair](#generate-or-migrate-your-provider-key-pair)
* [Notify Chromia of provider identity](#notify-chromia-of-provider-identity)
* [Configure PMC](#configure-pmc)

On the Chromia network, key pairs have different meanings and responsibilities. As a provider, you typically handle two
different types of key pairs:

1. A **provider key pair**, used to vote on and sign proposals. This key pair is used to identify the provider on the
   network.
2. **Node key pairs**, used to identify each node on the network. All nodes in the network have their unique key pair.

The PMC [keygen](https://docs.chromia.com/ecosystem/providers/pmc/commands/keygen/) command can create key pairs.

## Provider key pair

The provider key pair is your personal key pair. It's used to sign transactions and proposals on the network. In the
future, it'll connect to a wallet and thus be the target for your revenue stream. You must keep this key pair safe as
it's not possible to recover this. Therefore, you should configure `pmc` to use this key pair. For more information, see
PMC [keygen](https://docs.chromia.com/ecosystem/providers/pmc/commands/keygen/).

You'll only generate this key once. We recommend setting this up [globally](https://docs.chromia.com/ecosystem/providers/pmc/commands/keygen/)
for your convenience if you plan to participate on several networks.

note

Please write down the privkey/mnemonic so that you can recover it later.

### Generate or migrate your provider key pair

If you already possess a key pair, you should migrate it. Otherwise, generate a new one using the following command:

Terminal

```
mkdir -p .chromia
pmc keygen --save .chromia/config//will create a config file in working directory
```

This action creates a `.chromia/config` file containing your key pair. While PMC automatically detects this file if
placed in the working directory or root, you can specify an alternate path with `-cfg /path/to/file`.

In the next step, you'll configure the **Provider key pair**, which serves as your identity within the Chromia network.
It’s important to store this key pair securely, as it plays a critical role in network operations.

### Notify Chromia of provider identity

After generating the keypair, inform Chromia of your public key. This will initiate the process of voting to add you as
a provider in the network. To retrieve your public key, either check the `.chromia/config` file or use the following
command to display it in the terminal:

Terminal

```
pmc config --list
```

### Configure PMC

Before connecting the PMC CLI to the network, you need to configure the `api.url` and `brid` (Blockchain RID) in your
`.chromia/config` file. These should point to an existing node on the network with the management chain.

Terminal

```
pmc config --local --set brid=${ mainnetBrids.DIRECTORY_CHAIN_BRID }
```

Terminal

```
pmc config --local --set api.url=https://system.chromaway.com
```

The `.chromia/config`file should look like this when done:

Terminal

```
privkey = <Provider privkey>

pubkey = <Provider pubkey>

brid = 7E5BE539EF62E48DDA7035867E67734A70833A69D2F162C457282C319AA58AE4

api.url = https://system.chromaway.com
```

[View this page on docs.chromia.com](https://docs.chromia.com/ecosystem/providers/nodes/provider-keypair/)Content mirrored from the live docs
