Abstract Node | Manual
1. First of all, purchase a server from AEZA.
We’ve started using the AEZA service more due to its high reliability and speed.
- A relatively modern CPU is recommended.
- RAM: 32GB
- Storage:
- Network: 100 Mbps connection (1 Gbps+ recommended)
2. Occupied Ports and API Access
When deploying a node, it’s essential to understand which ports are already in use to avoid conflicts.
The Abstract node uses the following ports:
You can access the APIs using the following:
Before installing the node, make sure these ports are not in use.
What are ports and what role do they play in nodes? - Read more
2. Set up the server on your PC.
Log in using the command root@ip
.
But before that, we recommend securing your server. Read more in our article.
3. Install the script.
1. Run the following command and download:
sudo bash -c 'git clone https://github.com/dknodes/Abstract.git && cd Abstract && chmod ugo+x AbstractDK.sh && ./AbstractDK.sh'
2. 🛠️ Start Mainnet Node
3. 🛠️ Start Testnet Node
4. 📄 View Container Logs
5. ⏹️ Stop Mainnet Node
6. ⏹️ Stop Testnet Node
7. 🚪 Exit
- If Docker is not installed, execute command 1.
- If Docker is already installed, go straight to step 2.
4. Install Mainnet and Testnet Node
Choose either Testnet or Mainnet — you won’t be able to run both nodes at the same time, so pick one. For this example, we’re selecting Testnet.
Important: Before installing the node, check your server specs. This node is highly demanding, and after installation, and Testnet node can get pretty heavy after installation.
For example, on an Aeza server with:
The load looks something like this.
5. Check logs
Not gonna show all the logs, but the main one to check is number 1.
6. Grafana
Next, Grafana is installed here, and there are three ways to access it:
1. Install a browser on the server.
Here’s a link with instructions: https://t.me/dknodes/63
2. Use SSH port forwarding:
ssh -L 3000:localhost:3000 <user>@<remote_server>
• 3000 on the left side (-L 3000:localhost:3000) is the local port on your machine.
• 3000 on the right side refers to the remote server’s port that you want to forward.
• <user> is your username on the remote server.
• <remote_server> is the IP address or domain of the remote server.
3. Modify the configuration to make it publicly accessible (not recommended).
To do this, replace 127.0.0.1:3000 with 0.0.0.0:3000 in the file:
• Abstract/external-node/mainnet-external-node.yml (for mainnet)
• Abstract/external-node/testnet-external-node.yml (for testnet)
Next, go to http://localhost:3000/d/0/external-node.
If you chose option 3, replace “localhost” with your server’s IP address.
- Tutorial on Nodes | Part 1
- Where to buy servers for nodes
- Why Securing Your Server Is Important and How to Do It
- The Importance of Using Different Ports When Running Multiple Nodes on One Server
- What is Docker?
- Unchain Node per one click!
- Ocean Node per one click!
- Hemi Node Management Manual
- Node From BlockMesh
- Node From Nesa
- Elixir Node
- INK NODE
- LENS PROTOCOL NODE
- Nexus Node
- OpenLedger Node Manual
- Titan Network | Manual
All the info on nodes, giveaways, educational content, and research will be on our channel — DKNODES, GitHub and X (Twitter).
Thanks for your attention, node runners!