.svg?alt=media&token=7e5932d9-8938-4b22-9f68-ef98b4283b65)
Overview
Learn more about Enjin nodes and its possibilities.
Running an Enjin node allows you to connect to the Enjin network, expose the RPC endpoint, and author Matrixchain 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:
Component | Requirement |
|---|---|
OS | Ubuntu 20.04 or newer |
CPU | 4 cores |
RAM | 16 GB |
Disk Space | 256 GB SSD |
This table shows the default ports that are used by the Enjin Matrixchain node and embedded Relaychain node:
Description | Ingress Port | Egress Port |
|---|---|---|
WS (Relaychain Only) | TCP 9944 | - |
RPC (HTTP & WS) | TCP 9933 | - |
P2P | TCP 30333 - 30334 | TCP 443 TCP 30333 - 30334 |
Prometheus | TCP 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.
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 https://github.com/paritytech/substrate subkey
subkey generate-node-key --file ./node.key # or any other path
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
Last modified 22d ago