SChernykh/p2pool (SChernykh/p2pool)
### [`v3.5`](https://togithub.com/SChernykh/p2pool/releases/tag/v3.5): P2Pool v3.5
[Compare Source](https://togithub.com/SChernykh/p2pool/compare/v3.4...v3.5)
Changes:
- **Added support for multiple Monero hosts.** P2Pool will switch to the next host in list when it thinks the current host is stuck or lagging. Documentation is [here](docs/COMMAND_LINE.MD#multiple-backup-hosts)
- Added console commands `hosts` and `next_host` to switch between hosts manually
- Rate limit peer list requests instead of banning peers who send them too often
- A few smaller bugfixes and code refactorings to improve overall stability
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.2** 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:
- GPG key to verify SHA256 sums can be downloaded from [github](https://togithub.com/monero-project/gitian.sigs/blob/master/gitian-pubkeys/SChernykh.asc) or [p2pool.io](https://p2pool.io/SChernykh.asc)
### [`v3.4`](https://togithub.com/SChernykh/p2pool/releases/tag/v3.4): P2Pool v3.4
[Compare Source](https://togithub.com/SChernykh/p2pool/compare/v3.3...v3.4)
Changes:
- Fixed a crash at startup (introduced in v3.3) when running as a service on some Linux systems
- Added MacOS aarch64 build (Apple Silicon)
- Prefer DNS TXT records to load the IP:port list of seed nodes. This makes it more flexible and immune to `hosts` file blocking
- Changed BLOCK_FOUND wording to make it clear who found the block
- P2Pool now checks Monero node ping at startup and shows a warning if it's 100 ms or more
- Added `version` console command
- P2PServer: fixed use after free bug on shutdown
- Tweaked how CURL lib is compiled for release binaries, binary size is reduced
- A few smaller bugfixes and code refactorings to improve overall stability
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.2** 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:
- GPG key to verify SHA256 sums can be downloaded from [github](https://togithub.com/monero-project/gitian.sigs/blob/master/gitian-pubkeys/SChernykh.asc) or [p2pool.io](https://p2pool.io/SChernykh.asc)
Configuration
📅 Schedule: Branch creation - "after 1pm,before 3pm" in timezone Europe/Paris, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
â™» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
v3.3->v3.5Release Notes
SChernykh/p2pool (SChernykh/p2pool)
### [`v3.5`](https://togithub.com/SChernykh/p2pool/releases/tag/v3.5): P2Pool v3.5 [Compare Source](https://togithub.com/SChernykh/p2pool/compare/v3.4...v3.5) Changes: - **Added support for multiple Monero hosts.** P2Pool will switch to the next host in list when it thinks the current host is stuck or lagging. Documentation is [here](docs/COMMAND_LINE.MD#multiple-backup-hosts) - Added console commands `hosts` and `next_host` to switch between hosts manually - Rate limit peer list requests instead of banning peers who send them too often - A few smaller bugfixes and code refactorings to improve overall stability 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.2** 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: - GPG key to verify SHA256 sums can be downloaded from [github](https://togithub.com/monero-project/gitian.sigs/blob/master/gitian-pubkeys/SChernykh.asc) or [p2pool.io](https://p2pool.io/SChernykh.asc) ### [`v3.4`](https://togithub.com/SChernykh/p2pool/releases/tag/v3.4): P2Pool v3.4 [Compare Source](https://togithub.com/SChernykh/p2pool/compare/v3.3...v3.4) Changes: - Fixed a crash at startup (introduced in v3.3) when running as a service on some Linux systems - Added MacOS aarch64 build (Apple Silicon) - Prefer DNS TXT records to load the IP:port list of seed nodes. This makes it more flexible and immune to `hosts` file blocking - Changed BLOCK_FOUND wording to make it clear who found the block - P2Pool now checks Monero node ping at startup and shows a warning if it's 100 ms or more - Added `version` console command - P2PServer: fixed use after free bug on shutdown - Tweaked how CURL lib is compiled for release binaries, binary size is reduced - A few smaller bugfixes and code refactorings to improve overall stability 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.2** 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: - GPG key to verify SHA256 sums can be downloaded from [github](https://togithub.com/monero-project/gitian.sigs/blob/master/gitian-pubkeys/SChernykh.asc) or [p2pool.io](https://p2pool.io/SChernykh.asc)Configuration
📅 Schedule: Branch creation - "after 1pm,before 3pm" in timezone Europe/Paris, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
â™» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.