Price:

BITCOIN

Jeremy Rubin says Blockstream gatekeeping stalls Bitcoin innovation

Wednesday, May 6, 2026 · from 3 podcasts, 4 episodes
TFTCBitcoin Takeover PodcastBitcoin Optech
  • Independent developers argue corporate interests at Blockstream stifle Bitcoin's evolution by sidelining key upgrades like CheckTemplateVerify.
  • Builders face a choice: compromise by building on centralized platforms or migrate their work to rival chains like Bitcoin Cash.
  • Peripheral work on quantum recovery and formal protocol rules advances while core governance remains gridlocked.

Bitcoin’s most straightforward scaling upgrade has been stuck for seven years, and developer Jeremy Rubin says the bottleneck isn’t technical - it’s social. On the Bitcoin Takeover Podcast, Rubin argues CheckTemplateVerify (CTV) failed because of a “paternalistic” dynamic where critics demanded an ever-shifting definition of “technical consensus.” He points to a 2022 Telegram exchange where key figures like Adam Back allegedly used FUD to demoralize supporters, despite backing from about 150 developers and researchers.

“The 2022 CTV activation effort failed due to paternalistic arguments about 'technical consensus' and targeted FUD, including a two-hour Andreas Antonopoulos podcast framing covenants as a government censorship tool.”

- Jeremy Rubin, Bitcoin Takeover Podcast

Rubin attributes this stagnation to a cultural hegemony. He argues Blockstream, a major Bitcoin infrastructure company, operates with an assumption of inherent technical supremacy, viewing outside innovation as a threat. Instead of supporting independent proposals like CTV, Rubin says Blockstream engineers proposed alternative paths that stalled progress for years, centralizing influence over a protocol built on decentralization.

The result is a builder’s dilemma. Without native on-chain primitives like covenants, engineers who want to create trust-minimized tools are forced onto centralized platforms or rival chains. Rubin warns this brain drain undermines Bitcoin’s cypherpunk mission, pushing talent toward environments like Bitcoin Cash or upcoming forks where they can actually ship code.

While core development is gridlocked, peripheral innovation continues. The Bitcoin Optech newsletters detail independent work on a zero-knowledge proof system for quantum emergency recovery and Toby Sharp’s project to codify Bitcoin’s consensus rules into 34 formal, semantic specifications. This work aims to break the cycle of relying solely on Bitcoin Core’s code as the de facto protocol, enabling true client diversity.

Meanwhile, the regulatory climate adds pressure. On TFTC, Marty Bent and Lauren Rodriguez detailed the criminal prosecution of Samourai Wallet developers, arguing it sets a precedent that holds developers liable for user actions. This legal threat further chills the environment for building privacy-preserving tools on Bitcoin.

Rubin is now working on Char, a decentralized staking protocol for Bitcoin layer 2s. He views such layer-2 research as a source of momentum, but the fundamental tension remains: Bitcoin’s social layer is proving harder to upgrade than its code.

“He observes a cultural antagonism towards Bitcoin being useful, where criticizing Ethereum is prioritized over evaluating positive technology progress within Bitcoin itself.”

- Jeremy Rubin, Bitcoin Takeover Podcast

#Protocol#Payments#Custody
Andreas M. AntonopoulosMarty BentBlockstreamBitcoinBitcoin CoreEthereum

Source Intelligence

- Deep dive into what was said in the episodes

TFTC: A Bitcoin Podcast
TFTC: A Bitcoin Podcast

Marty Bent

#742: Why Privacy Is Non-Negotiable with Lauren Rodriguez • May 6

  • Lauren Rodriguez says her husband, Samurai Wallet co-founder Keone, is unjustly imprisoned, and their lives were upended by a DOJ raid with no prior contact or warning.
  • The government charged Keone and co-defendant Bill with conspiracy to operate an unlicensed money transmitter business and conspiracy to money launder, despite FinCEN guidance indicating they were not in violation.
  • Rodriguez argues the case sets a dangerous precedent that developers are liable for user actions, equating it to holding messaging app creators responsible if criminals use their software.
  • Marty Bent asserts financial privacy is a prerequisite for freedom, citing that tools like Samurai Wallet restore basic transactional privacy lost in Bitcoin's transparent ledger.
  • Bent and Rodriguez warn that without privacy, Bitcoin becomes a perfect panopticon, creating physical security risks like the public target lists for Bitcoin holders in France.
  • Marty Bent cites a 2024 crypto brief where the administration seeks to expand the Patriot Act to include digital currencies, which would require impossible KYC/AML compliance for open-source software.
  • Marty Bent warns of a regulatory slippery slope, noting the Bank Secrecy Act's $10,000 reporting threshold from 1970 is equivalent to nearly $70,000 today due to currency devaluation.
