Skip to content

P2Pool v4.16

Latest
Latest

Choose a tag to compare

View all tags
@SChernykh SChernykh released this 13 Jun 15:00
· 4 commits to master since this release
Immutable release. Only release title and notes can be modified.
v4.16
4553c0c

Commits to master since this release

Changes in v4.16

A consensus vulnerability was found and fixed. It is strongly recommended to update to v4.16

Security fixes:

  • Consensus vulnerability fixed (details will be published later)

New features:

  • Display node's RPC SSL fingerprint when connecting with SSL
  • Added TLS support to merge mining (JSON RPC)
  • Merge mining (JSON RPC): added more API fields for better UX
  • Added "stuck" detection to status command's node health rating

Bugfixes:

  • P2PServer: multiple fixes and overall hardening of the network code
  • StratumServer: enforce min diff = 1000 in all cases
  • Miner: update api correctly when stopped
  • Miner: update api's total_hashes to a correct value when stopped

Full list of changes

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!

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.5.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 --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:3333 on 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:

Assets 13
Loading