Running the Parallax client

Running your own Parallax node is the best way to fully participate in the network—whether you’re a miner, or just a curious user who wants to verify everything independently.
This guide walks you through downloading, installing, and running the Parallax client with the simplest possible steps. For more technical details about the Parallax client, please read the Parallax client technical documentation.

---

​

Prerequisites

Before you begin, make sure you have:

• A computer running Windows, macOS, or Linux
• At least 2 GB of RAM (4 GB recommended for mining)
• At least 50 GB of space (SSD recommended, 100 GB for mining with DAG storage)
• A stable internet connection
• Port 32110 TCP & UDP allowed through your firewall (recommended — see Accepting incoming connections)

---

​

Step-by-step Guide

✨ You’re now connected to the Parallax network!

---

​

Accepting incoming connections

Your node works without this, but it can only connect out to other nodes. Letting other nodes connect in gives you more peers and helps strengthen the network. Two things have to let the connection through: your router and your computer’s firewall.

​

Router

Most home routers need no setup. The client asks the router to forward port 32110 automatically (UPnP or NAT-PMP), and keeps the mapping alive while it runs. If that fails, the node log shows Couldn't add port mapping; in that case, enable UPnP in your router’s settings, or forward 32110 TCP & UDP to your computer by hand.

​

Firewall

The router forwarding the port is not enough: your computer’s own firewall must allow it too.

• Windows: the first time parallaxd runs, Windows asks whether to allow it on the network. Tick both “Private networks” and “Public networks”, then click Allow access. Windows treats most networks as Public by default, so allowing Private alone usually still blocks incoming connections. If you already answered the prompt, open Windows Security → Firewall & network protection → Allow an app through firewall, click Change settings, and tick both columns for parallaxd. Or run this in a terminal opened as administrator:
  netsh advfirewall firewall add rule name="Parallax P2P TCP" dir=in action=allow protocol=TCP localport=32110
  netsh advfirewall firewall add rule name="Parallax P2P UDP" dir=in action=allow protocol=UDP localport=32110
  
  If you clicked Cancel on the prompt, Windows created a rule that blocks parallaxd, and block rules win over allow rules. Remove it in the “Allow an app through firewall” list, or under Advanced settings → Inbound Rules, before adding the rules above.
• macOS: if the firewall is on, allow parallaxd when macOS asks whether it may accept incoming connections. To change it later: System Settings → Network → Firewall → Options.
• Linux: most desktop distributions ship with the firewall off. If you use ufw or firewalld:
  sudo ufw allow 32110
  # or
  sudo firewall-cmd --permanent --add-port=32110/tcp --add-port=32110/udp && sudo firewall-cmd --reload
  

---

​

For Advanced Users

If you’re comfortable with the terminal, here are a few helpful commands:

• Check version:
  ./parallaxd version
  
• Change data directory:
  ./parallaxd --datadir /custom/path
  
• Enable API:
  ./parallaxd --http --http.api "eth,net,web3"
  
• Increase log detail:
  ./parallaxd --verbosity 4
  
• Show your node on status.parallaxprotocol.org:
  ./parallaxd --prlstats
  
  Your node reports under a random name, generated once and kept in the data directory, and is shown under a pseudonym. To report to another stats service, give its address: --prlstats [email protected]. Only mainnet nodes can report to status.parallaxprotocol.org.
• Sync from Parallax testnet:
  ./parallaxd --testnet
  

---

​

Security Notice

⚠️ Never expose RPC or WebSocket ports 8545/8546 directly to the internet without proper protection. This can put your node and assets at risk. For most users, simply double-clicking the client and letting it run is the safest approach.