Salvium P2Pool

Decentralized pool for Salvium mining. Originally forked from SChernykh's P2Pool for Monero, this implementation has been extensively rewritten and improved for Salvium.

Build Status

Contents

• Pool mining vs Solo mining vs P2Pool mining
• Features
• How payouts work in P2Pool
• Default P2Pool parameters
• Salvium version support
• How to mine on P2Pool
  • General Considerations
  • GNU/Linux
  • Windows
• Build instructions
• Donations

Pool mining vs Solo mining vs P2Pool mining

Here's the comparison table of the different ways of mining. While pool mining is the easiest to setup, it centralizes Salvium network and pool admin gets full power over your hashrate and your unpaid funds. Solo mining is 100% independent and the best for the network. P2Pool mining has all the advantages of solo mining, but also makes regular payouts possible.

Pool type	Payouts	Fee	Min. payout	Centralized?	Stability	Control	Setup
Centralized pool	Regular	0-3%	0.001-0.01 SAL	Yes	Less stable due to pool server outages	Pool admin controls your mined funds, what you mine and can execute network attacks	Only miner software is required
Solo	Rare	0%	Full block reward	No	As stable as your Salvium node	100% under your control	Salvium node + optional miner
P2Pool	Regular	0%	~0.04 SAL	No	Very stable: node failover and multiple Salvium nodes are supported	100% under your control	Salvium node(s) + P2Pool node(s) + optional miner(s)

Features

• Decentralized: no central server that can be shutdown/blocked. P2Pool uses a separate blockchain to merge mine with Salvium. Pool admin can't go rogue or be pressured to do an attack on the network because there is no pool admin!
• Permissionless: there is no one to decide who can mine on the pool and who can't.
• Trustless: there is no pool wallet, funds are never in custody. All pool blocks pay out to miners directly.
• PPLNS payout scheme
• 0% fee
• 0 SAL payout fee
• ~0.04 SAL minimal payout
• Fast block times, down to 1 second
• Uncle blocks are supported to avoid orphans - all your shares will be accounted for!
• Configurable PPLNS window size and block time
• Advanced mempool picking algorithm, it creates blocks with better reward than what salviumd solo mining does
• Password protected private pools
• Highly reliable configurations are supported (multiple P2Pool nodes mining to the same wallet, each P2Pool node can use multiple Salvium nodes and switch on the fly if an issue is detected)

How payouts work in P2Pool

First you need to find a pool share. This share will stay in PPLNS window for up to 2160 pool blocks (6 hours, auto adjustable to balance payout sizes and frequency). The moment P2Pool finds a Salvium block and you have at least 1 pool share in PPLNS window, you'll get a payout! Salvium block reward is split between all miner wallets in PPLNS window. Each miner gets a part of block reward proportional to the total difficulty of his/her shares in PPLNS window.

NOTE If P2Pool doesn't have enough hashrate to find Salvium blocks faster than every 6 hours on average (~15 MH/s), not all your pool shares will result in a payout. Even if pool hashrate is higher, bad luck can sometimes result in a share going through PPLNS window without a payout. But in the long run it will be compensated by other shares receiving multiple payouts - your payouts will average out to what you'd get with regular pool mining.

Default P2Pool parameters

• Block time: 10 seconds
• PPLNS window: up to 2160 blocks (6 hours, auto adjustable to balance payout sizes and frequency)
• Minimum payout requires at least 1 share in the PPLNS window and is proportional to the block reward divided across the total window

Salvium version support

• The latest Salvium v10 network upgrade happened on October 13th, 2025 (block 334,750).

In order to continue mining on P2Pool, you must update both Salvium and P2Pool software to the latest available versions as soon as they are released.

Salvium protocol version	Required Salvium software version	Required P2Pool version
v10	v1.0.7 or newer	v4.14 or newer

How to mine on P2Pool

General Considerations

• In order to mine on P2Pool, a synced Salvium node using salviumd v1.0.7 or newer is required. If you don't currently have one, you can download the official Salvium binaries, start salviumd on your PC and wait until it's fully synced.
• It is highly recommended that you create a separate restricted user account (in your OS) for mining. While P2Pool has been battle-tested for a long time now, any software may have unknown bugs/vulnerabilities.
• You can mine to a primary wallet address (the one starting with SC1) for mining. If you want to mine to a subaddress, you will need to provide both the main address (starting with SC1) and the subaddress (starting with SC1s) using --wallet and --subaddress command line parameters.
• Note: The --mini and --nano sidechains are not yet operating for Salvium. These will be launched once there is sufficient hashrate and demand. For now, use the main P2Pool sidechain.
• Check that ports 19080 (Salvium p2p port) and 38889/38888 (P2Pool/P2Pool mini p2p port) are open in your firewall to ensure better connectivity. If you're mining from a computer behind NAT (like a router) you could consider forwarding the ports to your local machine.
• You can connect multiple miners to the same P2Pool node. The more the better!
• The steps below assume that you run everything on the same machine. If it's not the case, change 127.0.0.1 to appropriate IP addresses for your setup.
• It is highly recommended to create a new mainnet wallet for P2Pool mining because wallet addresses are PUBLIC on P2Pool.

