Closed Paul1804 closed 1 year ago
It should be compatible. You need to make your stratum IP:port available from outside, check your firewall settings.
How can I put the difficulty on the p2pool? They (NiceHash) recommend meaning >= 262144.00
It's on the main page:
To set a custom fixed difficulty for your miner (for example, 10000), instead start XMRig with the following options:
xmrig.exe -u x+10000 -o 127.0.0.1:3333
But even with default settings, p2pool will give tasks with difficulty 4,000,000 at first, and then auto-adjust difficulty to 30 seconds per share.
Do you think it is possible to do without it in the case of a NiceHash?
I check my p2pool through NiceHash instruments
......please comment on
It used to work, maybe they changed something. The screenshot doesn't show what was the error.
It works for me:
What command line do you use for your p2pool instance?
this command....
./p2pool --loglevel 1 --no-randomx --in-peers 10 --no-autodiff --host 10.0.0.2 --wallet 47YmJAymcRB69jLsaexS2hFGJe4QKzBLuX47Gj3fKuSa999sJ4bb5f5XEV7yAHJKbs1toqAYHhGUp2CAmf7QsQnAM9FT3Rf --stratum 0.0.0.0:3334 --p2p 0.0.0.0:37888
I connected in this p2pool with xmrig. No problem. All is working. Check it. 146.59.10.99:3334 Below, my monerod config
zmq-pub=tcp://0.0.0.0:18083
rpc-bind-ip=0.0.0.0
rpc-restricted-bind-ip=0.0.0.0
confirm-external-bind=1
log-level=0
disable-dns-checkpoints=1
enable-dns-blocklist=1
prune-blockchain=1
sync-pruned-blocks=1
block-sync-size=15
--no-autodiff
is not compatible with Nicehash or MRR. They don't understand 8-byte difficulty format, but XMRig does, this is why XMRig works. Autodiff limits the difficulty to 4,000,000 and uses only 4-byte format. Difficulty above that requires better precision (8 bytes), and default p2pool difficulty with --no-autodiff
is way higher than 4,000,000.
I'll try this..
./p2pool --loglevel 1 --no-randomx --in-peers 10 --host 10.0.0.2 --wallet 47YmJAymcRB69jLsaexS2hFGJe4QKzBLuX47Gj3fKuSa999sJ4bb5f5XEV7yAHJKbs1toqAYHhGUp2CAmf7QsQnAM9FT3Rf --stratum 0.0.0.0:3334 --p2p 0.0.0.0:37888
... and it's better
Difficulty 100000 means your p2pool node is not synchronized. First make sure it's working correctly, then test on Nicehash.
is it synhronized ?
It's not synchronized. Check for warnings and errors in p2pool.log. Also, "background jobs running" should usually be empty. If you check status a few times and you see something there every time, it's not working correctly. You'll need to run with --loglevel 4
to see most warnings and errors.
I do --loglevel 4
and I see.. What you say about it ? ...and how can I fixed it ?
These warnings can be ignored. What's the ping to your node (10.0.0.2)? You use --no-randomx
, so p2pool has to ask node to calculate RandomX hashes each time, and it adds ping time to each add_external_block
. If you want faster sync, remove --no-randomx
.
10.0.0.2 it is the monerod on old computer (i686, 32 bit). His config file is..
zmq-pub=tcp://0.0.0.0:18083
rpc-bind-ip=0.0.0.0
rpc-restricted-bind-ip=0.0.0.0
confirm-external-bind=1
log-level=0
disable-dns-checkpoints=1
enable-dns-blocklist=1
prune-blockchain=1
sync-pruned-blocks=1
block-sync-size=15
I use this command line...
./p2pool --loglevel 1 --light-mode --in-peers 10 --host 10.0.0.2 --wallet 47YmJAymcRB69jLsaexS2hFGJe4QKzBLuX47Gj3fKuSa999sJ4bb5f5XEV7yAHJKbs1toqAYHhGUp2CAmf7QsQnAM9FT3Rf --stratum 0.0.0.0:3334 --p2p 0.0.0.0:37888
Now, all is -oK
....and this...
Thank you !
Compatible with a nicehash? I want to direct power to the p2pool....