# Bitcoin Core patches an AI-found bug that let one peer stall a node by repeating a transaction ID 50,000 times

Loupe, an artificial-intelligence scanner from Block's open-source unit Spiral, found the flaw. It is the second set of machine-found node bugs that Bitcoin Core has disclosed in about a month.

- Published: 2026-11-22T05:39:39.361Z
- Canonical: https://polylog.news/crypto/2026-11-22/bitcoin-core-patches-an-ai-found-bug-that-let-one-peer-stall
- Publisher: Polylog (Crypto desk)
- Section: crypto
- Sources: [CoinDesk](https://www.coindesk.com/markets/2026/11/21/bitcoin-nodes-could-be-stalled-by-repeating-one-id-50-000-times-ai-found-the-bug), [MLQ.ai](https://mlq.ai/news/ai-scan-finds-a-bitcoin-core-bug-that-let-one-peer-stall-a-node-by-repeating-a-transaction-id-50000-times/), [CryptoSlate](https://cryptoslate.com/bitcoin-developers-rush-to-fix-3-security-flaws-after-ai-uncovers-them/), [TFTC](https://www.tftc.io/bitcoin-core-ai-found-vulnerabilities-easily-discoverable-disclosure)

Bitcoin Core, the dominant implementation of the Bitcoin node software, [shipped fixes on Friday](https://www.coindesk.com/markets/2026/11/21/bitcoin-nodes-could-be-stalled-by-repeating-one-id-50-000-times-ai-found-the-bug) for a bug that let one connected peer stall a node. The project rated it medium severity. Loupe found it. Loupe is an open-source scanner from Spiral, Block's open-source unit, and it uses artificial-intelligence (AI) agents to examine Bitcoin code.

The attack works through transaction announcements. Nodes tell their peers about new transactions in batches of inventory messages, and the software did not skip repeated entries. An attacker could first send an orphan transaction, meaning one whose parent transactions the node has not yet seen, with thousands of missing parents. The attacker could then send inventory messages that repeat that transaction's ID 50,000 times. [MLQ.ai reported](https://mlq.ai/news/ai-scan-finds-a-bitcoin-core-bug-that-let-one-peer-stall-a-node-by-repeating-a-transaction-id-50000-times/) that each stall could last more than ten seconds. After the fix, the node processes each transaction in a batch only once.

Elias Rohrer runs Loupe at Spiral, and Bitcoin Core developer Gregory Sanders wrote the fix. One timeline says the report was filed on July 8 and the fix was merged in August, [according to KuCoin News](https://www.kucoin.com/news/flash/bitcoin-core-patches-bug-that-could-stall-nodes-via-repeated-transaction-ids). That leaves a gap of several months between the patch and public disclosure. The fix ships in versions 30.5 and 31.3. The 29.x series no longer receives support, so operators still running it remain exposed.

In late October, Bitcoin Core disclosed [three other Loupe-found bugs](https://cryptoslate.com/bitcoin-developers-rush-to-fix-3-security-flaws-after-ai-uncovers-them/). The most serious let a peer feed a node data until it ran out of memory and crashed on Windows, macOS and BSD systems, while [Linux nodes were reported unaffected](https://ambcrypto.com/bitcoin-core-patches-3-node-crashing-bugs-including-one-that-hit-windows-macos/). Those were [the first disclosures under a new Bitcoin Core policy](https://www.tftc.io/bitcoin-core-ai-found-vulnerabilities-easily-discoverable-disclosure) for flaws that AI tools can easily rediscover. The policy assumes that once a scanner can find a bug, an attacker with the same tool can find it too.

The stall bug threatened neither consensus nor user funds. A stalled node relays transactions and blocks late. That matters most to miners, exchanges and Lightning operators, who need an up-to-date view of the network. Not everyone reads the case as a breakthrough. [One AI-industry commentary](https://kenashe.ai/blog/2026-11-21-an-ai-agent-found-a-bitcoin-core-stalling-bug-not-a-security-panacea) argued that the find does not make automated scanning a replacement for human review. The record so far supports that narrower claim. Loupe finds resource-exhaustion bugs in peer-to-peer code, and humans still write and review the fixes.

## What this means

Cheap AI scanning lowers the cost of finding peer-to-peer bugs for defenders and attackers alike, so node operators on unsupported releases such as 29.x face rising exposure. The likelier outcome is more medium-severity Bitcoin Core disclosures within months, and a disclosed bug that splits consensus or puts funds at risk would change that assessment.

## What to watch

- Whether Bitcoin Core shortens the time between a fix and its disclosure for AI-found bugs. A shorter gap would show that developers believe attackers are running the same scanners.
- Whether Loupe or similar tools turn up bugs in Lightning implementations or alternative node clients, which have smaller review teams than Bitcoin Core.
- How fast node operators upgrade to versions 30.5 and 31.3, since the share of reachable nodes on unsupported versions shows how much of the network stays exposed.
