Hosting an Enjin Node

Running an Enjin node allows you to connect to the Enjin network, expose the RPC endpoint, and author blocks. This guide walks you through the process of running your own node locally and on a remote server.


In general, requirements for running an Enjin node are quite similar to running a Substrate node.

Therefore, if you are not sure about specific details, you can always refer to the official Substrate documentation. However, building a Matrixchain Node, i.e. Enjin Matrixchain node, requires a little more time and resources, since Matrixchain nodes also run a full Relaychain node.


For building and running an Enjin node, the recommended hardware is:

OSUbuntu 20.04 or newer
CPU4 cores
Disk Space256 GB SSD


It is recommended to have more disk space available (512 GB+) if you are running an Archive Node.


This table shows the default ports that are used by the Enjin Matrixchain node and embedded Relaychain node:

DescriptionIngress PortEgress Port
WS (Relaychain Only)TCP 9944-
RPC (HTTP & WS)TCP 9933 -
P2PTCP 30333 - 30334TCP 443
TCP 30333 -30334
PrometheusTCP 9615-

This table shows the ports that are recommended to be exposed depending on the type of node you are running:



This section covers advanced topics associated with running the Enjin node.

Node Key

Substrate nodes use node keys for identification in peer-to-peer communication. To generate a node key, use the subkey tool, which can be downloaded using the following command:

cargo install --force --git subkey

After installing the subkey tool, you can generate the node key using the following command:

subkey generate-node-key --file ./node.key # or any other path

Purging the chain

To begin anew, without any chain history, you may want to purge the chain.


The following will command will purge the chain data for the Enjin Matrixchain

./target/release/matrixchain purge-chain --chain mainnet