-
br-m<isaac_newton:matrix.org> They say a tiger cannot change its stripes.
-
br-m<isaac_newton:matrix.org> Does someone really just shut down a pool and never think about it again?
-
br-m<isaac_newton:matrix.org> And take important code with them, never sharing it? To never return? Did they regret what they had done?
-
br-m<routingerror:metropolis.nexus> I don't understand mining pools
-
br-m<routingerror:metropolis.nexus> Do we combine all the CPU power to an algorithm or its individual CPU's trying to find the hash
-
br-m<routingerror:metropolis.nexus> So a lot of CPU's just increase probability of finding the hash hence payout is regular[... more lines follow, see mrelay.p2pool.observer/e/0Ymw-6gLNVZ3S1Zr ]
-
br-m<monero.arbo:matrix.org> 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.
-
br-m<ofrnxmr:xmr.mx> Its a bunch of miners, mining individually to the pools address
-
br-m<ofrnxmr:xmr.mx> The pool keeps track of each miners "work" (even if useless), and pays them proportionally (depeing on the payment wcheme. Pps, pplns, etc)
-
br-m<routingerror:metropolis.nexus> The work is tried hashes? Also prob keep track of all possible paths tried
-
br-m<ofrnxmr:xmr.mx> The word is "shares" @ a difficulty, accumulated
-
br-m<monero.arbo:matrix.org> the search space is too big for keeping track of guesses to be useful
-
br-m<ofrnxmr:xmr.mx> 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
-
br-m<ofrnxmr:xmr.mx> 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
-
br-m<jpk68:matrix.org> What is the current security impact of #11276, if any?
-
br-m<jpk68:matrix.org> I assume this is just a sort of defense-in-depth thing, but not totally sure
-
br-m<ack-j:matrix.org> It is defense in depth. Currently the buffer overflow is unreachable but could be reached with a regression
-
sech1Ah, 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.