03:39:24 <gingeropolous> 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
13:43:33 <garth> Yup
13:43:41 <garth> This is a huge benefit 
13:44:21 <garth> Some voice inside any unsuccessful solo minor is always saying You sure this is set up correctly?
14:22:16 <gingeropolous> hrm, i seem to have xmrig-proxy working with a custom diff so it shows me something is happening properly
14:22:43 <gingeropolous> though i wonder if the proxy will show me if the block is found
15:10:26 <manolo1133> hello
15:11:07 <manolo1133> for around 15000 h/s from 3 pcs is better xmrig-proxy or p2pool from one of all
15:56:25 <hyc> what could possibly be not working when solo mining with daemon?
16:54:22 <w[m]> <gingeropolous> "hrm, i seem to have xmrig-..." <- Ive just been checking xmrig results for the top result being higher than the difficulty 
16:54:23 <w[m]> Not sure how to get that info from xmrig-proxy (top results)
16:56:01 <w[m]> <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)
17:10:07 <gingeropolous[m]> hyc: , i have no idea. I just like my software to not keep me in the dark about its ongoings
17:13:57 <gingeropolous[m]> and currently, monerod with an external miner attached tells you nothing about mining
17:14:45 * moneromooo adds a message like: Warning: some asshole is using your CPU to mine!
17:15:48 <gingeropolous> 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
17:16:03 <moneromooo> 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.
17:17:36 <gingeropolous> 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
17:20:00 <gingeropolous> 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
17:20:13 <gingeropolous> i.e., there are no shares
17:21:28 <moneromooo> Well, you can log the RPC calls if you twiddle the log level line.
17:21:49 <moneromooo> Might be a bit spammy though, if your daemon does much else RPC wise.
17:22:41 <moneromooo> And if the daemon doesn't send a block template, the moiner will complain.
17:26:12 <gingeropolous> bah. doesn't seem like xmrig-proxy uses zmq 
17:34:51 <sech1> manolo1133 you can connect all your pcs directly to p2pool
17:35:32 <sech1> "But I have no idea if p2pool already does the same" <- p2pool generates an unique hashing blob for each connected miner
20:25:47 <merope> <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?
21:25:01 <hyc> no idea
21:30:15 <sech1> subaddress solo mining is not supported in monerod
21:32:32 <sech1> construct_miner_tx assumes that the address it gets is a regular Monero address starting with 4...
21:35:58 <sech1> "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
21:38:01 <hyc> merope: there you have it
21:38:20 <hyc> so constructing the block template would fail immediately
21:38:51 <sech1> https://github.com/monero-project/monero/blob/master/src/rpc/core_rpc_server.cpp#L1834
21:55:55 <merope> Nice!