Bitcoin Core waited to disclose three fixed security flaws
- Bitcoin Core disclosed details after fixes were available and the oldest affected release was no longer supported.
- A reorganization bug could leave miners unable to build block templates.
- Two other flaws weakened Tor privacy and could stall block downloads.
Bitcoin Core’s security contributors kept three vulnerabilities private while fixes were shipped to maintained releases. Antoine, a Bitcoin Core security contributor at Chaincode Labs, said details became public after the oldest affected branch, version 29, reached end of life. That coordinated process gives users time to install fixes before attackers can study the flaws.
The most serious bug could leave a node’s mempool inconsistent during a chain reorganization. The bug involved TRUC transactions: eviction removed a sibling transaction but left its descendants behind. Miners using an affected node could then fail to create block templates until restarting it. Niklas Kogger found the flaw with Fusamoto, a framework that tests Bitcoin Core through simulated network events, not with automated LLM scanning.
The other bugs threatened different parts of node operation. A whitelist setting could cause inbound Tor peers to be treated like local connections, weakening address-gossip privacy protections and denial-of-service limits. Antoine estimated about 5,000 reachable nodes were exposed. Another flaw let a peer send a malformed witness variant that cleared a node’s block-download state without providing a valid block, stalling processing for 10 minutes. Under tighter conditions, an attacker controlling three parallel-download peers could keep restarting the delay.
Antoine said reviewers initially rated the block-stall bug as low severity, then raised it to medium after recognizing that even one peer could stall a blocks-only node. He knew of no exploitation in the wild, and said major miners had upgraded; triggering the reorganization bug also required mining power. The fixes were shipped across supported Bitcoin Core releases.
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.
- 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.
Also discussed on this episode: (14)
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.
Safety (2)
- 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.
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.

