SChernykh/p2pool v3.3

P2Pool v3.3

on GitHub

PSA: this release has a known bug #262 - it affects those who run P2Pool as a service on certain Linux distributions. The solution is in comments.

Changes:

• Fixed a rare sync bug (a new peer couldn't sync sometimes and needed a restart)
• Improved stability (fixed a data race bug introduced in v3.2)
• Console can now read commands via localhost TCP (port number to connect to can be read from api/local/console json)
• Stratum API: added block reward share percent
• Refactored code to reduce compiled binary size
• Improved internal memory allocation for TCP connections
• Added --version command line parameter
• TCPServer: use /64 prefix to ban IPv6 peers

Before you start mining, create a new wallet and don't use it for anything else but mining for privacy reasons - all wallet addresses are public on P2Pool! Only primary wallet address is supported - no subaddresses or integrated addresses.

It is strongly recommended to synchronize your system clock before you start mining!

Recommended monerod command line parameters:

./monerod --zmq-pub tcp://127.0.0.1:18083 --out-peers 64 --in-peers 32 --add-priority-node=node.supportxmr.com:18080 --add-priority-node=nodes.hashvault.pro:18080 --disable-dns-checkpoints --enable-dns-blocklist

--out-peers 64 --in-peers 32 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 16 --in-peers 8 instead.

--add-priority-node=node.supportxmr.com:18080 --add-priority-node=nodes.hashvault.pro:18080 is needed to have guaranteed good working nodes in your connected peers.

--disable-dns-checkpoints is needed to avoid periodical lags when DNS is updated (it's not needed when mining)
--enable-dns-blocklist is needed to ban known bad nodes

Usage:

• Run Monero daemon v0.18.2.2 or newer: ./monerod --zmq-pub tcp://127.0.0.1:18083 --out-peers 64 --in-peers 32 --add-priority-node=node.supportxmr.com:18080 --add-priority-node=nodes.hashvault.pro:18080 --disable-dns-checkpoints --enable-dns-blocklist
• Run p2pool: ./p2pool --host 127.0.0.1 --wallet YOUR_WALLET_ADDRESS
• Start mining to port 3333 on your machine: ./xmrig -o 127.0.0.1:3333
• You can set custom difficulty for your miner to get more accurate stats on P2Pool side: ./xmrig -o 127.0.0.1:3333 -u x+50000 (it doesn't affect mining rewards in any way)

Antivirus

Some antiviruses and firewalls may flag any Monero-related executables and archives, including P2Pool, as malware. This is because it contains RandomX mining code and therefore is considered as "mining software". To be sure that you downloaded the original binaries, always check SHA256 sums of what you downloaded - a GPG signed list of SHA256 sums is in sha256sums.txt.asc. You can read the instructions on how to do it here: https://www.getmonero.org/resources/user-guides/verification-windows-beginner.html - but to check P2Pool binaries, replace binaryFate's key with the GPG key provided here:

• GPG key to verify SHA256 sums can be downloaded from github or p2pool.io