Wallet software compatible with P2Pool payouts

• Official Salvium CLI and GUI v1.0.7 and newer

GNU/Linux

1. Download the latest P2Pool binaries from the releases page.
   • Alternatively, grab the latest source code for P2Pool and build it.
2. Download the latest XMRig (linux-static-x64) binary here.
3. Prepare enough huge pages (each of salviumd/P2Pool/XMRig needs them):

sudo sysctl vm.nr_hugepages=3072

4. Check that ports 19080 (Salvium p2p port) and 38889/38888 (P2Pool/P2Pool mini p2p port) are open in your local firewall to ensure better connectivity.
5. Start salviumd with the following command/options:

./salviumd --zmq-pub tcp://127.0.0.1:19083 --out-peers 32 --in-peers 64 --enforce-dns-checkpointing --enable-dns-blocklist

Note: The --zmq-pub option is required for P2Pool to work properly.

--out-peers 32 --in-peers 64 is needed to (1) have many connections to other nodes and (2) limit incoming connection count because it can grow uncontrollably and cause problems when it goes above 1000 (open files limit in Linux). If your network connection's upload bandwidth is less than 10 Mbit, use --out-peers 8 --in-peers 16 instead.

--enforce-dns-checkpointing is needed to combat the selfish mining attempts by malicious actors.

--enable-dns-blocklist is needed to ban known bad nodes.

6. Start P2Pool with the following command/options:

./p2pool-salvium --host 127.0.0.1 --wallet YOUR_WALLET_ADDRESS

