01:19:47 They say a tiger cannot change its stripes. 01:19:47 Does someone really just shut down a pool and never think about it again? 01:19:47 And take important code with them, never sharing it? To never return? Did they regret what they had done? 11:28:01 I don't understand mining pools 11:28:01 Do we combine all the CPU power to an algorithm or its individual CPU's trying to find the hash 11:28:01 So a lot of CPU's just increase probability of finding the hash hence payout is regular[... more lines follow, see https://mrelay.p2pool.observer/e/0Ymw-6gLNVZ3S1Zr ] 11:29:15 sounds to me like you get it, it's the second thing. I bunch of miners mining together but independently to get rewards more often. 11:30:30 Its a bunch of miners, mining individually to the pools address 11:31:31 The pool keeps track of each miners "work" (even if useless), and pays them proportionally (depeing on the payment wcheme. Pps, pplns, etc) 11:32:36 The work is tried hashes? Also prob keep track of all possible paths tried 11:33:11 The word is "shares" @ a difficulty, accumulated 11:33:16 the search space is too big for keeping track of guesses to be useful 11:34:10 So, pool sends jobs @ a difficulty, lets say 100k. you miner mines these low difficulty shares, and the pool coints them 100k * number of shares you mined 11:35:40 So, leta say you find one a minute for 10mins, that gives you "1M". This is your contribution / measurement of your portion of the total that the pool has counted across all users 15:45:22 What is the current security impact of #11276, if any? 15:52:34 I assume this is just a sort of defense-in-depth thing, but not totally sure 16:11:10 It is defense in depth. Currently the buffer overflow is unreachable but could be reached with a regression 16:23:20 Ah, that one. Both Claude and Codex got triggered by it all the time in my AI audits. It's not reachable in the current code.