Re: 557870: Thanks for the heads up. I had forgotten that I had been doing some bitcoind development on server computer while my hashrate was off on pool.bitcoin.com, and was running buggy incomplete code. I fixed this on Wednesday shortly after that orphan block was found.
On another note: Someone with the address 18Wc9XdyCBq8fazP5yErKGA64JVEFENJ1p decided to send about 5 PH/s to my BCH node suddenly. The sudden increase in the number of connections saturated a per-login 1024 open file limit on that account, which made the server get all buggy and drop connections. I've increased the open file limit, and performance is again normal. You're welcome to continue mining there if you'd like.
Warning: i'm seeing quite a few lines like this:
2018-12-01 08:28:43.072649 GOT SHARE! 18Wc9XdyCBq8fazP5yErKGA64JVEFENJ1p 6654496d prev 191c7d81 age 5.77s DEAD ON ARRIVAL
which suggests poor performance (high latency?) on your end. It looks like you're losing about 2% of your hashrate due to DOAs. That's not awful, but maybe worth optimizing.
@jtoomim: That is me. Hopefully it is up to ~7-8 PH/s now. Spinning up my own p2pool node and figured I'd try yours out while waiting for it to sync since we're neighbors in Grant County. How delighted I was to find out you not only contribute/maintain your p2pool git, but that you're also mining BCH on your own node.
Re: the DOA shares, hmm. Absolutely worth optimizing, IMO. Assuming your server is hosted locally I should have fantastic latency to you from only a few miles away. I know my GPU-based private pool server is hosted at a datacenter in Seattle and I get ~5ms ping (from the rig itself to the config server/pool server in Seattle, fully end-to-end). I'm not sure why, I will swap over to my node and see if I am getting the same results and keep yours as failover if you don't mind. Appreciate the work you're doing here. Now I wish I had been in town to come check out your farm open-house after one of the last PUD meetings