Register devnet pNodes
Update your pNode software
Connect to your pNode via SSH, forwarding the required ports to the pNode localhost.
If you are using Windows, use cmd.exe or PowerShell in this format:
Be sure to verify the location of your SSH private key file and your pNode public IP address.
ssh -i "C:\path to ssh key\id_ed25519" root@<my.p.node.ip> -L 4000:localhost:4000 -L 3000:localhost:3000 -L 8000:localhost:80If you are using macOS or Linux, use this format:
Be sure to verify the location of your SSH private key file and your pNode public IP address.
ssh -i ~/.ssh/id_ed25519 root@<my.p.node.ip> -L 4000:localhost:4000 -L 3000:localhost:3000 -L 8000:localhost:80- Port 3000 is for the GUI connection (http://localhost:3000)
- Port 4000 is for the xandminerd connection
- Port 8000 is for running the Pod Monitor
Run the latest version of the install.sh script, then select Option 2: Update Xandeum pNode Software.
Run the installer as the root user.
Use sudo -i to switch to root before running the command.
Your sudo password may be required.
wget -O install.sh "https://raw.githubusercontent.com/Xandeum/xandminer-installer/refs/heads/master/install.sh" && chmod a+x install.sh && ./install.shAfter selecting Option 2, choose the default options unless you know what you are doing and want to use different settings.
- Keypair Configuration - pRPC Configuration - Atlas Cluster Configuration Select "DevNet" here - Operator Revenue Configuration This will not do anything on devnet. We have chosen 1000 as the default value, but you must still type "1000" and press Enter. - Pod Log Configuration
Wait for the completion messages. It may take several minutes. Your installed versions must be these versions or later:
Verifying services... ✓ xandminer.service is running ✓ xandminerd.service is running ✓ pod.service is running
✓ All services started successfully
xandminer: v1.3.4 (Cologne) xandminerd: v1.3.1 pod: v1.3.2
Xandminer web Service Running On Port : 3000 Xandminerd Service Running On Port : 4000
Register as a pNode owner
Keep the SSH tunnel open to one of the pNodes owned by the wallet you are registering. Then open http://localhost:3000 in your browser.
If you have upgraded correctly, you should see something like this:
Note the pNode Identity Pubkey shown on the page. Click it to copy that pNode's public key to your clipboard. You will need it later.
Connect your wallet
Using Phantom or Solflare, connect your manager wallet using the Select Wallet button. Choose the wallet that has purchased at least one pNode license.
- A wallet can have multiple pNode licenses
- Each pNode will need its own IP address
Select the "Register pNode" button
This will take you to http://localhost:3000/owner.
If this is the first time you have done this for the wallet, you will see a screen like this:
Press the Register button, then approve the transaction in your wallet. You will need a small amount of SOL in your wallet.
After the transaction is confirmed, the page should refresh to something like this:
You will see the Rewards Wallet, which you can redirect, and a table with a row for each of your pNodes.
Register each devnet pNode
Each pNode must be added individually.
Open an SSH tunnel to your first pNode and copy its public key. You can do this from the previous screen at http://localhost:3000.
In the Devnet pNode PubKey column, click the empty - placeholder for that row. Paste in the public key, then click outside the field to apply the edit. A Save button will appear, as shown below:
Click the Save button, then approve the transaction in your wallet. You will need a small amount of SOL in your wallet.
Register each pNode one at a time. Before saving a Devnet pNode public key, make sure your SSH tunnel is connected to that specific pNode. If the tunnel points to a different pNode, the transaction will fail with an expected signer mismatch error.
Once you have registered all your pNodes, you will see a screen like this:
Here you can see that each pNode is registered, along with its current credits, boost value, NFT assignment options, and Manager setting.