Also from this episode: (4)

Censorship (1)

  • Rodriguez says the DOJ's forfeiture of Samurai's website led to scammers recreating it, creating real victims where the original service had none.

Politics (1)

  • Rodriguez calls for a presidential pardon and public pressure, directing listeners to billandkeone.org to sign petitions and donate towards their $2 million in legal debt.

Regulation (1)

  • Bent argues that existing KYC/AML laws are ineffective, citing data that they prevent only a tiny fraction of illicit funds while creating massive data breach risks.

Privacy (1)

  • Rodriguez connects the attack on financial privacy tools to a broader erosion of rights, using the analogy of blinds on windows and locks on doors as fundamental privacy norms.
#Regulation#Open Source#Digital Sovereignty#BTC Markets#Censorship
Bitcoin Takeover Podcast
Bitcoin Takeover Podcast

S17 E22: Jeremy Rubin on CTV, Char & Building on Bitcoin • May 6

  • Jeremy Rubin describes CTV (Check Template Verify) as a fundamental, straightforward enhancement enabling Bitcoin to be used in the context people need.
  • A core CTV use case is congestion management. A platform like Coinbase could issue verifiable certified checks for withdrawals, bypassing months of transaction backlog with a single transaction.
  • CTV enables self-custody vaults. One example is a vacation wallet where triggered withdrawals take a month, allowing time to cancel if a theft is detected during travel.
  • Rubin says the 2022 CTV activation effort failed due to paternalistic arguments about 'technical consensus' and targeted FUD, including a two-hour Andreas Antonopoulos podcast framing covenants as a government censorship tool.
  • Rubin attributes opposition partly to social dynamics, not technical flaws. He cites the UTXOS.org signals page showing support from around 150 developers, businesses, and researchers.
  • Rubin states Blockstream provides positive contributions but views itself as having inherent technical supremacy over other Bitcoin developer groups.
  • Rubin argues that Bitcoin's lack of on-chain primitives pushes development to centralized platforms, contrasting with Ethereum's ability to host decentralized applications like Uniswap.
  • He observes a cultural antagonism towards Bitcoin being useful, where criticizing Ethereum is prioritized over evaluating positive technology progress within Bitcoin itself.
  • Rubin says the current Bitcoin design forces capable engineers to compromise their values, accepting federations or forks because they cannot ship their desired trust-minimized tools on the base layer.
  • Rubin is working on Char, a decentralized staking and sequencer protocol for Bitcoin layer 2s that uses slashed Bitcoin to enforce honest behavior and enable fast pre-commitments.
  • He views Proof of Stake as a neutral technology. In Char, creating a conflict causes you to lose Bitcoin, connecting economic security back to Bitcoin's proof-of-work.
  • Rubin rejects building on Bitcoin Cash or eCash just to prove CTV works, arguing the goal is to build on Bitcoin itself to keep it a socially relevant project.
  • On Paul Sztorc's eCash fork, Rubin disagrees with the path but acknowledges Sztorc's good intentions and frustration at failing to achieve his goals within Bitcoin.
  • Rubin sees excitement in layer 2 research like BitVM and ZeroSync, citing breakthroughs like Robin Linus's BinoHash for quantum-resistant signatures as momentum-building.
#Protocol#Adoption
Bitcoin Optech
Bitcoin Optech

