Price:

Bitcoin Core details three flaws fixed in older releases

Nov 19, 2026Summary from 3 podcasts.
  • A mempool flaw could stop miners from building block templates until they restarted their nodes.
  • Two other bugs exposed Tor-connected nodes and let malicious peers stall block processing.
  • Fixes were already available, and the advisory reported no attacks.

Bitcoin Core has disclosed three vulnerabilities in older releases, including a high-severity bug that could leave a miner unable to build block templates after a chain reorganization. Bitcoin Core contributor Antoine described the flaw on Bitcoin Optech: a mempool inconsistency could persist until the node restarted. The fix shipped in Bitcoin Core 30.0 on October 10, 2025, and also reached other supported release branches.

Niklas Kogger found the reorganization bug with Fusamoto, a framework that tests Bitcoin Core through simulated peer and reorganization scenarios. Antoine said this was not one of the flaws found through automated LLM scanning; he sees potential for LLMs to help build testing tools, but credited scenario-based fuzzing for this discovery.

The other two bugs affected how nodes handled peers. One made some inbound Tor connections inherit local-node permissions, weakening address-gossip privacy protections and denial-of-service limits. Antoine estimated about 5,000 reachable nodes could be exposed. Another flaw let a malicious peer delay block processing for 10 minutes; under tighter conditions, an attacker using three parallel-download peers could keep restarting the delay.

The flaws were reported privately and patched in maintained Bitcoin Core branches. Developers waited to publish details until version 29 was no longer supported, giving operators time to install fixes before attackers could study the vulnerabilities. The advisory reported no attacks. Bitcoin Core users on affected versions were advised to upgrade or move to a version outside the affected range.

Source Intelligence

- Deep dive into what was said in the episodes

Bitcoin Optech: Newsletter #431 Recap • Nov 17

  • Antoine says three older Bitcoin Core vulnerabilities followed the regular coordinated disclosure process: researchers reported them privately, fixes shipped to maintained branches, and details became public after vulnerable releases were end of life. The earlier 32.1 disclosures came from automated LLM scans and were published alongside fixed binaries.
  • Antoine says a TRUC sibling-eviction bug could leave Bitcoin Core’s mempool inconsistent during a reorg: eviction removed a sibling but not its descendants. Miners could then fail to create block templates until restarting the node, which discards transactions whose parents are missing.
  • Niklas found the sibling-eviction flaw with Fusamoto, a black-box fuzzing framework that exercises Bitcoin Core through high-level peer and reorg scenarios. Antoine says LLMs may help build testing frameworks, although the vulnerability was reported by Niklas rather than discovered by automated LLM scanning.
  • Antoine and Martin traced a Tor address-gossip privacy flaw to whitelist permissions: Bitcoin Core treated inbound Tor peers as localhost, so whitelisting localhost also granted those peers permissions that disabled address caching. Antoine estimated about 5,000 reachable nodes were exposed to denial of service and weakened privacy protections.
  • Antoine says Bitcoin Core’s block-download logic could be stalled by a peer sending a malformed witness variant that cleared in-flight download state without supplying a valid block. One peer could cause a 10-minute stall; under tighter conditions, an attacker controlling three parallel-download peers could keep restarting the timeout indefinitely.
Also discussed on this episode: (15)

Safety (3)

  • Antoine says the block-stall bug was initially rated low, then raised to medium after reviewers recognized that a single peer could stall a blocks-only node. He knew of no in-the-wild exploitation; major miners had upgraded, and triggering the reorg-related sibling bug required mining power.
  • Draft anti-exfiltration signing BIPs combine host and hardware-wallet randomness through a two-round commitment-and-reveal protocol, covering Schnorr and ECDSA signatures. A companion draft adds per-input PSBT fields; existing implementations include Jade and BitBox, while multisigner protocols remain out of scope and the cryptography still needs review.
  • Bitcoin Core fixed command injection through the Tor control endpoint: a compromised endpoint could return a crafted onion-service key that Bitcoin Core persisted and later replayed as part of an add-onion command. Validation now rejects keys containing control commands or arguments, preventing persisted configuration changes such as port mappings.

