Commits to master since this release
Changes in v4.8
A number of security issues were found and fixed in the console commands code. It is recommended to update to v4.8
Security fixes:
- Console: limit access via local TCP port. It was possible for local users to send console commands to a running P2Pool instance without any user access checks. Now only a user with read access to P2Pool's local API files can do it.
- Console: don't listen on a local TCP port when local API is not enabled
- Console: don't let random unformatted data end up in the log
New features:
- Added
--stratum-ban-timeoption to configure the ban time of stratum clients - API: add
last_share_found_timein local/stratum - API: added merge mining data to the
api_folder/local/merge_miningpath - Tari: added "block push via gRPC" functionality for better block propagation
Bugfixes:
- Log: always reopen the log file on SIGUSR1
- TCPServer: fixed SOCKS5 error checking logic
- Fixed host ping time calculation when using SOCKS5 proxy
- Correct unit prefix symbol for unit 'kilohash per second'
- Correct unit prefix symbol for unit 'mebibyte'
- Don't use outdated merge mining data (more than 30 minutes old) and warn the user in the log
- Get a new merge mining block template immediately after submitting a block, don't wait for a polling interval timeout
- Updated internal dependencies (curl to 8.14.1)
Special thanks to Low-power for contributions to this release.
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 --disable-dns-checkpoints --enable-dns-blocklist
--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.
--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.4.0 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 --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) - 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: