01:29:16 <hyc> no, it'll work
01:29:32 <hyc> miners aren't in constant communication with anything
01:30:21 <hyc> but you'll be mining fewer txns into a block than possible, if your monerod isn't receiving txns quickly
04:15:59 <fsg> hyc: thanks for the info
04:17:30 <fsg> the monerod would be running in the same host too
11:06:48 <mechanic41turk[m> Hello. I was reading https://github.com/SChernykh/p2pool#how-to-mine-on-p2pool
11:07:01 <mechanic41turk[m> the `monerod` command to run is given as:
11:07:13 <mechanic41turk[m> \>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
11:07:38 <mechanic41turk[m> I was checking https://monerodocs.org/interacting/monerod-reference/ to get a better grasp of those flags
11:08:04 <mechanic41turk[m> The `--enable-dns-blocklist` entry reads, "The DNS blocklist is centrally managed by Monero contributors. It is not recommended unless in emergency situations."
11:08:54 <mechanic41turk[m> What is the reason to enable that for running a monerod for p2pool?
11:09:10 <sech1> because it blocks known fake nodes
11:10:58 <mechanic41turk[m> okay, thanks.
11:13:27 <mechanic41turk[m> 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?
11:13:46 <mechanic41turk[m> Machine 1: generates 1.5 kh/s. Machine 2: generates: 0.5 kh/s.
11:14:03 <DataHoarder> You connect them to the same p2pool, easier :)
11:14:17 <DataHoarder> and key parameter here is the “wallet” you pass
11:14:31 <mechanic41turk[m> 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?
11:14:33 <DataHoarder> this is what accumulates shares for you, be it on your computer or elsewhere 
11:14:50 <DataHoarder> as it all ends up being shares on the same chain
11:15:10 <mechanic41turk[m> DataHoarder: There is only one p2pool currently, right? So, they are by definition connected to the same p2pool.
11:15:14 <sech1> hashrates add up
11:15:17 <mechanic41turk[m> DataHoarder: OK.
11:15:22 <mechanic41turk[m> sech1: OK, thanks.
11:15:41 <DataHoarder> Same p2pool daemon I meant, you can connect any amount of miners to it
11:15:59 <DataHoarder> even if you have different setups elsewhere it all aggregates to same wallet address 
11:16:12 <mechanic41turk[m> Good to know.
11:16:28 <mechanic41turk[m> Hoping a greater share of the hashrate for the p2pool.
18:27:27 <xmrpow> 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?
18:28:17 <pauliouk> did you grab the p2pool monerod mod too?
18:28:20 <DataHoarder> update monerod and submodules xmrpow 
18:28:36 <DataHoarder> also you can use upstream release-0.17 branch
18:28:44 <DataHoarder> https://github.com/monero-project/monero/commits/release-v0.17
18:28:50 <DataHoarder> this has the required changes already
18:29:07 <xmrpow> Ah. Ok. Didnt know about that. Thanks!