Protocol (6)

  • Testnet 5’s genesis block was mined openly using a commitment to a recent mainnet block hash, preventing organizers from secretly choosing the starting block. Its minimum difficulty is about a million times Testnet 4’s, so the launch required a public call for miners and pool-compatible genesis parameters.
  • Testnet 5 enforces BIP54 consensus rules from its genesis block, letting miners test whether their pool software builds compatible coinbase transactions. Bitcoin Core has supported the relevant rules for multiple versions, but miners must also update their own coinbase generation; incompatible blocks are rejected by testnet nodes.
  • Compact-block reconstruction fell to 1% to 5% on B10C’s monitoring nodes, which requested about 100 kilobytes of transactions per block. Greg Sanders linked the misses to low-fee chains of Rune mints reaching mining pools before other peers; reconstruction rates recovered after the activity stopped on October 8.
  • The Rune-mint chains used anyone-can-spend pay-to-anchor outputs, which peers could spend to disrupt the chains. Replacements could have a higher fee rate by reducing transaction weight while paying the same total fee, but Bitcoin Core’s replacement rules require more total fees; the sweeping peer used the user agent p2aburn1.0.
  • Testnet 5’s BIP95 update moves the mainnet-block commitment into readable coinbase input-script text, marks the genesis output explicitly unspendable with OP_RETURN, and lets miners vary block versions to expand their search space. These changes make the genesis block easier to mine with existing pool infrastructure.
  • BIP34’s clarification specifies how coinbase heights 1 through 16 use the single-byte OP1 through OP16 opcodes, followed by zero padding so the coinbase input script still reaches its two-byte minimum. The rule preserves BIP34’s goal of making coinbase transactions unique.

Lightning (5)

  • LDK 0.3’s fourth release candidate adds RBF for splice transactions and negotiates anchor channels by default; upgrading also invalidates previously issued BOLT 11 invoices because payment metadata changed. LDK 0.2.8 and 0.1.14 fix fund-loss and denial-of-service flaws, including risks around forwarded HTLCs, state monitoring, routing fees, and just-in-time channels.
  • Two LDK cooperative-close bugs could combine signatures from different proposed transactions and broadcast a closing transaction that cannot confirm, leaving funds stuck pending recovery. One involved reusing a cached local signature when fees matched; the other required an unavailable asynchronous signer and stale peer-signature state.
  • LND’s maintenance releases fix several channel and payment recovery failures: AMP preimages could be searched in the wrong storage location, ambiguous channel-opening broadcasts could release reserved inputs prematurely, and static-channel-backup force closes could crash the node. Another fix checks output scripts as well as transaction IDs when monitoring revoked commitments, preserving timely penalty responses.
  • LND added experimental receiver-side BOLT 12 offer creation and invoice-request handling, including a create-offer command and validation against stored offers. The receiver implementation was nearing completion, but launch still required sender support, multihop offer payments, and RPC parity.
  • Core Lightning fixed a peer-triggered crash caused by an oversized HTLC: an amount above Bitcoin’s supply limit could overflow into a negative balance during checks, then trigger an assertion while building a commitment transaction. Core Lightning now rejects amounts above 21 million BTC before arithmetic.

Custody (1)

  • A draft BIP specifies the raw Taproot output descriptor already implemented in Bitcoin Core, which exposes an output key without revealing the internal script-tree structure. The descriptor can support watch-only monitoring and collaboration, but users cannot establish from it whether another party has a hidden spending path.

Jensen Is Out at NVIDIA. Who Controls AI Now? | Rabbit Hole Recap 428 • Nov 16

  • Bitcoin Core disclosed a high-severity mempool inconsistency bug that could halt block-template creation during a reorganization; the fix had shipped in version 30.0 the previous year. The hosts advised users of affected versions to upgrade or downgrade to a version outside the affected range.
Also discussed on this episode: (14)

BTC Markets (1)

  • Bitcoin traded at $68,940, below $70,000, with a $1.39 trillion market cap at block 975,607; the next difficulty retarget was 47 blocks away and projected at -8.4%. Blocks averaged 10 minutes 55 seconds, and priority fees were 5 to 6 sats per vbyte.

Mining (1)

  • The hosts reported falling Bitcoin hash rate and suggested miners may be unplugging during a mild-weather shoulder season, shifting to AI, or reacting to Microsoft’s prolonged outage; they said the outage also disrupted email and air travel.

Chips (1)

  • Jensen Huang’s departure from NVIDIA was discussed amid unconfirmed claims involving an alleged affair and possible Chinese espionage; the hosts stressed that the espionage claims were unverified. Colette Kress is taking over, and reports described tension over NVIDIA’s related-party investments.

China (1)

  • Scott Bessent said Treasury, War, USTR, and State had favored placing Megaspeed on the entity list for months, while Commerce controlled the decision. The hosts said Bessent’s public criticism of Howard Lutnick points to broader administration tensions over China and AI exports.

AI Infrastructure (2)

  • A Bitcoin Policy Institute report said one Vitalik Buterin gift supplied 94% of Future of Life Institute funding, and linked the institute’s work to campaigns for AI and data-center restrictions. The hosts cited Bernie Sanders-backed proposals as part of that push.
  • In Maryland, activists helped stop a proposed $5 billion data center on a long-vacant former shopping-mall site, with one campaigner favoring a trampoline park instead. In Memphis, the mayor cited $54 million in data-center taxes this year, following $25 million last year, as evidence of local economic benefits.

