drumr_ retweeted
Yellow has had enough of “Big Bitcoin”, “in control”, Bugle shitting on pleb culture, and Gen Z irony watering everything out.
“We gotta go back”
“Fuck your only NGU perspectives. Fuck your Big Bitcoin.”
“I am a pleb. I will remain a pleb. If that makes me uncool, fuck you too.”
drumr_ retweeted
Bitcoin Core just disclosed CVE-2025-62861, rated High severity: after a reorg, miners on 28.0 to 29.1 could be left unable to build valid blocks, and Core says it could be exploited. Fixed Oct 2025, disclosed now per policy.
The bug lived in TRUC (BIP 431), the mempool policy Gloria Zhao (glozow) proposed and championed, specifically inside the sibling-eviction logic she wrote in PR #29306.
Zhao went from a cold email by Chaincode's Adam Jonas in January 2020 to Brink's first fellow that December and to maintainer over mempool policy by July 2022. The area she was given primary authority over is where the bug lived.
The decisive ACKs and the merge came from the same informal network the CAPTURE series documents: Suhas Daftuar (Chaincode co-founder), Ava Chow (who backed Zhao's maintainership and merged the PR), and Greg Sanders (who later wrote the OP_RETURN uncap Zhao merged).
Nobody caught this bug, inside the network or out. But when social credit and authority are routed away from independent reviewers, and the same few people design, approve, merge and fix, there are fewer chances to catch the next one. TRUC added another layer of rules and exceptions so Lightning-style protocols can fee-bump more easily. Complexity for extra use cases is not free.
The CAPTURE series documents how an informal network of Chaincode Labs and Brink funders and organizers, including John Newbery and Adam Jonas, selectively funded and elevated certain developers, most notably Zhao, while grants, review attention and social credit were routed away from more experienced independent contributors such as Luke Dashjr, Vasil Dimov and Jon Atack.
Those decisions concentrated authority in a small overlapping group, which later exercised it in the policy changes culminating in the OP_RETURN uncap.
citadel21.com/the-network
citadel21.com/the-lever
citadel21.com/the-merge
A new high severity advisory has been posted: bitcoincore.org/en/2026/11/1…
drumr_ retweeted
Replying to @btc_boomers @LawrenceLepard
The most powerful computer network in the world controlled by 2 mining pools, coercible by governments or Saylor-Black rock level suits. Woke dishonest devs. A pleb army neutered by nodes that don't matter and admonished by the cult-leaders who are really paid-off influencers who can't afford the sponsorship loss, let alone the social cost, of maintaining a backbone. Yeah this is all going swimmingly. You all became the very thing we sought to destroy. Congrats. AND YOU KNOW IT IN YOUR BONES, but none of you are intellectually honest enough to admit it.
drumr_ retweeted
CAPTURE Part 4: THE MACHINE
The fourth and final installment is out.
Bitcoin Magazine wasn’t just covering the fight over Bitcoin’s future. Its parent operated an Ordinals trading desk, invested in businesses tied to the ecosystem, and maintained editorial policies that exempted parts of that same business.
Then came an $80,000/month marketing contract, with an option for Nakamoto Inc. to buy BTC Inc at a valuation tied to its earnings, in a window that included the OP_RETURN fight. Nakamoto exercised the option.
Readers were not consistently told about these commercial relationships.
A documented investigation into the commercial interests and media infrastructure surrounding the Bitcoin Core controversy.
citadel21.com/the-machine
drumr_ retweeted
Replying to @dotkrueger
IMO more Bitcoiners should spend more time on understanding that if "digital credit" is developed it will ensure BTC never goes to $1m
That may even be the point of "digital credit."
But Bitcoiners would be well-served to study "credit gold" that began in London in mid-80s
drumr_ retweeted
Think about the COLDCARD disaster.
Now read and listen to this.
(10 years ago) Paul Rosenberg, OG Cypherpunk describes how the NSA operates behind the scenes, as appears in Snowden’s documents:
NSA guys knocks on your door.
“We want you to weaken your hash for creating the cryptographic key!”
Source below.
drumr_ retweeted
Bitcoin Core has shipped one consensus change in the last nine years, and it broke. Taproot activated in 2021, and within 13 months people were using it to stuff arbitrary data into the chain in a way nobody designed for and nobody agreed to. Every attempt to fix that has been rejected or closed, and the one policy constraint that was slowing it down got removed over broad opposition, spurring a significant portion of node runners to abandon Core entirely and rally behind a competing implementation.
Meanwhile CTV and BIP-54 have both been sitting for seven years, one trying to add functionality and the other trying to fix bugs that have existed since the beginning. Neither has really moved. And now the same people who shipped a consensus change they did not understand, and refused to clean up after, want to change consensus again.
Taproot's consequences came as a surprise because the Bitcoin consensus protocol has never been formally specified. A BIP describes what it intends to do, but it gets layered on top of a protocol that nobody has ever fully written down. When you change something you have not fully characterized, you cannot know what you are actually changing. That is how unintended behavior makes it to mainnet, and it is why the same thing can happen again.
I am not against changing Bitcoin. I am against changing Bitcoin blind. Before anyone earns the right to change consensus again, they need to demonstrate two things: that they know how to make consensus changes safely, and that they are willing to fix their mistakes when those changes go wrong. That means a formal specification of the entire existing consensus protocol, formal verification of any proposed change against that specification, and differential testing against independent implementations before anything ships. Alternative implementations exist. What does not exist is any process that treats them as a mandatory check on Core before a consensus change goes live.
The bar for changing the monetary base layer of human civilization is not vibes and rough consensus. Build the infrastructure to do this right, or stop asking.
drumr_ retweeted
“Bitcoin is an app. What is that app? It's money. It's open, borderless, permissionless money. Stop trying to make it do more.”
@_MattHill_ of @start9labs explains Bitcoin Core's desire to turn Bitcoin into Ethereum.
Replying to @mattkratter
@mattkratter a month ago:
"It's easy to foresee a long-range attack that includes rugging a lot of Bitcoiners ... by a close-source secure chip, or even a random number generator that's not producing truly random private keys ..."
Why haven't the voices sounding the alarms about NVK and Coldcard for months or even years—like Matt, @sesi_the_man, @zherbert, and many others—received wider attention and coverage?
Because they're not part of "the club".
Replying to @americanhodl8
Coldcard's "sleep at night technology" entropy.
drumr_ retweeted
Replying to @enur72
Arbitrary data is noise in the monetary system. It reduces the quality of the money. It obscures the communication system of human needs which is the ultimate function of money. It’s a disgrace
Replying to @saylor
Guy from the 2020 class who built a company based on paper Bitcoin and derivative products as money instead of Bitcoin, doesn't self-custody his own coins or run a node, now telling OGs that they just heard of Bitcoin and shouldn't have an opinion about it.
This is next level.






















