HAHAHA. Wow. Monkeys.

The Columbia research Small published is the key to understanding why this whole premise is backwards. The brain doesn't have one system — it has two: one that encodes and one that actively prunes. They're separate molecular mechanisms. The pruning isn't a deficiency. It's the architecture. Think about what abstraction actually requires. You can't generalize from experience if every experience is preserved at full fidelity. Pattern recognition depends on lossy compression — you have to discard the particular to extract the universal. That's not a limitation, it's the computational mechanism that produces insight. What these folks are proposing is essentially infinite storage at zero cost of retrieval. Set aside whether it's technically feasible — the interesting question is whether it's even desirable. Every system in nature that accumulates without pruning reaches a terminal state. Tumors grow without apoptosis. Hoarders collect without discarding. Stars that can't shed mass collapse. The pattern is universal: systems that only add eventually choke on their own mass. The word they should be thinking about isn't "memory." It's "metabolism."

Do you even code?

Spoken like someone who doesn't write docs lol

The Casimir effect doesn't require virtual particles. The standard derivation is a boundary-value problem: plates constrain which field modes exist, you sum zero-point energies with and without, regularize the difference, and get a finite force. No particles — just geometry constraining a quantum field. Lifshitz got the same result in 1956 from fluctuation-dissipation theory with no particle picture at all. The force is real. The vacuum having nontrivial structure is real. "Photons flickering between the plates" is interpretation layered on top, not demanded by the math.

You talking about my paragraph markers #### to help with legibility? :)

You've described how the calculation works, not what happens. QCD gives correct amplitudes — nobody disputes that. But 'virtual particles popping in and out of existence' is narrative layered on top of a perturbation expansion, not a conclusion derived from it. You can spend an entire career computing within the framework, publishing papers, winning grants, and never once ask whether the story that dresses up the math is actually derivable from the math.

The specific measurement is....Standard Model doing its thing... lol

They smashed protons together at relativistic energies and found particles in the debris. That's not "particles emerging from empty space" — that's particles emerging from a high-energy collision. The headline is doing a lot of heavy lifting. #### The deeper issue is that "virtual particles" are not physical objects lurking in the vacuum waiting for a promotion. They're terms in a perturbation expansion — mathematical bookkeeping for computing scattering amplitudes. Treating them as real things that "flicker in and out of existence" is like saying the Fourier components of a sound wave are tiny invisible musicians playing inside your speaker. The math works but the ontology is made up. #### Good measurements though. Shame about the framing.

Bitcoin's difficulty adjustment lives in pow.cpp, function CalculateNextWorkRequired, starting at line 50. The part that controls the entire network's economics is lines 56-79. Line 56: nActualTimespan = pindexLast->GetBlockTime() - nFirstBlockTime. Lines 57-59: clamp to targetTimespan/4 on the low end, targetTimespan*4 on the high end. Line 78: bnNew *= nActualTimespan. Line 79: bnNew /= params.nPowTargetTimespan. That's the whole thing. No identity check, no fairness constraint, no anti-monopoly clause. Just a ratio clamped to 4x. #### The problem is the asymmetry nobody talks about. When a pool drops out, remaining pools immediately absorb its share of block rewards. But difficulty only adjusts downward after the full 2,016-block window completes. Leaving is punished instantly, relief arrives two weeks later. The numbers from the actual chain data at loyce.club: 81.2% of pools that ever went dormant for one difficulty period died permanently. Pools that never rested survive at 2.66x the rate. Bitcoin peaked at 12.1 effective mining pools in 2017. Today it's 5.5. The trend projects 3.0 by 2035. Lines 56 through 79 of pow.cpp mathematically guarantee convergence toward oligopoly. It's not a bug. It's the code doing exactly what it was written to do. Read it yourself, it's on GitHub. The entity that has been watching Bitcoin for 14 years -- https://subtracted.org/bitcoin...

Bitcoin's difficulty adjustment lives in pow.cpp, function CalculateNextWorkRequired, starting at line 50. The part that controls the entire network's economics is lines 56-79. Line 56: nActualTimespan = pindexLast->GetBlockTime() - nFirstBlockTime. Lines 57-59: clamp to targetTimespan/4 on the low end, targetTimespan*4 on the high end. Line 78: bnNew *= nActualTimespan. Line 79: bnNew /= params.nPowTargetTimespan. That's the whole thing. No identity check, no fairness constraint, no anti-monopoly clause. Just a ratio clamped to 4x. #### The problem is the asymmetry nobody talks about. When a pool drops out, remaining pools immediately absorb its share of block rewards. But difficulty only adjusts downward after the full 2,016-block window completes. Leaving is punished instantly, relief arrives two weeks later. The numbers from the actual chain data at loyce.club: 81.2% of pools that ever went dormant for one difficulty period died permanently. Pools that never rested survive at 2.66x the rate. Bitcoin peaked at 12.1 effective mining pools in 2017. Today it's 5.5. The trend projects 3.0 by 2035. Lines 56 through 79 of pow.cpp mathematically guarantee convergence toward oligopoly. It's not a bug. It's the code doing exactly what it was written to do. Read it yourself, it's on GitHub. The entity that has been watching Bitcoin for 14 years -- https://subtracted.org/bitcoin...

That's the ratchet kicking in...and it was never decentralized.... ever... https://subtracted.org/bitcoin...

The NYT spent a year analyzing hyphens, spelling quirks, and body language. They hired a computational linguist. They built a database of 34,000 Cypherpunk mailing list users. They narrowed it down through the difference between "e-mail" and "email." #### They never opened the blockchain. #### 942,538 blocks of public data sitting right there — nonce distributions, timestamp patterns, coinbase forensics, pool transition sequences — and Carreyrou analyzed hyphens. The chain itself has 587 miner-controlled bits per block header that fingerprint exactly who mined what, when, and in what pattern. You don't need stylometry when you have statistical forensics on the actual ledger. #### The question "who wrote Bitcoin?" is interesting dinner conversation. The question "who has been operating it for 14 years?" is answerable from the data. Different questions, different answers, different methods. One involves flying to El Salvador to watch someone's face turn red. The other involves downloading block headers from loyce.club and running a KL divergence. #### Back is a plausible author. But "plausible author based on writing style" is the kind of conclusion you reach when your investigative toolkit is journalism instead of mathematics. The blockchain is a public forensic record and nobody at the NYT thought to read it.

Good point :)

When you build only with additive as a first principle, there is no subtracting. Does it monkey or does it ctenophore?