From 3bcde151eef2e66d5e3a10b416983f9ca6f769c5 Mon Sep 17 00:00:00 2001 From: sech1 Date: Fri, 29 Aug 2025 18:47:29 +0200 Subject: [PATCH] Updated docs: `--enforce-dns-checkpointing` is now recommended --- README.md | 10 +- docker-compose/cfg/docker-compose.jinja2 | 2 +- docker-compose/docker-compose.yml | 2 +- docs/html/index.html | 4 +- docs/html/mini/index.html | 4 +- docs/html/nano/favicon-32x32.png | Bin 0 -> 671 bytes docs/html/nano/index.html | 320 +++++++++++++++++++++++ 7 files changed, 331 insertions(+), 11 deletions(-) create mode 100644 docs/html/nano/favicon-32x32.png create mode 100644 docs/html/nano/index.html diff --git a/README.md b/README.md index cd0de8e..54f0eca 100644 --- a/README.md +++ b/README.md @@ -154,7 +154,7 @@ sudo sysctl vm.nr_hugepages=3072 4. Check that ports 18080 (Monero p2p port) and 37889/37888 (P2Pool/P2Pool mini p2p port) are open in your local firewall to ensure better connectivity. 5. Start `monerod` with the following command/options: ``` -./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 +./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 ``` **Note:** The `--zmq-pub` option is required for P2Pool to work properly. @@ -163,7 +163,7 @@ The `--zmq-pub` option is required for P2Pool to work properly. `--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) +`--enforce-dns-checkpointing` is needed to combat the selfish mining attempts by malicious actors `--enable-dns-blocklist` is needed to ban known bad nodes @@ -222,7 +222,7 @@ nocreate 8. Start `monerod` with the following command/options: ``` -.\Monero\monerod.exe --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 +.\Monero\monerod.exe --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 ``` **Note:** The `--zmq-pub` option is required for P2Pool to work properly. @@ -231,7 +231,7 @@ The `--zmq-pub` option is required for P2Pool to work properly. `--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) +`--enforce-dns-checkpointing` is needed to combat the selfish mining attempts by malicious actors `--enable-dns-blocklist` is needed to ban known bad nodes @@ -253,7 +253,7 @@ The `--zmq-pub` option is required for P2Pool to work properly. 13. *(Optional but highly recommended)* You can create a Quickstart by creating a batch (.bat) file with the following contents and placing it in your P2Pool directory along with `xmrig.exe`. ``` @ECHO OFF -start cmd /k %~dp0\Monero\monerod.exe --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 +start cmd /k %~dp0\Monero\monerod.exe --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 ECHO Wait until the Monero daemon shows fully synced before continuing. This can take some time. Type 'status' in other window to check progress. PAUSE start cmd /k %~dp0\p2pool.exe --wallet YOUR_WALLET_ADDRESS --mini diff --git a/docker-compose/cfg/docker-compose.jinja2 b/docker-compose/cfg/docker-compose.jinja2 index 8dbf91f..3fa9593 100644 --- a/docker-compose/cfg/docker-compose.jinja2 +++ b/docker-compose/cfg/docker-compose.jinja2 @@ -118,7 +118,7 @@ services: restart: unless-stopped command: >- --zmq-pub tcp://0.0.0.0:18083 - --disable-dns-checkpoints + --enforce-dns-checkpointing --enable-dns-blocklist --out-peers 16 --in-peers 32 diff --git a/docker-compose/docker-compose.yml b/docker-compose/docker-compose.yml index 73e0461..7366cd0 100644 --- a/docker-compose/docker-compose.yml +++ b/docker-compose/docker-compose.yml @@ -94,7 +94,7 @@ services: restart: unless-stopped command: >- --zmq-pub tcp://0.0.0.0:18083 - --disable-dns-checkpoints + --enforce-dns-checkpointing --enable-dns-blocklist --out-peers 16 --in-peers 32 diff --git a/docs/html/index.html b/docs/html/index.html index c6afa18..86ba877 100644 --- a/docs/html/index.html +++ b/docs/html/index.html @@ -248,7 +248,7 @@ It's highly recommended to create a new wallet for mining because wallet address @@ -304,7 +304,7 @@ P2Pool is a decentralized community, there is no dedicated support. You can reac
  • I get an error "monerod RPC ... is incompatible, update to RPC >= v3.8"
  • I get warnings "peer ... is ahead on mainchain (height ..., your height ...). Is your monerod stuck or lagging?" -
    +


    diff --git a/docs/html/mini/index.html b/docs/html/mini/index.html index 11c4bbf..bb511d1 100644 --- a/docs/html/mini/index.html +++ b/docs/html/mini/index.html @@ -248,7 +248,7 @@ It's highly recommended to create a new wallet for mining because wallet address @@ -304,7 +304,7 @@ P2Pool is a decentralized community, there is no dedicated support. You can reac
  • I get an error "monerod RPC ... is incompatible, update to RPC >= v3.8"
  • I get warnings "peer ... is ahead on mainchain (height ..., your height ...). Is your monerod stuck or lagging?" -
    +


    diff --git a/docs/html/nano/favicon-32x32.png b/docs/html/nano/favicon-32x32.png new file mode 100644 index 0000000000000000000000000000000000000000..354734dcf71434aca9b903a17c507ab5cf81cfdb GIT binary patch literal 671 zcmV;Q0$}}#P)Px#u~1A@MMrQ<_o#mMnP~T;c&n?c_n~(Gw2%6*jrgjB z^L8=zoNe`kMfIF*WMpKNl$4yDoT#X%e}8|htgMcXj>W~rnwpxqxw)5@mu+orXlQ7z zuCD+8|NsC0^odaSpmqQD?*IS){L8cd|Nr>1j{pDvOiWDjXdLr*Gx@%sfPjEjR#xxt z?`dgi@@*vYYa#M!9%^c8@bK_#Y;00eQcq7$Q&Us&X&?Rl{hXYfRaI5=ghvAGj-LPk z03>u$PE!DU#+_iK8#8PDy!5;Lp_>}aZMi3wE3*3b8HV=qw;dZ`e2*Pj*~kC@010qN zS#tmY1=Iil1=Io3ZKcWp00BoyL_t(I%Wc!?nt~t{24GyuT-x_-S~=R3+CJ6&U)aC_ zjFRu4eD5QIK!_I4a-ztwJYtL&ggIdHFesa=f9LRRJgp>}dg3WRVs?3f31OT@W&l&A@V| z0eU`D4a}DOcTRO6Bf%8U!({Z!bJf8Whei`|q}&@d=H{wH*))UZ`&c(F<@(alFNRzH z?(6R7)oQh$di`v-O1HB&9IJXf?3pk4pwsVm`<;P4_7927aF>rI%!>d3002ovPDHLk FV1k}9LY@Es literal 0 HcmV?d00001 diff --git a/docs/html/nano/index.html b/docs/html/nano/index.html new file mode 100644 index 0000000..ac8806e --- /dev/null +++ b/docs/html/nano/index.html @@ -0,0 +1,320 @@ + + + + +P2Pool nano - Decentralized Monero mining pool + + + + + + +
    P2Pool nano
    Decentralized Monero mining pool
    +
    Latest release: P2Pool
    +
    + + + + + + +
    + + + + + + + + + + + + + + + + +
    PoolNetwork
    HashrateN/AN/A
    MinersN/A
    PPLNS windowN/A
    Last blockN/AN/A
    Total blocksN/A
    Current effortN/A
    Average effort
    last 50 blocks
    		N/A
     
    Fee0%
    Min payout0.00027 XMR
    Payout schemePPLNS
     
    StatisticsP2Pool observer
    + + +
    HeightEffortAge
    +
    + +
    P2Pool video guide +
      +
    • A detailed video guide to install P2Pool and start mining +
    +
    + +
    Setup Monero wallet +Wallets with confirmed P2Pool support
    +You might not see P2Pool payouts in other wallets if they're not updated! + +It's highly recommended to create a new wallet for mining because wallet addresses are public on p2pool. You have to use the primary wallet address for mining. Subaddresses and integrated addresses are not supported, just like with monerod solo mining. +
    + +
    Setup Monero node +
      +
    • Download the latest Monero release +
    • [Optional] Open port 18080 (Monero p2p port) in your firewall to ensure better connectivity +
    • Run ./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 +
    • If your network connection's upload bandwidth is less than 10 Mbit, use --out-peers 8 --in-peers 16 instead. +
    • Wait until it's fully synchronized. If you didn't run Monero node before, it can take up to several days to synchronize (5-6 hours on a modern PC with fast SSD and fast Internet connection). You can add --prune-blockchain argument to the command line to run a pruned node (3-4 times less disk usage) +
    + +
    Setup P2Pool node +
      +
    • Download the latest P2Pool release +
    • [Optional] Open port 37889 (P2Pool port) or 37890 (P2Pool nano port) in your firewall to ensure better connectivity +
    • Run ./p2pool --host 127.0.0.1 --wallet YOUR_WALLET_ADDRESS --nano +
    • It should take no more than 5-10 minutes to synchronize +
    + +
    Miner software +
      +
    • XMRig is recommended. XMRig Proxy is fully supported. +
    • Once P2Pool sync is complete, XMRig should be able to connect to the stratum server on port 3333 +
    • Run ./xmrig -o 127.0.0.1:3333. Note that you don't need to specify wallet address for xmrig. Wallet address set in xmrig config will be ignored! +
    • To set custom fixed difficulty for your miner (for example, 10000), run ./xmrig -u x+10000 -o 127.0.0.1:3333 +
    • To connect another mining rig to your P2Pool node, run ./xmrig -o YOUR_P2POOL_NODE_IP:3333 on that mining rig +
    + +
    Checking your progress +
      +
    • You can enter your wallet address at P2Pool Observer +
    • P2Pool Observer for P2Pool nano can be found here +
    • You will find your wallet's statistics there only after you've mined at least 1 P2Pool share +
    +
    + +
    Help and support +P2Pool is a decentralized community, there is no dedicated support. You can reach and get help from other miners on: +
    +
    +
    +
      +
    • What are system requirements to run P2Pool? +
      • P2Pool needs 0.5 GB disc space and 2.6 GB RAM to run (0.6 GB RAM in light mode). Add this to monerod requirements if you run both on the same machine. Add --light-mode to p2pool command line to reduce the memory usage to 0.6 GB, or --no-randomx --no-cache to reduce the memory usage to less than 100 MB.

      +
    • Does P2Pool work with XMRig Proxy? +
      +
    • Does monerod have to be run on the same machine as P2Pool? +
      • No, you can run them on different machines and even connect multiple p2pool instances to a single server running monerod

      +
    • Does P2Pool work with pruned Monero node? +
      • Yes, you can use pruned Monero node to mine on P2Pool

      +
    • Does P2Pool require incoming connections to work properly? +
      • P2Pool (and Monero) can work with only outgoing connections, but it's recommended to open ports 18080 (Monero) and 37889/37888/37890 (P2Pool/P2Pool mini/P2Pool nano) for better connectivity with the rest of the network.

      +
    • I have been mining for several hours and still got no rewards? +
      • P2Pool doesn't work exactly like regular pools - there's no "pending balance" here. You need to find a pool share first and then wait for P2Pool to find a Monero block. You'll get a payout to your XMR wallet as soon as a block is found and you have shares in PPLNS window. It can take several days to a week to find a share if your hashrate is low. Type "status" command in P2Pool console or visit P2Pool observer to check your progress.

      +
    • I am mining but I can't find any shares +
      • First check for any warnings and errors in P2Pool console and logs. If everything works fine, you can check the average share time calculator to get an idea how often you should find a share with your hashrate. If this time is more than 1 day, it's recommended to switch to P2Pool mini or P2Pool nano by adding --mini or --nano to P2Pool command line.

      +
    • I get an error "monerod RPC ... is incompatible, update to RPC >= v3.8" +
      • Use monerod v0.18.0.0 or newer

      +
    • I get warnings "peer ... is ahead on mainchain (height ..., your height ...). Is your monerod stuck or lagging?" +
      • Make sure you add these arguments to monerod command line: --zmq-pub tcp://127.0.0.1:18083 --enforce-dns-checkpointing --enable-dns-blocklist

      +
    +
    +

    +
    +Pool API | Source | Onion URL
    +Donate to support the project:
    44MnN1f3Eto8DZYUWuE5XZNUtE3vcRzt2j6PzqWpPau34e6Cf4fAxt6X2MBmrm6F9YMEiMNjN6W4Shn4pLcfNAja621jwyg
    +  +
    + + \ No newline at end of file