-
hyc
I had 142 accepted shares and 3 rejected
-
hyc
never noticed rejected shares before
-
sech1
hyc what was the reject reason? xmrig should show it
-
hyc
[2021-08-27 23:27:26.372] cpu rejected (81/1) diff 383076 "Invalid job id" (15539 ms)
-
hyc
[2021-08-27 23:27:26.372] net no active pools, stop mining
-
hyc
[2021-08-27 23:27:31.497] net use pool 192.168.1.214:3333 192.16
-
hyc
-
hyc
looks like it was just stale
-
hyc
diff 383076 was on line 4
-
sech1
share was rejected at 23:27:26.372 and was sent to p2pool at 23:27:10.833. p2pool sent 4 new jobs between these two points and it only remembers last 4 job IDs. Which means that this share reached p2pool and was verified sometime between 24.218 and 26.372, 14 seconds after it was sent. It's something with your network again
-
sech1
or something with your p2pool build...
-
garth
Have we crossed 3GHZ on mainnet yet? Seems like we are getting awfully close
-
nioc
2.95 now, it has been between 2.64 and 2.84 for the past week
-
hyc
yeah I see a few connection timed out messages here, so something is still flaky with the mac
-
hyc
xmrig says ping time 89ms which is ridiculously slow for this LAN
-
hyc
and once again p2pool was reporting a lower height than monerod actually had
-
hyc
so maybe zmq-pub is sending out of date info
-
hyc
heh. even the xmrig miner on the mac reports a ping time of 34ms, that's localhost
-
hyc
seems like macos is just a pig
-
hyc
or libuv sucks
-
hyc
either or both could be true
-
sech1
or libuv on macos sucks
-
hyc
why does p2pool need to execute randomx itself? why doesn't it just trust the hashes its miners submit?
-
hyc
\i suppose if p2pool sent bad hashes to monerod it would eventually get banned
-
hyc
never mind... still it would be nice not to need up to 3 instances of randomx on a machine. if we isolate randomx hasing to its own process
-
hyc
and let monerod and p2pool send data to it over a socket for verification
-
hyc
would reduce footprint
-
hyc
xmrig itself could serve that purpose
-
hyc
meanwhile configure a trusted client mode in monerod and p2pool for a local xmrig
-
sech1
why would p2pool trust other nodes without checking PoW on blocks they send?
-
hyc
right, it can't.
-
sech1
New hashrate ATH at block
xmrchain.net/block/2437045 - 3012.8 MH/s