I'll take some small credit for poking seth in the direction of docker :D

sethsimmons: your docker container presumes a patched monerod is available?

<Inge> "Seth: your docker container..." <- Yes!

I will try to release a single tagged patched monerod later, maybe today but not sure

Back over 3 gigawatts!

new hashrate ATH: block 2442014, diff 365355834108, 3044.6319509 MH/s

We gotta have more than the 13 miners that p2pool.io reports, right?

1 miners = 1 Address

1 wallet*

So I presume we have some very high hashrate people on this pool then

that's miners who mined at least 1 pool share in the last 24 hours

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

that's your shares for whatever the next block is

because you've already been paid your previous shares

I've also gotten 5 payouts since ~yesterday

Right I see, so presumably at some point it would have been >0 but I just missed it?

yep

Right gotcha. Yeah I think I may have lost some progress whenever the port change happened

sech1: one wallet = 1 p2pool instance?

yes

you can run the same wallet on multiple nodes though

sure. and many miners against one p2pool node I presume

yes, but one p2pool node can't run more than 1 wallet

I didn't look yet but ou of curiosity how is p2pool allocating nonces to individual stratum clients?

it uses new extra nonce for each client

cool

and the base extra nonce is unique per p2pool instance?

per node\

no, they always count from 0

tx key is unique, so two instances will generate different hashing blobs

ahh, right

Can we get a hashrate on "p2pool.io/api/network/stats" so we can work out the pools % of the network hashrate?

hashrate = difficulty / 120

Ah, thanks

Is there anything I can grep for in logs to see when my shares fall out of the PPLNS window?

well, you can search for "SHARE FOUND" in the log, then 2-3 lines down there will be "SideChain add_block: height = ..."

that's the sidechain height of your share

perfect thank you.

it falls out of window at height+2160

Have received a few like this: WARNING 2021-09-04 14:07:37.2018 StratumServer client: invalid JSON request (parse error)

WARNING 2021-09-04 14:07:37.2019 StratumServer peer 94.232.43.63:7674 banned for 600 seconds

is that from random connections or does the peer mean like the peer list of other nodes?

I did a git pull and remade the p2pool binaries before restarting

Just to integrate any new changes

" 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

We’ve passed 1% of the mainnet hash rate :)

we were there a few days ago too. nice to see it continue

Any guesses of what percent where we’ll stabilize at?

51%

:P

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

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.

*If

38 bytes per output * 2160 outputs = 82080 bytes max for coinbase outputs

82kb ain’t bad at all

The 38 bytes per output is amazingly small

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

when I run p2pool with screen it's ignoring the config and putting me on the old sidechain.

screen -S p2pool ./p2pool blah blah blah

Not sure if this is a Linux knowledge gap for me, but anyone else been able to run it this way?

garth I'll add versioning when there will be more than 1 version :)

QuickBASIC works just fine for me, running it inside latest debian docker container

do you have spaces in the config path?

No it's ~/.bin/p2pool/config.json

hmm, have you tried fullpath?

screen can be fickly sometimes, atleast for me

Run with strace to see what config file it's trying to open.

you don't need to use config.json

default embedded config will land you on the correct sidechain

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.

prob wasn't sync yet

maybe it's really an old chain and someone is mining on it

it's not easy to kill p2pool, as designed :)

lol

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.

I'm running my node in screen, no problems

lol @ hack the Pentagon

split the screen into two vertically and have monerod on one side too, with high log level

sell the footage to hollywood studios

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.

i.e. I'm Linux nub so probably running something wrong.

Have you tried separating the Screen command from starting p2pool? I am running mine that way and it working great.

yeah I always just run a screen window itself, then start something inside it.

because it's annoying for the window to just disappear if the inner command exits

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?

./p2pool --help ???

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?

New block! :D

Another block!

Nice.

I like how it immediately pops up in the wallet

Another block in the wallet... Hey, miners, leave these rigs alone.

We don't need no computations

We don’t need no single-output coinbase

Would a pruned node be problematic or lead to issues with p2pool?

I'm running with a pruned node and haven't had any problems.