12:43:05 <m-relay> <x​fedex:matrix.org> Does the Docker Build generate reproducible binaries?
12:46:58 <selsta> no
12:47:13 <selsta> or which dockerfile?
12:48:01 <selsta> everything in here should produce reproducible builds: https://github.com/monero-project/monero/tree/master/contrib/gitian
12:48:40 <selsta> this dockerfile is not made for reproducible builds: https://github.com/monero-project/monero/blob/master/Dockerfile
21:18:52 <m-relay> <c​harutocafe:matrix.org> have 1 minute blocks been reconsidered since monero went from 1 minute to 2 minute blocks? i believe one of the main reasons was due to block overhead and many more empty blocks, nowadays since the network is so active that argument doesn't seem to make much sense.
21:19:29 <m-relay> <c​harutocafe:matrix.org> one of the main reasons for the change, i mean
21:23:05 <tevador> the main reason was to reduce the orphan rate
21:25:35 <m-relay> <c​harutocafe:matrix.org> assuming p2pool had more than 90% of the monero network hashrate, would that still be as impactful?
21:27:07 <m-relay> <c​harutocafe:matrix.org> as in, would the orphan rate from reducing the block time increase in the same manner? i have the idea that it woudn't.
21:28:00 <tevador> yes, two p2p miners could still find blocks simultaneously and part of the network hashrate would be wasted
21:35:09 <m-relay> <c​harutocafe:matrix.org> but wouldn't that be less common since all miners would be mining in the same "pool" and the moment one miner finds a new block, almost instantly the pool sends new work to the miners? while in the current multi-pool scenario, one pool could take a long time to realize that a miner from a different pool found a block because they might not be direct peers.
21:35:47 <m-relay> <c​harutocafe:matrix.org> perhaps i misunderstand how p2pool and pool mining in general works
21:36:39 <m-relay> <c​harutocafe:matrix.org> but i always had the idea that large pools generally had much less orphan rates than smaller pools
22:01:51 <tevador> Block propagation is never instant. There is always some short window when everyone is mining a stale block.
22:03:40 <m-relay> <o​frnxmr:monero.social> Their nodes handle more connections and propagate faster.
22:03:40 <m-relay> <o​frnxmr:monero.social> p2pool doesn't connect to everyone like a centralnserver. Its p2p
22:04:32 <m-relay> <o​frnxmr:monero.social> P2pool has orphans of its own.
22:07:01 <tevador> One way to deal with orphans is to add the difficulty of uncle blocks to the chainwork. This way, no hashes are wasted. Even ethereum got it wrong and could have been ~40% attacked when it was still PoW.