Skip to content

P2Pool v3.0
Compare
Choose a tag to compare
@SChernykh SChernykh released this 31 Jan 18:13
· 585 commits to master since this release
v3.0
e64a0ac

P2Pool (not Monero!) will hardfork to new consensus rules on March 18th, 2023 at 21:00 UTC. You must update to P2Pool v3.0 or newer before this date.

Changes:

  • March 18th hardfork Dynamic PPLNS window targeted to 2 Monero blocks (2 payouts) per share on average: #221
  • March 18th hardfork Fix for duplicate shares which are sometimes found and can't be added to p2pool: #222
  • March 18th hardfork Improved coinbase transaction generation (better efficiency and privacy): #223, #225
  • Much faster miner jobs generation: down from 0.75 seconds to 0.04 seconds for 10,000 connected workers
  • Display Monero node's IP:port being used in status command
  • Display number of failed shares (found but failed to be added to p2pool for various reasons) in status command
  • Display PPLNS window duration (hours and minutes) in status command
  • Reduced the delay to include new transactions in the block template being mined
  • Fixed DNS resolving failing sometimes: #229
  • Many other small bug fixes and optimizations

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.0 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:

Assets 8
Loading