How-to: Ravencoin Full Node 4.3.2.1 on Ubuntu 22.04

·

Running a Ravencoin full node on Ubuntu 22.04 is a powerful way to contribute to the decentralized network, validate transactions independently, and support the integrity of the Ravencoin blockchain. This comprehensive guide walks you through every step—from system preparation to final verification—with clear, secure, and maintainable practices.

Whether you're a blockchain enthusiast, developer, or simply interested in self-hosting infrastructure, this tutorial ensures your Ravencoin Core 4.3.2.1 installation is isolated, efficient, and production-ready.

Why Run a Ravencoin Full Node?

Before diving into setup, it’s important to understand the value of running your own node:

👉 Learn how blockchain nodes empower financial independence and security today.

System Requirements

Ensure your server meets the following minimum specifications:

Step 1: Prepare the Operating System

Start with a clean Ubuntu 22.04 installation and elevate privileges to root:

sudo su
apt update && apt upgrade -y

This ensures all system packages are up-to-date and secure before proceeding.

Step 2: Create a Dedicated User for Ravencoin

For security and isolation, run Ravencoin Core under a dedicated user account:

groupadd rvn
useradd -g rvn -m -s /bin/bash rvn
su - rvn

This limits potential damage if the service is compromised and follows Linux best practices for service separation.

Step 3: Download and Extract Ravencoin Core 4.3.2.1

Navigate to your home directory and download the official release:

wget https://github.com/RavenProject/Ravencoin/releases/download/v4.3.2.1/raven-4.3.2.1-x86_64-linux-gnu.zip

Extract the archive using Python’s built-in zipfile module and tar:

python3 -m zipfile -e raven-4.3.2.1-x86_64-linux-gnu.zip ~
tar -xf linux/raven-4.3.2.1-x86_64-linux-gnu.tar.gz

Clean up unnecessary files:

rm -rf linux __MACOSX raven-4.3.2.1-x86_64-linux-gnu.zip

Step 4: Set Up Executable Path

Make the binaries easily accessible by linking them into the user’s local bin directory:

mkdir ~/bin
ln -s ~/raven-4.3.2.1/bin/raven-cli ~/bin/raven-cli
ln -s ~/raven-4.3.2.1/bin/ravend ~/bin/ravend

Log out and back in to ensure the PATH environment variable is updated:

exit
su - rvn

Step 5: Configure Ravencoin Core

Create the configuration directory and edit the settings:

mkdir ~/.raven
vi ~/.raven/raven.conf

Add the following lines (customize externalip to match your public IPv4/IPv6):

externalip=121.98.22.147
externalip=2404:4408:63a4:a01::250
listenonion=0
disablewallet=1
dbcache=2048
Note: Set disablewallet=1 if you're not using the built-in wallet—this reduces memory usage and attack surface.

FAQ: Why disable the wallet?

Q: Why set disablewallet=1?
A: If you’re only running a node for validation or asset tracking, disabling the wallet improves performance and security by removing unused components.

Q: Can I enable it later?
A: Yes—simply remove or set disablewallet=0, then restart the daemon.

Q: What does dbcache=2048 do?
A: It allocates 2 GB of RAM for database caching, speeding up blockchain sync and query performance.

👉 Discover how secure blockchain configurations protect your digital assets long-term.

Step 6: Perform an Initial Test Run

Start the daemon manually to verify configuration:

ravend

Wait about 30 seconds, then stop it gracefully:

^C
tail ~/.raven/debug.log

Check for errors in the log output. If everything looks good, proceed to daemonize the service.

Step 7: Automate Startup with systemd

Return to root and create a systemd service file:

exit
vi /etc/systemd/system/ravend.service

Paste the following configuration:

[Unit]
Description=Ravencoin daemon
After=network.target
Wants=network-online.target

[Service]
User=rvn
Group=rvn
Type=forking
PIDFile=/home/rvn/.raven/raven.pid
ExecStart=/home/rvn/bin/ravend -daemon -pid=/home/rvn/.raven/raven.pid
KillMode=process
Restart=always
TimeoutSec=120
RestartSec=30

[Install]
WantedBy=multi-user.target

Reload systemd, enable auto-start, and launch the service:

systemctl daemon-reload
systemctl enable ravend.service
systemctl start ravend.service
systemctl status ravend.service

Monitor logs in real time:

journalctl -xeu ravend.service -f

Step 8: Configure Log Rotation

Prevent debug logs from consuming excessive disk space by setting up logrotate:

vi /etc/logrotate.d/ravend

Add this configuration:

/home/rvn/.raven/debug.log {
    su rvn rvn
    missingok
    notifempty
    compress
    delaycompress
    sharedscripts
    copytruncate
}

Test the configuration:

sudo systemctl restart logrotate.service
sudo systemctl status logrotate.service

The copytruncate directive ensures logs are rotated without stopping the running process.

Step 9: Verify Node Operation

Switch back to the rvn user and run diagnostic commands:

su - rvn
raven-cli getnetworkinfo
raven-cli getblockchaininfo
raven-cli getpeerinfo

These will show:

Monitor disk usage growth:

du -h ~/.raven/

Expect initial growth as the chain downloads—currently around 100–150 GB depending on pruning settings.

FAQ: Troubleshooting Common Issues

Q: My node isn’t showing up on ravennodes.com—why?
A: Ensure port 8767 is forwarded correctly on your router and firewall (ufw or iptables). Also verify externalip is set and publicly reachable.

Q: How long does sync take?
A: With decent hardware and bandwidth, expect 6–24 hours. Initial sync speed depends heavily on disk I/O.

Q: Should I prune the blockchain?
A: Only if storage is limited. Pruning removes old blocks but still allows full validation of new ones.

Final Checks and Network Contribution

Once synchronized, visit ravennodes.com to confirm your node appears online. This confirms successful participation in the global Ravencoin network.

You now operate a fully independent, secure, and functional Ravencoin full node on Ubuntu 22.04, supporting asset transfers, message broadcasting, and blockchain integrity.

👉 Secure your crypto journey by understanding how full nodes enhance trustless systems.

Core Keywords

By following this guide, you've not only installed software—you've become an active guardian of a decentralized ecosystem. Keep your system updated, monitor logs periodically, and consider joining community channels for ongoing support and insights.