# Migrate V1 to V2 - P12 Keystore Constellation Network has introduced a new version 2 standard for `.p12` keystore files. These updated keystores are now required to access the Hypergraph and metagraph clusters. {% hint style="danger" %} Version 1 `.p12` files are no longer supported. {% endhint %} *** ## πŸ“Œ Purpose of This Guide This guide is intended to help Node Operators **still using version 1 `.p12` files** migrate their private key to the updated **version 2 format**, ensuring compatibility with current network requirements. *** ## πŸ› οΈ Setup Requirements
OptionDescription
1Live Constellation Validator NodeUtilize an existing Constellation Network validator node with all components already installed.
2Ephemeral VPS with nodectl Build a temporary VPS, install nodectl, use its utility to migrate your p12 from version 1 to version 2.
3Load utilities necessary onlyUse an existing or build a temporary VPS and only install the utilities necessary to complete this guide.
### Option 1: Use an Existing Node With `nodectl` If you already have `nodectl` running: * Upload your version 1 `.p12` file using the restore process. * Refer to platform-specific steps: * **Restore `.p12` from macOS** * **Restore `.p12` from Windows** > ⚠️ **Caution:**\ > Do not overwrite an existing or active `.p12` file in a running Validator node environment. *** ### Option 2: Create a Temporary VPS If you don’t have an existing node: 1. Provision a new Linux VPS (Debian-based preferred). 2. Upload your version 1 `.p12` file. 3. Install `nodectl` following the official documentation. > πŸ’‘ **Note:**\ > This VPS will **not** be used to run a Validator node. Its purpose is solely to install the required tools for migration. > βœ… Minimum Requirements: > > * 30GB of disk space > * Internet connectivity > * SSH access *** ### Option 3: Manual Setup Alternatively, install the required components manually: * `java` * `haveged` * `cl-keytool.jar` * `cl-wallet.jar` > πŸ“Ž Still ensure the VPS or machine has at least 30GB of available disk space. *** ### πŸ”„ Begin the Conversion Process Once setup is complete, proceed with the following steps. *** #### Step 1: Upload Your `.p12` File Place your original version 1 `.p12` file (from macOS or Windows) into the working directory of your VPS. Example path: ``` /home/nodeadmin/tessellation/ ``` *** #### Step 2: Set Environment Variables Export the following environment variables using your `.p12` file details. Be preciseβ€”use double quotes and match spacing exactly. ```bash export CL_KEYALIAS="myConstellationAlias" export CL_KEYSTORE="/home/nodeadmin/tessellation/myconstellation.p12" export CL_PASSWORD="my_password" export CL_STOREPASS="my_storepass_passphrase" export CL_KEYPASS="my_keystore_passphrase" ``` Confirm the exports: ```bash env | grep CL_ ``` Expected output: ``` CL_KEYALIAS=myConstellationAlias CL_KEYSTORE=/home/nodeadmin/tessellation/myconstellation.p12 CL_PASSWORD=my_password CL_STOREPASS=my_storepass_passphrase CL_KEYPASS=my_keystore_passphrase ``` *** #### Step 3: Run the Migration Command Run the following command to migrate the `.p12` file to version 2 format: ```bash java -jar /var/tessellation/cl-keytool.jar migrate ``` > βœ… If successful, no output will appear. If there's an issue, an error will be printed. *** #### Step 4: Verify the New File List the directory to verify that a new version 2 `.p12` file has been created: ```bash ls -l ``` Expected output (example): ``` -rw-r--r-- 1 nodeadmin nodeadmin 1094 May 26 12:17 myconstellation_v2.p12 ``` *** #### Step 5: Test the New `.p12` File Update your `CL_KEYSTORE` variable to point to the new file: ```bash export CL_KEYSTORE="/home/nodeadmin/tessellation/myconstellation_v2.p12" ``` Now display the public key to confirm the file is valid: ```bash java -jar /var/tessellation/cl-wallet.jar show-public-key ``` Example output: ``` EC Public Key [ee:ff:aa:bb:cc:dd:ee:ff:11:22:33:44:55:66:77:88:99:aa:bb:cc] X: abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890 Y: 111222333444555666777888999101010111111121212131313141414151515a ``` *** ### βœ… Completion Your `.p12` file is now migrated from **version 1 to version 2**. > πŸ”’ **Important:**\ > Store the original version 1 file in a secure, offline (air-gapped) location temporarily. *** #### πŸ§ͺ Final Testing To fully validate your new `.p12` file: * Connect to the appropriate Constellation cluster (Layer0 or Layer1). * Export and verify the private key. * Use the new file in your validator setup or wallet integration. *** #### πŸ” Optional: Rename the New File If you want to use the original filename, rename your new file: ```bash mv /home/nodeadmin/tessellation/myconstellation_v2.p12 /home/nodeadmin/tessellation/myconstellation.p12 ``` *** #### βš™οΈ `nodectl` Configuration (If Applicable) If you're using `nodectl` and kept the `_v2` filename, make sure to update the configuration: ```bash sudo nodectl configure ``` > This ensures `nodectl` references the correct `.p12` file for all future operations. *** You have now successfully migrated and verified your `.p12` keystore to the latest version, ensuring your validator remains compatible with Constellation Network's current infrastructure. --- # Agent Instructions: 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: ``` GET https://docs.constellationnetwork.io/run-a-node/legacy/migrate-v1-to-v2-p12-keystore.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.