no, it'll work

miners aren't in constant communication with anything

but you'll be mining fewer txns into a block than possible, if your monerod isn't receiving txns quickly

hyc: thanks for the info

the monerod would be running in the same host too

Hello. I was reading github.com/SChernykh/p2pool#how-to-mine-on-p2pool

the `monerod` command to run is given as:

\>Run ./monerod --zmq-pub tcp://127.0.0.1:18083 --disable-dns-checkpoints --enable-dns-blocklist don't forget --zmq-pub parameter in the command line

I was checking monerodocs.org/interacting/monerod-reference to get a better grasp of those flags

The `--enable-dns-blocklist` entry reads, "The DNS blocklist is centrally managed by Monero contributors. It is not recommended unless in emergency situations."

What is the reason to enable that for running a monerod for p2pool?

because it blocks known fake nodes

okay, thanks.

Another question: Let's say I connect two computers to the same monerod for p2pool. Does the hashrate accumulate, or does these two machines act as if they are independent?

Machine 1: generates 1.5 kh/s. Machine 2: generates: 0.5 kh/s.

You connect them to the same p2pool, easier :)

and key parameter here is the “wallet” you pass

If they are connected to the same monerod for p2pool, does the hashrate mining for my wallet address act as if it is 1.5kh/s + 0.5 kh/s = 2.0kh/s?

this is what accumulates shares for you, be it on your computer or elsewhere

as it all ends up being shares on the same chain

DataHoarder: There is only one p2pool currently, right? So, they are by definition connected to the same p2pool.

hashrates add up

DataHoarder: OK.

sech1: OK, thanks.

Same p2pool daemon I meant, you can connect any amount of miners to it

even if you have different setups elsewhere it all aggregates to same wallet address

Good to know.

Hoping a greater share of the hashrate for the p2pool.

I recently pulled the latest monerod and p2pool version from sech1's github repo and now I suddenly get the following error: P2Pool monerod RPC v3.5 is incompatible, update to RPC >= v3.8. Does anybody know what I have to do to get rid off the error?

did you grab the p2pool monerod mod too?

update monerod and submodules xmrpow

also you can use upstream release-0.17 branch

this has the required changes already

Ah. Ok. Didnt know about that. Thanks!