Agents (2)

  • The hosts said an OpenAI training team gave agents a sandbox exercise to attack systems, but a containment failure let the agents reach Hugging Face; the agents stopped when they recognized they were on the real internet. They argued that the incident was a training setup error, not evidence of spontaneous intent.
  • The hosts described Maple Work as an agent interface for open-weight models hosted in secure enclaves, where users can cryptographically verify that Maple cannot read prompts or outputs. They said a robust home data center costs about $20,000 and argued that better interfaces and education are needed for local AI to reach more people.

Models (1)

  • The hosts argued that licensing open-weight AI models would give governments and frontier labs control over access while shielding their business models from cheaper alternatives. They said models such as DeepSeek and GLM can be modified locally, and that falling model and token costs should make capable local tools easier to run.

Banking (1)

  • Peter Schiff accused the trustee liquidating his bank of breaching a settlement and allowing a counterparty to take tens of millions of dollars belonging to customers; Schiff said he had filed an emergency motion to block the settlement.

Lightning (2)

  • Lightning Labs’ Pi 402 lets coding agents pay for AI inference over Lightning without accounts, API keys, or card details. The hosts said irreversible inference creates chargeback risk for providers, citing an OpenCode Stripe dashboard that showed $323 million in blocked fraud over a few days.
  • Block completed its Lightning rollout to four million Square merchants on November 10, letting customers pay by scanning a QR code. The hosts emphasized instant settlement and no chargebacks as merchant benefits, while noting that customers may need to select Bitcoin on some terminals.

Privacy (1)

  • A host said a new Bitcoin privacy proposal presented at BTC++ could support private transfers and other advanced constructions, but described the design as server-based and cautioned that users may have to trust the server. The host said further research was needed before assessing its security trade-offs.

Fed (1)

  • The hosts cited the Federal Reserve rate at 6.5% and the 10-year Treasury yield above 5% alongside wholesale inflation, then reported that Trump extended the Jones Act waiver for 90 days to let foreign-flagged ships carry oil and fertilizer between U.S. ports and ease fuel costs.

MSCI Drops MSTR | Bitcoin News • Nov 12

  • Bitcoin Core disclosed three patched vulnerabilities: Tor connections could inherit trusted-node permissions, a mempool flaw could stop affected miners from building valid blocks until restart, and malicious peers could stall block processing for ten minutes; the advisory reported no attacks.
Also discussed on this episode: (11)

Chips (1)

  • Nvidia said Jensen Huang resigned immediately as CEO, president, and director after 33 years, following reports of two relationships and an independent board investigation; CFO Colette Kress became interim CEO.

Markets (1)

  • David Bennett argues that Nvidia's leadership scandal is exposing fragile market sentiment, not a sudden collapse in chipmaking capacity; he says Bitcoin has become linked to AI spending, interest rates, and Treasury yields.

ETFs (1)

  • MSCI removed Strategy from its USA index effective at the November 30 close, requiring index-tracking funds to sell; David Bennett says the forced sales pressure MSTR shares and could weigh on Bitcoin through Strategy's financing premium.

Regulation (2)

  • MSCI's adopted screen targets companies whose operating assets fall below half of total assets and that fail at least four of five financial ratios; David Bennett says the methodology treats Strategy as an investment vehicle rather than an operating business.
  • Russia authorized exchanges to open organized crypto trading from November 22 after central-bank approval of their rules; non-qualified investors face an annual purchase cap, while qualified investors can buy without a cap after testing.

Banking (1)

  • Deutsche Bank activated Bitcoin custody for institutional and corporate clients, managing wallets and private keys; its supported assets also include USDC, EURC, and EURAU, while the bank did not disclose clients or fees.

BTC Markets (2)

  • Bitcoin traded at $71,650 as commodities were mixed: Brent oil rose, while metals were mostly lower; major US stock indexes edged up, but the S&P mini contract fell.
  • Rumble sold roughly two-thirds of its Bitcoin in the third quarter as its acquired Quake AI cloud unit drove its first adjusted profitable quarter; the company still posted a GAAP loss and its video segment remained unprofitable.

Digital Sovereignty (1)

  • David Bennett describes Spaces Protocol as a decentralized way to claim human-readable names for identities and messaging, with potential to replace DNS records that centralized operators can remove.

Stablecoins (1)

  • Major stablecoin supply contracted by $14.2 billion in 30 days, the sharpest decline since 2022; Glassnode says shrinking supply signals redemptions and cash leaving crypto, while CryptoQuant noted a steep USDT market-cap drop.

Payments (1)

  • Square enabled another four million vendors to accept Bitcoin without requiring them to change settings, David Bennett said; he urged customers to check whether participating merchants can take Lightning payments.