00:32:35 <gingeropolous> 41 uncles in this current window
03:02:30 <gingeropolous> P2POOOOL! P2POOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOLLLLLL!!!!
03:03:10 <gingeropolous> how u get an orphan with uncles?
03:04:47 <gingeropolous> also, how resilient is the current p2pool against attackers? can't think of how it would go down, but perhaps dos etc
03:44:34 <hyc> dos by bad hash submissions?
03:44:52 <hyc> or just sending garbage to the rpc ports i suppose?
05:54:59 <sech1> or if your monerod is lagging
06:04:48 <sech1> 3 more blocks were mined: 2438762, 2438818, 2438881
06:44:47 <Inge> are you mining on mainnet now?
06:44:52 <Inge> yes you are.
06:55:51 <sech1> p2pool hashrate 39.697 MH/s, oh my
07:26:38 <Inge> xnbya: wen p2pool hashrate on minexmr.com?
07:27:49 <Inge> I guess it is currently part of the 507MH unknown hashrate
07:32:06 <sech1> it's not easy to get this hashrate automatically yet
07:32:16 <sech1> you have to type "status" in console
08:13:21 <Guest9960> Hi all! Tried out p2pool this morning, following the instructions on github. Got everything to work, but difficulty is 401M, way too high for my miner. Is there any way to adjust the difficulty? Thanks!
08:35:34 <sech1> xmrig -u x+10000 -o 127.0.0.1:3333
08:35:43 <sech1> to set static difficulty 10000 for your miner
08:36:18 <sech1> or "user":"x+10000", in pools section of config.json
09:27:25 <Guest9960> Okay, xmrig is now showing lots of accepted shares w/ diff 10001. However status in p2pool says Your hashrate = 0 H/S and Your Shares = 0
09:29:27 <sech1> because you need to find that pool share with difficulty 401M
09:29:48 <sech1> check the hashrates that StratumServer status shows
09:30:38 <Guest9960> So I am supposed to find one share once in a few weeks?
09:30:48 <sech1> what's your hashrate?
09:31:07 <sech1> more like one share once in a few days even for low-end PCs
09:31:09 <Guest9960> about 2KH/s
09:31:38 <sech1> Read "How PPLNS works in p2pool" in readme
09:32:52 <sech1> so it'll take ~2.5 days on average for you. But once you find a share, it's almost guaranteed payout (sometimes even more than one) with current p2pool hashrate.
09:33:48 <Guest9960> Thanks for clarification, sech1. I really appreciate your work and will keep mining.
09:35:09 <sech1> Current p2pool hashrate is ~39.5 MH/s, it finds Monero blocks every ~2 hours 15 minutes on average and PPLNS window size is 6 hours
10:17:55 <hyc> ooo I have 1 share in current window
10:28:59 <ErCiccione> Hey folks, would you mind writing a short blog post about p2pool? I think people should be aware of this great project and a blog post on getmonero would give it a lot of visibility. Something short that just announces the project and point people to the github repo and communication channels would be enough. If you give me the markdown with the blog post i can take care of the rest
10:31:01 <ErCiccione> or even jsut a draft with the core points, then i'll take care of making the post
10:31:57 <hyc> prob any useful info you want to relay is in the p2pool README.md
10:34:29 <ErCiccione> yeah i could do it but maybe the people who work on the project would like to mention something specific. If that's not the case or nobody feels like writing a post i can do it from scratch later
10:35:43 <sech1> I don't know, try to compile something from README.md and the reddit post: https://www.reddit.com/r/Monero/comments/p9apyd/psa_monero_decentralized_mining_pool_p2pool/
10:36:28 <ErCiccione> ok
11:00:32 <sech1> hyc re "dos by bad hash submissions/just sending garbage" p2pool checks everything and bans bad peers, in theory. There's always a possibility I missed something.
11:04:23 <moneromoooo> For the record, relaying blocks before checking would bypass that (unless done very carefully maybe).
11:15:27 <sech1> p2pool nodes don't relay unchecked blocks. Broadcast is only done after full verification
11:15:41 <sech1> p2pool verification is much lighter than monerod's
11:16:36 <sech1> it does call submit_block RPC after only checkin PoW when it sees p2pool block with enough PoW, but it only happens when someone finds Monero block
12:31:12 <QuickBASIC> I finally got Ubuntu installed on an old laptop and compiled p2pool there and have been able to point all my other miners. Seems to be working.
12:32:48 <QuickBASIC> Although I was having some weird "End of file" error on some of my miners until I stopped and started p2pool, but it was probably an issue on the miner side.
12:36:12 <jaska087> avg result time 19h
12:36:13 <jaska087> nice
12:49:02 <gingeropolous> ah, ErC is gone. sech1 , is p2pool ready for blog posts etc? or are we still in the "only ppl that can help debug should use" phase?
12:53:15 <sech1> It's ok, as long as these people are able to compile their binaries.
12:56:48 <sech1> people are de-facto using it already, 38-40 MH/s already would make p2pool #11 on https://miningpoolstats.stream/monero
13:09:24 <gingeropolous> true
13:09:42 <gingeropolous> even though its only 7 total peers afaict :/
13:13:16 <jaska087> nice, did my share go old already before p2pool found a block?
13:13:17 <jaska087> D:
13:22:26 <sech1> p2pool is a bit unlucky right now
13:22:40 <sech1> should've found 2-3 blocks since the morning, but nothing so far
13:55:34 <garth> Is it possible for me to install p2pool on my VPS and then mine to it via my home computer so that it doesn’t broadcast my home IP?
13:56:16 <sech1> yes
13:56:18 <moneromoooo> Yes. And if you publish your VPS address, you might even get free hash.
13:58:09 <jaska087> myxmr.net:3000 tee-hee
13:59:28 <jaska087> does p2pool regonize subaddress/integrated addresses
14:04:42 <gingeropolous> no jaska087 , main addy only
14:07:03 <jaska087> right, so it won't run if subaddress/integrated address is used?
14:13:34 <sech1> it will say "Invalid wallet address"
14:14:44 <jaska087> Ah ok, that dono address was main address then
15:14:10 <sech1> PSA: current sidechain is borked, I found a bug tx keys generation :D
15:14:19 <sech1> I'll update p2pool soon and we'll start a new sidechain
15:14:32 <sech1> borked = not all payouts might be spendable
15:18:00 <sech1> or maybe they are spendable, but it's still a bug there. I added a few more checks for tx public/secret keys and they fail at some blocks
15:22:08 <sech1> the 3 outputs in my wallet were all spendable, that's good. Can everyone try to run sweep_all in their miner wallets?
15:29:01 <jaska087> got no balance so no go
15:31:54 <moneromoooo> Is this test useful for the testnet wallet ? I have not mined on mainnet yet.
15:32:04 <sech1> yes, check testnet wallet too
15:32:20 <moneromoooo> OK, I'll try a bit later when I can that vm)
15:32:59 <sech1> PSA: I've started a new sidechain, you'll need to build the latest code and connect to port 37889 instead (everything else is the same)
15:33:20 <sech1> funny thing is that old p2pool will continue to run and I can't stop it until everyone switches :D
15:37:28 <jaska087> done switching
15:38:36 <sech1> now we need to wait for those 40 MH/s to switch...
15:38:47 <jaska087> what? my 9kh is not enough!?
15:39:45 <sech1> every hash counts
15:40:03 <jaska087> :P
15:49:57 <moneromoooo> 1581 outputs, all could be spent.
15:55:17 <jaska087> setting custom diff for xmrig is just to calculate the pool hashrate more accurate, it does not get added to shares, right?
15:56:36 <sech1> it's to calculate hashrate
15:56:41 <sech1> in stratum server status
15:57:47 <jaska087> ah yes that is what i meant, good to know
15:58:16 <sech1> moneromoooo interesting... Funny thing is that my generate_keys skipped sc_reduce32 sometimes on 1 in 15 attempts: https://github.com/SChernykh/p2pool/commit/780afd84a2fbc10316c1c57329b8ecb3c2933f01#diff-3700f1a6da19be70db791c8b323a328192eda62ce64f3f5b70c868e1bdbf63baR87
15:58:37 <sech1> I totally forgot how "continue" works in a do..while loops.
15:59:09 <sech1> So some tx secret keys that were generated were not correct
15:59:28 <sech1> they are used to calculate stealth addresses, so I assume if you see a payout, you should be able to spend it
15:59:44 <sech1> but with added checks in that commit, old sidechain failed to verify
16:30:30 <jaska087> PPLNS window              = 411 blocks (+1 uncles, 1 orphans)
16:30:37 <jaska087> nnnooo...! think of the orphans!
16:31:40 <sech1> that was a block at height 0. I guess someone joined with miners connected and started mining before fully synced
16:32:11 <oliver_> that was me, sorry
16:32:27 <sech1> it's not a problem
16:32:38 <sech1> more like a normal way of operation for p2pool
16:34:00 <sech1> hyc ping. You need to update to the latest and switch to the new sidechain
17:03:34 <hyc> ok
17:04:18 <sech1> port number changed to 37889 to avoid lots of warnings from old nodes
17:04:55 <sech1> your shares on old sidechain will stay there and will be reward if old nodes mine a Monero block
17:10:28 <Inge> .mine 15000
17:18:14 <jaska087> so many banned nodes
17:18:54 <sech1> Then it's better to stop p2pool, delete p2pool_peers.txt and start again
17:19:11 <sech1> but it's not required, bans are temporary
17:19:18 <jaska087> aight
17:27:25 <sech1> old sidechain is still alive, mined block https://xmrchain.net/block/2439270
17:27:29 <sech1> I got a payout from that block
17:42:16 <QuickBASIC> Sorry. Just checked. Need to rebuild and change port, right? My old one is still running on old chain for another hour or so not going to disrupt anything?
17:47:13 <sech1> Just rebuild, change port and delete p2pool_peers.txt before starting again
17:47:32 <sech1> old one will not disrupt because port number has changed
18:03:51 <QuickBASIC> Roger will do. I'm out and don't have access to it at the moment.
18:11:50 <hyc> hm i didn't delete peers file
18:13:02 <sech1> It's not critical. Your node will ban incompatible peers
18:13:16 <sech1> when they update and ban expires, they should reconnect again
18:33:04 <QuickBASIC> I stopped it and will rebuild later today. I wasn't getting any shares with my 1900 h/s anyway.
18:35:02 <QuickBASIC> One of my miners kept periodically saying "end of file" and "connection refused". Over the last 10 hour or so, but then would go right back to getting "new jobs" by itself.
18:35:40 <QuickBASIC> To be clear I I built an install it on Ubuntu running on actual hardware now, so it's not running in a vm container anymore.
18:36:18 <QuickBASIC> I opened up the ports with ufw on Ubuntu, but was still seeing periodically connection refused and then it would go back to normal.
18:37:57 <QuickBASIC> Xmrig was running on a separate Windows machine and connecting to the p2p stratum on Ubuntu.
18:39:05 <sech1> connection refused shouldn't happen if p2pool is running, it's happens when you try to connect and no one is listening on that port
18:43:14 <aypro> i had it happen to me one time, turns out my p2pool banned 127.0.0.1 ... don't know why
18:45:18 <aypro> 16:56:56.7097 StratumServer peer 127.0.0.1:59955 is banned, disconnecting
18:46:13 <sech1> it should have ban reason a few lines up in the log
18:47:19 <sech1> or more than a few lines up. You can search the log for warnings from StratumServer
18:49:53 <aypro> WARNING 2021-08-31 17:17:04.4182 StratumServer client: invalid JSON request (unknown method)
18:49:53 <aypro> WARNING 2021-08-31 17:17:04.4182 StratumServer peer 127.0.0.1:57404 banned for 600 seconds
18:50:58 <sech1> unknown method? What miner is it?
18:51:15 <aypro> xmrig
18:51:34 <aypro> 6.14.1
18:52:16 <sech1> do you have keepalive on in xmrig config?
18:53:50 <aypro> yes
18:54:26 <sech1> set it to false then
18:54:35 <sech1> I need to fix it on p2pool side though
18:54:48 <sudo_ki[m]> Hi all, I'm having trouble with setting up p2pool. 
18:54:48 <sudo_ki[m]> I have built the latest version of monero-gui (17.2.3). I have firewall rules for the ports I've specified but when I run the software I get: p2pool get_miner_data RPC response is invalid. On the node I get: invalid zqm/sub message. Can anyone lend me a hand?
18:54:53 <aypro> ok, will do
18:55:48 <sech1> The node must run custom monerod build
18:57:12 <sudo_ki[m]> Ah, release is not OK? Where abouts is the repo for that build?
18:57:43 <sech1> https://github.com/SChernykh/p2pool#ubuntu-2004
18:57:57 <sech1> you need to follow the instructions for monerod binary
18:59:07 <sudo_ki[m]> XD, I glossed over it. Thanks a lot
18:59:15 <selsta> v0.17.2.3 does not contain all the changes for p2pool
20:10:52 <QuickBASIC> Can the next one be named 'mainnet test 2 electric boogaloo'?
20:21:18 <garth> p3pool
20:24:54 <sech1> Something interesting will be here https://p2pool.io/api/
20:34:56 <sech1> when it works, it should be enough to have an entry at https://miningpoolstats.stream/monero 
20:40:30 <QuickBASIC> Every time I build p2pool I have to manually go add the path to UV_LIBRARY and UV_LIBRARY_DEBUG to the CMakeCache.txt (because it's set to NOTFOUND). Am I possibly doing something wrong? It works when I add the path under /use/lib/x86_64_yaddayadda for the .so, but I prefer not to have to do it every time.
20:41:12 <QuickBASIC> * autocorrect mangled the /usr/ path but you get the idea.
20:45:14 <moneromoooo> https://paste.debian.net/hidden/75204c5e/
20:48:57 <QuickBASIC> Sorry moo, not a dev so I'm not sure what you're pointing out here.
20:49:47 <selsta> try to change it as in the posted patch
20:51:12 <QuickBASIC> Ah understood. Away from that machine at the moment but will try as soon as I can.
21:07:11 <QuickBASIC> Yeah, just tested the diff and cmake finds it now.
21:07:33 <QuickBASIC> But that's changing four lines manually instead of two.
21:08:26 <selsta> sech1: can you merge ^ ?
21:10:25 <QuickBASIC> Ahh umm my git-fu is not up to par. I'm assuming there's a programmatic way to apply the diff, but I just copy and pasted using nano lol.
21:10:50 <selsta> git apply patch
21:11:27 <QuickBASIC> Thanks selsta.
21:17:50 <sech1> merged
21:20:17 <QuickBASIC> Yay!
22:31:12 <QuickBASIC> Oh damn. I found 3 shares with my piddly 1.9 kH/s in the last 30 mins since I got back up and running.
22:31:45 <QuickBASIC> Actually more like 1 hour.
22:32:09 <QuickBASIC> But that's super lucky. I should have like 1-2 shares per 2.5 days or so.
22:33:20 <QuickBASIC> I just noticed you added the stratum hashrate stats sech1. Too cool.
22:52:50 <gingeropolous> sech1, so i think im on the new sidechain now
23:20:39 <sech1> 10 different nodes, 10 wallets in PPLNS window. This second test is more interesting so far
23:20:53 <sech1> QuickBASIC you'll get more shares now while difficulty is low
23:43:57 <QuickBASIC> sech1 I noticed a commit that doesn't allow multiple connections from the same IP. Does that mean that someone sharing a single residential connection couldn't both use p2pool independently?