7. Wait until the initial P2Pool sync is finished (shouldn't take more than 5-10 minutes).
8. Start XMRig with the following command/options:

./xmrig -o 127.0.0.1:3333

• Note that you don't need to specify your wallet address for XMRig. Wallet addresses set in XMRig config will be ignored!
• To set a custom fixed difficulty for your miner (for example, 10000), instead start XMRig with the following options:

./xmrig -u x+10000 -o 127.0.0.1:3333

9. XMRig should connect and start mining!

Additional Information:

• You can check the p2pool.log for any warnings or errors using the following command:

grep -E 'WARNING|ERROR' p2pool.log

• P2Pool has verbose logging by default, you can reduce it by using "loglevel N" command where N is between 0 and 6. Default loglevel is 3.
  • You can use logrotate with a config like this to control logfile growth:

<path-to-logfile>
{
rotate 7
daily
missingok
delaycompress
nocreate
}

Windows

Note: Windows SmartScreen may block incoming connections by files that are "Downloaded from the Internet". You can allow 'p2pool-salvium.exe' and 'salviumd.exe' by double-clicking them, clicking "More Info", then click "Run Anyway" and then closing them immediately so you can run them from the command line. Advanced users can use the PowerShell cmdlet Unblock-File to remove this flag.

1. Download the latest P2Pool binaries from the releases page.
   • Alternatively, grab the latest source code for P2Pool and build it.
2. Download the latest XMRig binary here.
3. Expand the P2Pool binaries into an appropriate location (%USERPROFILE%/bin or C:/bin/ are good options)
4. Expand XMRig binary into an appropriate location (the same folder as P2Pool is fine).
5. Prepare huge pages to work properly (each of salviumd/P2Pool/XMRig needs them):
   • On Windows 10 or above, run XMRig at least once as Administrator (right-click Run As Administrator)
   • On earlier versions of Windows, you'll need to run XMRig as Administrator at least once per login.
6. Create "Salvium" folder inside extracted P2Pool folder and copy Salvium binaries there.
7. Open a command prompt and navigate to the folder where you extracted P2Pool.

Note: When running the below commands, Windows Firewall may prompt to allow connections, click "Allow" if prompted.

8. Start salviumd with the following command/options:

.\Salvium\salviumd.exe --zmq-pub tcp://127.0.0.1:19083 --out-peers 32 --in-peers 64 --enforce-dns-checkpointing --enable-dns-blocklist

Note: The --zmq-pub option is required for P2Pool to work properly.

--out-peers 32 --in-peers 64 is needed to (1) have many connections to other nodes and (2) limit incoming connection count because it can grow uncontrollably and cause problems when it goes above 1000 (open files limit in Linux). If your network connection's upload bandwidth is less than 10 Mbit, use --out-peers 8 --in-peers 16 instead.

--enforce-dns-checkpointing is needed to combat the selfish mining attempts by malicious actors.

--enable-dns-blocklist is needed to ban known bad nodes.

9. Start P2Pool with the following command/options:

.\p2pool-salvium.exe --host 127.0.0.1 --wallet YOUR_WALLET_ADDRESS

10. Wait until the initial P2Pool sync is finished (shouldn't take more than 5-10 minutes).
11. Start XMRig with the following command/options:

.\xmrig.exe -o 127.0.0.1:3333

• Note that you don't need to specify your wallet address for XMRig. Wallet addresses set in XMRig config will be ignored!
• To set a custom fixed difficulty for your miner (for example, 10000), instead start XMRig with the following options:

  xmrig.exe -u x+10000 -o 127.0.0.1:3333
  

12. XMRig should connect and start mining!
13. (Optional but highly recommended) You can create a Quickstart by creating a batch (.bat) file with the following contents and placing it in your P2Pool directory along with xmrig.exe.

@ECHO OFF
start cmd /k %~dp0\Salvium\salviumd.exe --zmq-pub tcp://127.0.0.1:19083 --out-peers 32 --in-peers 64 --enforce-dns-checkpointing --enable-dns-blocklist
ECHO Wait until the Salvium daemon shows fully synced before continuing. This can take some time. Type 'status' in other window to check progress.
PAUSE
start cmd /k %~dp0\p2pool-salvium.exe --wallet YOUR_WALLET_ADDRESS
ECHO Wait until the P2Pool shows fully synced before continuing. This can take some time.
PAUSE
%~dp0\xmrig.exe -o 127.0.0.1:3333

Build instructions

Only 64-bit builds are supported, in particular ARMv7 or older CPUs are not supported. The reason is that RandomX hashing algorithm is too slow in 32-bit mode, and P2Pool needs to check new blocks very fast to keep up with other nodes.

Prerequisites

• cmake >= 3.10
• C++ compiler with C++17 support. GCC-8, Clang-13 and MSVC-2019 have been tested and confirmed to work, older compilers may fail to build P2Pool.

Ubuntu 20.04

Run the following commands to install the necessary prerequisites, clone this repo, and build P2Pool locally on Ubuntu 20.04:

sudo apt update && sudo apt install git build-essential cmake libuv1-dev libzmq3-dev libsodium-dev libpgm-dev libnorm-dev libgss-dev libcurl4-openssl-dev libidn2-0-dev
git clone --recursive https://github.com/mxhess/p2pool-salvium
cd p2pool-salvium
mkdir build && cd build
cmake ..
make -j$(nproc)

Arch Linux

# Build from source using the instructions above
git clone --recursive https://github.com/mxhess/p2pool-salvium
cd p2pool-salvium
mkdir build && cd build
cmake ..
make -j$(nproc)

Windows

P2Pool binary (Visual Studio Community 2019 build): NOTE: You need to have the "Desktop Development with C++" module installed.

git clone --recursive https://github.com/mxhess/p2pool-salvium
cd p2pool-salvium
mkdir build
cd build
cmake .. -G "Visual Studio 16 2019"

then open generated build\p2pool.sln in Visual Studio and build it there

Alternatively, you can select "Clone a repository" within the GUI, then select "Build" from the menu.

macOS

Run the following commands to install the necessary prerequisites, clone this repo, and build P2Pool locally on your Mac:

brew update && brew install git cmake libuv zmq libpgm curl
git clone --recursive https://github.com/mxhess/p2pool-salvium
cd p2pool-salvium
mkdir build && cd build
cmake ..
make -j$(sysctl -n hw.logicalcpu)

FreeBSD

Run the following commands to install the necessary prerequisites, clone this repo, and build P2Pool locally on FreeBSD:

pkg install git cmake libuv libzmq4 curl
git clone --recursive https://github.com/mxhess/p2pool-salvium
cd p2pool-salvium
mkdir build && cd build
cmake ..
make

Android (Termux)

Run the following commands to install the necessary prerequisites, clone this repo, and build P2Pool locally in Termux:

pkg install git build-essential cmake libuv libzmq libcurl
git clone --recursive https://github.com/mxhess/p2pool-salvium
cd p2pool-salvium
mkdir build && cd build
cmake ..
make -j$(nproc)

Donations

If you'd like to support further development of Salvium P2Pool, you're welcome to send any amount of SAL to the following address:

SC1siDDg9o3hBrSHJPBaGPXmJvPcUku8nD84cCT2PNUn61PxtdtBynHBiCaUf7BbNJctmU8LKabiHNE8x5ReYg6RYEhSqRFcL2W

Credits

This project was originally forked from P2Pool by SChernykh (Monero). Credit for the original P2Pool concept and implementation goes to SChernykh and contributors. The Salvium implementation has been extensively rewritten with significant improvements and adaptations for the Salvium network.