12:56:41 <m-relay> <p​reland:monero.social> https://matrix.monero.social/_matrix/media/v1/download/monero.social/TekcGmaMfLnjmcRelORVrhUH
12:56:47 <m-relay> <p​reland:monero.social> 🤡
15:13:02 <m-relay> <r​dorsch:matrix.org> My monerod suddenly starts crashing:
15:13:04 <m-relay> <r​dorsch:matrix.org> https://paste.debian.net/hidden/dd6368b5/
15:13:06 <m-relay> <r​dorsch:matrix.org> is that a known issue?
15:13:36 <m-relay> <r​dorsch:matrix.org> Worked well before for very many blocks.
15:19:34 <sech1> Enable huge pages to stop this error
17:42:12 <m-relay> <j​effro256:monero.social> @sech1: what do you think about adding a weight clawback for miner transactions with a high amount of outputs to prevent the network from penalizing p2pool as much ?
17:43:26 <sech1> P2Pool payouts are 0 fee already
17:44:06 <sech1> or do you mean consolidations?
17:44:10 <m-relay> <s​trawberry:monero.social> I think he's talking about big consolidation tx fees because p2pool outputs are so small
17:44:27 <m-relay> <j​effro256:monero.social> yes but block reward is reduced when coinbase weight causes the block weight to go above the penalty free zone
17:44:58 <m-relay> <j​effro256:monero.social> more output = more weight = more penalty = less block reward
17:45:19 <m-relay> <s​trawberry:monero.social> is it possible to receive 2 coinbase outputs in same block by using p2pool?
17:45:22 <m-relay> <j​effro256:monero.social> not talking about consolidations atm
17:45:36 <m-relay> <j​effro256:monero.social> yes
17:45:38 <sech1> p2pool pays 1 output per wallet
17:46:12 <m-relay> <j​effro256:monero.social> u could just have 2 miner addresses, but only one per wallet
17:46:16 <sech1> I think it's better to have some compact format for coinbase consolidations
17:46:22 <sech1> it will save blockchain space as well
17:46:44 <m-relay> <s​trawberry:monero.social> so if you get multiple p2pool shares, you get 1 big output from it?
17:46:50 <sech1> yes
17:49:13 <m-relay> <s​trawberry:monero.social> maybe decrease the p2pool window for less consistent but larger outputs
17:49:50 <m-relay> <j​effro256:monero.social> the more you do that, the closer to solo mining you get in terms of UX, which is the whole reason why p2pool exists IMO
17:50:28 <m-relay> <s​trawberry:monero.social> yes its closer to solo mining, but some people are surely willing to make that tradeoff
17:50:53 <sech1> P2Pool main actually has smaller window right now
17:51:20 <sech1> PPLNS window = 373 blocks now
17:51:27 <sech1> It auto adjusts if hashrate gets too big
17:51:45 <sech1> min payout is 0.00153 XMR
17:51:57 <sech1> so people can already choose betwen p2pool main and p2pool mini
17:52:14 <m-relay> <j​effro256:monero.social> Does it adjust based on the mempool size / historical block size as compared to the penalty free zone ?
17:54:08 <sech1> No, it adjust to mine no more than ~2 Monero blocks per PPLNS window, so that each P2Pool share receives <= 2 payouts on average
17:54:25 <sech1> Before that it got ridiculous - P2Pool did more than 10 payouts per share
17:58:05 <m-relay> <s​trawberry:monero.social> while this would initially be an incentive to use p2pool, can't centralized pools also use it for cheaper payouts?
17:58:08 <m-relay> <j​effro256:monero.social> Maybe I'm misunderstanding the comment, but why would it limit the number of mined mainnet blocks? So it discards successfully mined blocks ? Surely not
17:58:27 <m-relay> <j​effro256:monero.social> Do you mean limiting the number of payouts per PPLNS ?
17:59:11 <m-relay> <j​effro256:monero.social> strawberry: yes
18:00:37 <m-relay> <s​trawberry:monero.social> then it benefits all miners at the expense of other users
18:01:07 <m-relay> <s​trawberry:monero.social> that being said, pools probably wouldn't go to the effort to implement that? or maybe I'm underestimating them
18:01:16 <sech1> jeffro256 it limits PPLNS window size to such size that it mines 2 Monero blocks per PPLNS window on average
18:01:31 <sech1> in other words, total difficulty of shares in PPLNS window = 2x Monero difficulty
18:02:21 <m-relay> <j​effro256:monero.social> ahhh okay
18:02:28 <m-relay> <j​effro256:monero.social> thanks for the info
20:06:44 <m-relay> <h​orixon:monero.social> i think the miner can set higher difficulty
20:07:36 <m-relay> <h​orixon:monero.social> maybe im confusing with centralized pools