i remember now one of the reasons i bailed on solo mining and was excited about p2pool... the fact that solo mining to the daemon provides no feedback regarding whether its working right

Yup

This is a huge benefit

Some voice inside any unsuccessful solo minor is always saying You sure this is set up correctly?

hrm, i seem to have xmrig-proxy working with a custom diff so it shows me something is happening properly

though i wonder if the proxy will show me if the block is found

hello

for around 15000 h/s from 3 pcs is better xmrig-proxy or p2pool from one of all

what could possibly be not working when solo mining with daemon?

<gingeropolous> "hrm, i seem to have xmrig-..." <- Ive just been checking xmrig results for the top result being higher than the difficulty

Not sure how to get that info from xmrig-proxy (top results)

<manolo1133> "for around 15000 h/s from 3..." <- Personally, I proxy it. But I have no idea if p2pool already does the same (same meaning "nicehash" the workload)

hyc: , i have no idea. I just like my software to not keep me in the dark about its ongoings

and currently, monerod with an external miner attached tells you nothing about mining

and yeah hyc , if its the daemon doing the mining, then sure, its working. its when connecting xmrig to the daemon where i feel like im just hoping all the pipes are piping and the fjords are fjording etc

But seriously, monerod doesn't know if another process is mining. It can know whether it got requested a blck template, and if a block was submitted.

yeah, i guess there's not much status to update with if the attached miners are always going for the primary diff. the only status update would be whether a block was found

but "block template sent to IP.address1.goes.here, IP.address2.goes.here ". would be nice,. i guess monerod isn't sending out new jobs besides new blocks

i.e., there are no shares

Well, you can log the RPC calls if you twiddle the log level line.

Might be a bit spammy though, if your daemon does much else RPC wise.

And if the daemon doesn't send a block template, the moiner will complain.

bah. doesn't seem like xmrig-proxy uses zmq

manolo1133 you can connect all your pcs directly to p2pool

"But I have no idea if p2pool already does the same" <- p2pool generates an unique hashing blob for each connected miner

<hyc> "what could possibly be not..." <- What if someone sets up xmrig with a subaddress, and tries to solo mine? Does xmrig issue an error/warning?

no idea

subaddress solo mining is not supported in monerod

construct_miner_tx assumes that the address it gets is a regular Monero address starting with 4...

"What if someone sets up xmrig with a subaddress, and tries to solo mine?" I think monerod will complain and xmrig will just display this error

merope: there you have it

so constructing the block template would fail immediately

Nice!