Constellation Network
IntroductionFundamentalsFor DevelopersNode Validators
  • Index
  • Introduction
  • Elements
    • Toolkit
    • Development Environment
    • Hydra CLI
    • Developer Dashboard
    • Telemetry Dashboard
    • Metagraph Monitoring Service
  • Metagraph Framework
    • Overview
    • Framework Architecture
    • Installation
    • Currency
      • Working with Tokens
    • Data
      • State Management
      • Lifecycle functions
    • Framework Endpoints
    • Custom Endpoints
  • Guides
    • Quick Start
    • Send a Transaction
    • Manual Setup
    • Customize Rewards Logic
    • Custom Data Validation
    • Working with p12 files
    • Snapshot Fees
    • Deploy a Metagraph
      • Security groups
      • Key pairs
      • Base instance
        • Generating base instance
        • Connect to the instance
        • Generating AMI (Image) from Base Instance
        • Launching instances from AMI
      • Start Metagraph Instances
        • Configuring P12 Files
        • Start Global L0 Instances
        • Start Metagraph L0 Instances
        • Start Currency L1 Instances
        • Start Data L1 Instances
  • Resources
    • Network APIs
    • Example Codebases
    • Metagraph Development Video Series
Powered by GitBook

Main

  • Website
  • Get DAG
  • Explore Projects
  • Partners

Socials

  • Telegram
  • Discord
  • X (Twitter)

Tools

  • Wallet
  • DAG Explorer
  • Coingecko

© 2025 CONSTELLATION NETWORK

On this page
  • Generating p12 files​
  • Finding Your Node IDs​

Was this helpful?

Export as PDF
  1. Guides

Working with p12 files

PreviousCustom Data ValidationNextSnapshot Fees

Last updated 1 month ago

Was this helpful?

Generating p12 files

This guide will walk you through the process of creating your own custom p12 files. We will generate three files to match the original Euclid Development Environment project's configuration.

Caution

If using a Euclid Development Environment project, you must update your configuration to use your own custom p12 files. Projects submitted with the default p12 files that come with the project will be rejected.

Step 1: Download cl-keytool.jar Executable

Download the cl-keytool.jar executable. This is included as an asset with each release of Tessellation.

Step 2: Set Up Your Environment Variables

Modify the following variables with your custom details and export them to your environment:

export CL_KEYSTORE=":your_custom_file_name.p12"
export CL_KEYALIAS=":your_custom_file_alias"
export CL_PASSWORD=":your_custom_file_password"

Replace :your_custom_file_name.p12, :your_custom_file_alias, and :your_custom_file_password with your specific file name, alias, and password, respectively.

Step 3: Generate Your Custom .p12 File

Execute the following command to generate your custom .p12 file:

java -jar cl-keytool.jar generate

This will create a .p12 file in the directory from which the command was executed.

Repeat steps 2 and 3 two more times to create a total of three custom p12 files. Remember to change the file name each time to avoid overwriting any existing files.

Your node ID is the public key of your wallet which will be stored as a p12 file.

Caution

If using a Euclid Development Environment project, you must update your configuration to use your own custom p12 files. Projects submitted with the default p12 files that come with the project will be rejected.

Editing the details of the following variables and export to your environment.

export CL_KEYSTORE=":your_file_name.p12"
export CL_KEYALIAS=":your_file_alias"
export CL_PASSWORD=":your_file_password"

Then you can run the following to get your node ID:

java -jar cl-wallet.jar show-id

Step 4: Repeat the Process

Finding Your Node IDs

Download the cl-wallet.jar executable. This is distributed as an asset with each .

​
​
​
​
​
​
How to generate p12 files
release of Tessellation