Commits to master since this release
Changes in v4.11
Recommended update, see the bugfixes section
New features:
- Subaddress support. You can now mine to a subaddress:
./p2pool --wallet MAIN_ADDRESS --subaddress SUBADDRESS ...- Pay attention that SUBADDRESS must belong to the same wallet that was specified as MAIN_ADDRESS
- Display git commit in version
- Added logging of
submit_blockRPC timings (can be used to track your Monero node's performance) - Tari: track gRPC channel state (aka node connection status) and display it in logs/status/API
Bufixes:
- Added a filter for late txpool notifications. Workaround for a Monero node bug that caused some P2Pool blocks to be invalid (1-2 blocks out of a 1000).
- Fixed a rare crash at startup caused by a wrong initialization order (it could happen when you build it from source)
- Monero block broadcasts: check PoW in background to not stall the P2P event loop
- Updated internal dependencies (curl to v8.16.0)
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 32 --in-peers 64 --add-priority-node=p2pmd.xmrvsbeast.com:18080 --add-priority-node=nodes.hashvault.pro:18080 --enable-dns-blocklist --enforce-dns-checkpointing
--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.
--add-priority-node=p2pmd.xmrvsbeast.com:18080 --add-priority-node=nodes.hashvault.pro:18080 is needed to have guaranteed good working nodes in your connected peers.
--enable-dns-blocklist is needed to ban known bad nodes
--enforce-dns-checkpointing is needed to combat the selfish mining attempts by malicious actors
Usage:
- Run Monero daemon v0.18.4.2 or newer:
./monerod --zmq-pub tcp://127.0.0.1:18083 --out-peers 32 --in-peers 64 --add-priority-node=p2pmd.xmrvsbeast.com:18080 --add-priority-node=nodes.hashvault.pro:18080 --enforce-dns-checkpointing --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) - To connect another mining rig to your P2Pool node, run
./xmrig -o YOUR_P2POOL_NODE_IP:3333on that mining rig
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: