Starting the server with various configuration options can be done using a configuration file instead of using just flags. The command used to start the server with a config file: polygon-edge server --config <config_file_name>

Export config file with default configuration

The configuration with default settings for the ZChains server can be exported into a config file in either yaml or json file format. This file can be used as a template for running the server using a configuration file.

YAML

To generate the config file in yaml format:

or just

the config file named default-config.yaml will be created in the same directory that this command has been run from.

File example:

JSON

To generate the config file in json format:

the config file named default-config.json will be created in the same directory that this command has been run from.

File example:

Checkout section to get information on how to use these parameters.

Typescript schema

The following is the sample format for the configuration file. It's written in TypeScript to express the properties types (string, number, boolean), from it you could derive your configuration. It's worth mentioning that the PartialDeep type from type-fest is used to express that all properties are optional.

Overview

Currently, the ZChains is concerned with keeping 2 major runtime secrets:

• The validator private key used by the node, if the node is a validator

• The networking private key used by libp2p, for participating and communicating with other peers

For additional information, please read through the

The modules of the ZChains should not need to know how to keep secrets. Ultimately, a module should not care if a secret is stored on a far-away server or locally on the node's disk.

Everything a module needs to know about secret-keeping is knowing to use the secret, knowing which secrets to get or save. The finer implementation details of these operations are delegated away to the SecretsManager, which of course is an abstraction.

The node operator that's starting the ZChains can now specify which secrets manager they want to use, and as soon as the correct secrets manager is instantiated, the modules deal with the secrets through the mentioned interface - without caring if the secrets are stored on a disk or on a server.

This article details the necessary steps to get the ZChains up and running with a server.

:::info previous guides It is highly recommended that before going through this article, articles on and are read. :::

Prerequisites

This article assumes that a functioning instance of the Hashicorp Vault server is already set up.

Additionally, it is required that the Hashicorp Vault server being used for the ZChains should have enabled KV storage.

Required information before continuing:

• The server URL (the API URL of the Hashicorp Vault server)

• Token (access token used for access to the KV storage engine)

Step 1 - Generate the secrets manager configuration

In order for the ZChains to be able to seamlessly communicate with the Vault server, it needs to parse an already generated config file, which contains all the necessary information for secret storage on Vault.

To generate the configuration, run the following command:

Parameters present:

• PATH is the path to which the configuration file should be exported to. Default ./secretsManagerConfig.json

• TOKEN is the access token previously mentioned in the

• SERVER_URL

:::caution Node names Be careful when specifying node names.

The ZChains uses the specified node name to keep track of the secrets it generates and uses on the Vault instance. Specifying an existing node name can have consequences of data being overwritten on the Vault server.

Secrets are stored on the following base path: secrets/node_name :::

Step 2 - Initialize secret keys using the configuration

Now that the configuration file is present, we can initialize the required secret keys with the configuration file set up in step 1, using the --config:

The PATH param is the location of the previously generated secrets manager param from step 1.

Step 3 - Generate the genesis file

The genesis file should be generated in a similar manner to the and guides, with minor changes.

Since Hashicorp Vault is being used instead of the local file system, validator addresses should be added through the --ibft-validator flag:

Step 4 - Start the Polygon Edge client

Now that the keys are set up, and the genesis file is generated, the final step to this process would be starting the Polygon Edge with the server command.

The server command is used in the same manner as in the previously mentioned guides, with a minor addition - the --secrets-config flag:

The PATH param is the location of the previously generated secrets manager param from step 1.

Overview

Currently, the ZChains is concerned with keeping 2 major runtime secrets:

• The validator private key used by the node, if the node is a validator

Overview

The ZChains has two types of private keys that it directly manages:

• Private key used for the consensus mechanism

Overview

Currently, the ZChains is concerned with keeping 2 major runtime secrets:

• The validator private key used by the node, if the node is a validator

• The networking private key used by libp2p, for participating and communicating with other peers

For additional information, please read through the

The modules of the ZChains should not need to know how to keep secrets. Ultimately, a module should not care if a secret is stored on a far-away server or locally on the node's disk.

Everything a module needs to know about secret-keeping is knowing to use the secret, knowing which secrets to get or save. The finer implementation details of these operations are delegated away to the SecretsManager, which of course is an abstraction.

The node operator that's starting the ZChains can now specify which secrets manager they want to use, and as soon as the correct secrets manager is instantiated, the modules deal with the secrets through the mentioned interface - without caring if the secrets are stored on a disk or on a server.

This article details the necessary steps to get the ZChains up and running with .

:::info previous guides It is highly recommended that before going through this article, articles on and are read. :::

Prerequisites

GCP Billing Account

In order to utilize GCP Secrets Manager, the user has to have enabled on the GCP portal. New Google accounts on GCP platform are provided with some funds to get started, as a king of free trial. More info

Secrets Manager API

The user will need to enable the GCP Secrets Manager API, before he can use it. This can be done via . More info:

GCP Credentials

Finally, the user needs to generate new credentials that will be used for authentication. This can be done by following the instructions posted . The generated json file containing credentials, should be transferred to each node that needs to utilize GCP Secrets Manager.

Required information before continuing:

• Project ID (the project id defined on GCP platform)

• Credentials File Location (the path to the json file containing the credentials)

Step 1 - Generate the secrets manager configuration

In order for the ZChains to be able to seamlessly communicate with the GCP SM, it needs to parse an already generated config file, which contains all the necessary information for secret storage on GCP SM.

To generate the configuration, run the following command:

Parameters present:

• PATH is the path to which the configuration file should be exported to. Default ./secretsManagerConfig.json

• NODE_NAME is the name of the current node for which the GCP SM configuration is being set up as. It can be an arbitrary value. Default polygon-edge-node

:::caution Node names Be careful when specifying node names.

The ZChains uses the specified node name to keep track of the secrets it generates and uses on the GCP SM. Specifying an existing node name can have consequences of failing to write secret to GCP SM.

Secrets are stored on the following base path: projects/PROJECT_ID/NODE_NAME :::

Step 2 - Initialize secret keys using the configuration

Now that the configuration file is present, we can initialize the required secret keys with the configuration file set up in step 1, using the --config:

The PATH param is the location of the previously generated secrets manager param from step 1.

Step 3 - Generate the genesis file

The genesis file should be generated in a similar manner to the and guides, with minor changes.

Since GCP SM is being used instead of the local file system, validator addresses should be added through the --ibft-validator flag:

Step 4 - Start the Polygon Edge client

Now that the keys are set up, and the genesis file is generated, the final step to this process would be starting the Polygon Edge with the server command.

The server command is used in the same manner as in the previously mentioned guides, with a minor addition - the --secrets-config flag:

The PATH param is the location of the previously generated secrets manager param from step 1.