00:09:00 <crypto_grampy[m]> sech1/whoever runs p2pool.observer, some good comments in here that would help improve usability of p2pool:  https://twitter.com/vikrantnyc/status/1459287640583413760?s=20
00:09:43 <crypto_grampy[m]> i.e. i'm sure vik isn't the only one with these q's.  
00:23:22 <dubious_> that would be Mr DataHoarder :)
00:24:05 <DataHoarder> crypto_grampy[m]: I believe they haven't found shares, just while syncing
00:25:39 <DataHoarder> like, low difficulty shares that show up when you have a miner attached when you first have p2pool
00:25:58 <DataHoarder> pretty sure they don't have 17 shares found just after startup
00:26:09 <DataHoarder> on current difficulty, would be nice :)
00:26:40 <DataHoarder> maybe point them to https://p2pool.observer/calculate-share-time
00:27:16 <pauliouk> I'd be happy with 1 share found within a day of start up :P
16:06:12 <orangeboxcutter> should i set a custom fixed difficulty? i get jobs but nothing is accepted when running without a fixed difficulty
16:07:26 <sech1> it won't hurt and you will be able to see accepted
16:09:52 <orangeboxcutter> is there a way to set it so it self-adjusts?
16:10:34 <sech1> in p2pool? No
16:10:44 <sech1> just set it to 30 * hashrate of your miner
16:10:55 <orangeboxcutter> okay thanks sech1 
16:22:37 <DataHoarder> orangeboxcutter: note these "accepted" jobs won't count as shares unless they fit p2pool difficulty
16:22:43 <DataHoarder> https://p2pool.observer/calculate-share-time
16:25:46 <orangeboxcutter> so i'm better off leaving it as is and letting it run
16:25:50 <orangeboxcutter> DataHoarder
16:26:16 <DataHoarder> you can have the fixed difficulty, it's fine
16:49:17 <pauliouk> hmmm sech1 just grabbed the current git and tried to build: https://paste.debian.net/1219496/    Debian 9, all packages up to date
16:50:02 <pauliouk> uint64_t*>(id.h);  it highlighted the closing backet
16:50:05 <pauliouk> *bracket
16:52:22 <sech1> what compiler version is it?
16:52:27 <sech1> run gcc --version
16:53:21 <pauliouk> gcc (Debian 6.3.0-18+deb9u1) 6.3.0 20170516
16:54:35 <pauliouk> I'll try an upgrade see if it clears it
16:55:54 <sech1> or add -fno-strict-aliasing to the flags here: https://github.com/SChernykh/p2pool/blob/master/cmake/flags.cmake#L10
16:56:41 <pauliouk> I'll give it a shot
16:58:48 <pauliouk> yup clean compile
16:59:21 <sech1> you can also build and run tests to be sure this compiler is adequate
16:59:33 <sech1> I haven't tested such old version
17:01:15 <pauliouk> yeah the vps's are due a dist-upgrade
21:40:21 <hyc> a thought: if majority of miners increment nonce from 0 up, there is a payoff advantage in running a miner that starts from maxint and decrements to 0
21:41:02 <hyc> while random distribution should mean that either side should win with equal probability, being one of only a few miners to start from the top and work down means fewer other miners to share with
21:42:00 <hyc>  ...perhaps only interesting for solo mining...
21:51:48 <pauliouk> hmm, would that apply to p2pool? bit of an odd one
22:42:25 <DataHoarder> On p2pool you have different hashes that everyone else
22:42:33 <DataHoarder> given hash of your share is in txextra
22:42:44 <DataHoarder> and your share includes adding more payout to yourself
22:42:52 <DataHoarder> same for solomining I guess
22:42:58 <DataHoarder> you all have different base hashes
22:43:10 <DataHoarder> (also different tx privkeys)
22:43:58 <DataHoarder> Afaik hyc on solo mining each user also has their own privkey and payout address, which is hashes into the hashing blob
22:44:15 <DataHoarder> So it’s all different starting points