Bitcoin Optech: Newsletter #403 Recap • May 6

  • Lalo implemented a zero-knowledge proof system using RISC-Zero to allow recovery of Bitcoin if SECP256K1 is broken. It proves a user holds the BIP32 seed corresponding to a spent public key.
  • Lalo's initial proof was 1.6-1.8 MB, but optimizations reduced it to 600 KB and then to 200 KB using succinct receipts. Verification takes milliseconds.
  • The proof system could enable batch aggregation for blockchain use, creating a single succinct proof for many claims, similar to a UTXO commitment.
  • Chava Pursky proposed binary fuse filters as a faster alternative to BIP-158's GCS filters. Benchmarks show a 6-45x speed-up on ARM and 9-80x on desktop with a 0-3% bandwidth increase.
  • Binary fuse filters have a higher false positive rate of ~1 in 65,000 compared to GCS's ~1 in 200,000. A key concern is ensuring deterministic filter construction.
  • Brandon Black and Lalo noted hierarchical filters spanning multiple blocks could be a better research direction to reduce total bandwidth for mobile clients using compact block filters.
  • A Conduition proposal describes post-quantum HD wallets that combine SECP256K1 and SPHINCS keys. SPHINCS keys don't change after the last hardened level, but this is acceptable for sweeping a wallet after a quantum break.
  • Brandon Black argues a pure post-quantum output type like BIP 360 is preferable to a Taproot V2 that disables key spends, as no user needs both a cheap key spend today and a disabled key spend later.
  • Daniel Buckner proposed defining specific post-quantum key type prefixes for use with Taproot's unknown key types, allowing scripts to commit to future PQ schemes today.
  • A demonstration on Signet showed BIP54 is needed. Attack blocks exploiting old script bugs took over a minute to validate, highlighting risks in a centralized mining environment.
  • Bitcoin Core #33671 adds a 'non-mempool' field to `getbalances` RPC, exposing balances from transactions not in mempool or blockchain, fixing accounting for stuck or non-standard transactions.
  • Bitcoin Core #34911 removes deprecated RBF fields from mempool RPCs as full RBF is now default. The fields can be restored with the deprecated RPC config option.
  • BIP 391 for binary output descriptors was closed after BIP 393 was proposed as a superior method for wallet descriptor annotations and recovery hints.
  • BDK #2188 fixes a security issue where the library would accept any transaction from an Electrum server without verifying it matched the requested transaction ID.
#Protocol#Mining#Privacy

Bitcoin Optech: Newsletter #402 Recap • May 1

  • Toby Sharp's Hornet Node project has defined 34 formal semantic rules that describe Bitcoin's non-script block validation logic, such as header difficulty and block weight limits.
  • Sharp argues Bitcoin can achieve client diversity by formally specifying all consensus rules, instead of relying solely on Bitcoin Core's code as the de facto protocol.
  • Sharp's specification includes both an English description and a pure function for each rule, with the goal of creating a domain-specific language for formal verification.
  • Gustavo notes all four major Lightning implementations now support Onion Messages and Bolt 12, making discussions about jamming protections timely.
  • Bitcoin Core 31's default UTXO database cache increased to 1024 MiB on systems with at least 4096 MB of RAM, up from 450 MiB.
  • Bitcoin Core 31 implemented the cluster mempool redesign and private broadcast via short-lived Tor or I2P connections.
  • A Bitcoin Core PR changed the `dumpTXOutset` RPC to create snapshots using a temporary UTXO database, allowing nodes to stay in sync with the network instead of rolling back the main chain.
  • BIP 361 is a two-phase abstract proposal to prohibit sending funds to quantum-vulnerable addresses after a post-quantum signature scheme is deployed.
  • Marc argues against funding quantum computer development through lost coins, noting approximately a third of all Bitcoin would be vulnerable to a long-range attack.
  • LND fixed a bug where expired blinded payment paths were forwarded into the blinded segment instead of being rejected at the introduction node.
  • LND implemented per-peer and global token bucket rate limits for incoming Onion Messages, mirroring earlier work for gossip message rate limiting.
Also from this episode: (3)

Lightning (3)

  • Lightning Network Onion Messages are vulnerable to jamming attacks because Bolt 4 does not specify size or rate limits, allowing flooding across any peer-to-peer connection.
  • Proposed mitigations for Onion Message jamming include upfront fees, bandwidth-metered payments, hop limits, proof-of-work puzzles, and backpropagation-based rate limiting.
  • Core Lightning v26.04.1 enabled splicing by default and added `splice` and `splice-out` commands, following the merger of the splicing proposal into the Bolt specification.
#Protocol#Lightning#Adoption#Privacy

Related Stories