Working with p12 files
Last updated
Was this helpful?
Last updated
Was this helpful?
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.
cl-keytool.jar
ExecutableDownload the cl-keytool.jar
executable. This is included as an asset with each release of Tessellation.
Modify the following variables with your custom details and export them to your environment:
Replace :your_custom_file_name.p12
, :your_custom_file_alias
, and :your_custom_file_password
with your specific file name, alias, and password, respectively.
Execute the following command to generate your custom .p12 file:
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.
Then you can run the following to get your node ID:
Download the cl-wallet.jar
executable. This is distributed as an asset with each .