06:53:54 I'll take some small credit for poking seth in the direction of docker :D 08:28:16 sethsimmons: your docker container presumes a patched monerod is available? 11:36:00 "Seth: your docker container..." <- Yes! 11:36:19 I will try to release a single tagged patched monerod later, maybe today but not sure 12:58:53 Back over 3 gigawatts! 13:07:01 new hashrate ATH: block 2442014, diff 365355834108, 3044.6319509 MH/s 13:08:00 We gotta have more than the 13 miners that p2pool.io reports, right? 13:08:31 1 miners = 1 Address 13:08:42 1 wallet* 13:09:32 So I presume we have some very high hashrate people on this pool then 13:09:36 that's miners who mined at least 1 pool share in the last 24 hours 13:13:24 Sorry, still getting my head around this. I know things are working because I've had 5 payouts already over the past few days but everything pool side implies I haven't done anything. Like 0H/s, "Your shares" is 0 and est block reward is also 0 13:13:48 that's your shares for whatever the next block is 13:13:59 because you've already been paid your previous shares 13:15:16 I've also gotten 5 payouts since ~yesterday 13:15:22 Right I see, so presumably at some point it would have been >0 but I just missed it? 13:15:29 yep 13:16:34 Right gotcha. Yeah I think I may have lost some progress whenever the port change happened 13:19:27 sech1: one wallet = 1 p2pool instance? 13:19:42 yes 13:19:53 you can run the same wallet on multiple nodes though 13:21:23 sure. and many miners against one p2pool node I presume 13:23:14 yes, but one p2pool node can't run more than 1 wallet 13:27:05 I didn't look yet but ou of curiosity how is p2pool allocating nonces to individual stratum clients? 13:39:16 it uses new extra nonce for each client 13:39:56 cool 13:40:37 and the base extra nonce is unique per p2pool instance? 13:40:46 per node\ 13:42:44 no, they always count from 0 13:43:20 tx key is unique, so two instances will generate different hashing blobs 13:43:50 ahh, right 13:46:22 Can we get a hashrate on "https://p2pool.io/api/network/stats" so we can work out the pools % of the network hashrate? 13:50:10 hashrate = difficulty / 120 13:55:19 Ah, thanks 14:22:06 Is there anything I can grep for in logs to see when my shares fall out of the PPLNS window? 14:23:21 well, you can search for "SHARE FOUND" in the log, then 2-3 lines down there will be "SideChain add_block: height = ..." 14:23:29 that's the sidechain height of your share 14:23:39 perfect thank you. 14:23:40 it falls out of window at height+2160 14:51:26 Have received a few like this: WARNING 2021-09-04 14:07:37.2018 StratumServer client: invalid JSON request (parse error) 14:51:26 WARNING 2021-09-04 14:07:37.2019 StratumServer peer 94.232.43.63:7674 banned for 600 seconds 14:52:00 is that from random connections or does the peer mean like the peer list of other nodes? 15:03:47 I did a git pull and remade the p2pool binaries before restarting 15:03:55 Just to integrate any new changes 15:15:57 " StratumServer client: invalid JSON request (parse error)" could've been some random connection to your stratum port if you enabled it in firewall for the Internet 15:16:58 We’ve passed 1% of the mainnet hash rate :) 16:10:02 we were there a few days ago too. nice to see it continue 16:50:14 Any guesses of what percent where we’ll stabilize at? 16:50:44 51% 16:50:50 :P 16:53:21 I believe there's a practical upper bound when the coinbase txn gets too big. if it becomes a significant proportion of the overall txn size and resulting txn exceeds the median blocksize 16:57:57 Of that's the case, then wouldn't the block size eventually increase to compensate because if p2pool is mining a significant portion of the last 100 block the median size will be higher. 16:58:07 *If 16:59:54 38 bytes per output * 2160 outputs = 82080 bytes max for coinbase outputs 17:23:16 82kb ain’t bad at all 17:23:44 The 38 bytes per output is amazingly small 17:25:04 Sech1: Are you going to put versioning into the connection descriptions? It might be nice to see what version of the software the network is using 17:30:14 when I run p2pool with screen it's ignoring the config and putting me on the old sidechain. 17:30:14 screen -S p2pool ./p2pool blah blah blah 17:30:14 Not sure if this is a Linux knowledge gap for me, but anyone else been able to run it this way? 17:33:46 garth I'll add versioning when there will be more than 1 version :) 17:34:53 QuickBASIC works just fine for me, running it inside latest debian docker container 17:35:23 do you have spaces in the config path? 17:36:06 No it's ~/.bin/p2pool/config.json 17:36:36 hmm, have you tried fullpath? 17:36:49 screen can be fickly sometimes, atleast for me 17:38:01 Run with strace to see what config file it's trying to open. 17:38:06 you don't need to use config.json 17:38:20 default embedded config will land you on the correct sidechain 17:39:51 Oh hmm. Weird. When I run it with screen status shows a total hash of 10 Mh/sec so I assumed it was the old chain. 17:40:33 prob wasn't sync yet 17:41:47 maybe it's really an old chain and someone is mining on it 17:42:23 it's not easy to kill p2pool, as designed :) 17:42:33 lol 17:45:27 I'll have to mess with it later. I thought I'd enabled SSH on that machine, but apparently not. I just wanted to run p2pool in screen so I can check it without walking across the house. My daughter asked if I was trying to hack the Pentagon because I keep on going into the den to look at the stats. 17:46:07 I'm running my node in screen, no problems 17:46:46 lol @ hack the Pentagon 17:47:03 split the screen into two vertically and have monerod on one side too, with high log level 17:47:12 sell the footage to hollywood studios 17:48:02 Yeah, I'm pretty sure it's a knowledge gap. The only reason I can navigate Linux at all is b/c I used to admin some old ass Solaris systems and there's some overlap otherwise learning from scratch how to navigate. 17:48:49 i.e. I'm Linux nub so probably running something wrong. 18:05:19 Have you tried separating the Screen command from starting p2pool? I am running mine that way and it working great. 18:06:02 yeah I always just run a screen window itself, then start something inside it. 18:06:17 because it's annoying for the window to just disappear if the inner command exits 18:08:12 I was gonna ask if there is a way or a plan to add down the road to have the options used with the p2pool command listed in some kind of config file? 18:08:51 ./p2pool --help ??? 18:12:13 maybe I worded that wrong, can I make a config.json or add to the current one in the parent folder that holds the host,rpc-port,wallet address etc? 18:18:21 New block! :D 21:16:48 Another block! 21:21:24 Nice. 21:22:12 I like how it immediately pops up in the wallet 21:22:23 Another block in the wallet... Hey, miners, leave these rigs alone. 21:22:36 * moneromooo tiptoes out 21:25:17 We don't need no computations 21:25:22 * DaveyJones sees himself out 23:07:19 We don’t need no single-output coinbase 23:07:55 * garth hires an assassin to take out a hit on himself 23:08:52 Would a pruned node be problematic or lead to issues with p2pool? 23:13:33 I'm running with a pruned node and haven't had any problems.