Setup Chromia Account
Install Chromia CLI
You can install Chromia CLI using a package manager or by downloading it directly from Chromia CLI Packages.
To install Chromia CLI (chr) on macOS, follow these steps:
If Homebrew is not installed, install it by running:
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"Add the Chromia repository to Homebrew by running the following command:
brew tap chromia/core https://gitlab.com/chromaway/core-tools/homebrew-chromia.gitInstall Chromia CLI with:
brew install chromia/core/chrTo verify the installation, check the version by running:
chr --version
To install Chromia CLI (chr) on Linux or WSL (Windows Subsystem for Linux), follow these steps:
Download and add Chromia's
apt-repopublic key to your system’s trusted keyrings:curl -fsSL https://apt.chromia.com/chromia.gpg | sudo tee /usr/share/keyrings/chromia.gpgAdd the Chromia repository to your list of package sources:
echo "deb [arch=amd64 signed-by=/usr/share/keyrings/chromia.gpg] https://apt.chromia.com stable main" | sudo tee /etc/apt/sources.list.d/chromia.listRun the following command to update your package sources:
sudo apt-get updateinfo
If you added
apt.chromia.combefore Chromia CLI version0.16.0, run the following command to allow the repository update:sudo apt-get --allow-releaseinfo-change updateOnce the repository is updated, install Chromia CLI by running:
sudo apt-get install chrTo verify that Chromia CLI is installed successfully, check the version:
chr --version
To install Chromia CLI (chr) on Windows using Scoop, follow these steps:
If Scoop is not installed, install it by running the following command in PowerShell (run as Administrator):
Add the Chromia repository (bucket) to Scoop by running:
Add the Java bucket to Scoop by running:
This will enable scoop to download the openjdk21 which chromia-cli depends on when installing
Install Chromia CLI by running:
To verify that Chromia CLI is installed successfully, check the version:
Create Private Keys
chr keygen -f eval_engine_keyYou can find the generated private key in the eval_engine_key file. Save this private key in your environment variables.
The file will contain content similar to this:
Important: Do not commit the
eval_engine_keyfile to git version control
Last updated