Price:

Bitcoin’s new testnet makes miners prove they’re ready

Nov 20, 2026Summary from 2 podcasts.
  • Testnet 5 replaces a spam-prone network with a tougher, more transparent setup.
  • Mining pools can test new consensus rules and catch compatibility problems before they matter on mainnet.

Bitcoin developers have replaced Testnet 4 after they could not patch a minimum-difficulty flaw that allowed free-block spam. Testnet 5 began on November 14, when Anthony Towns mined its first block alongside mainnet block 975744. The new genesis block commits to a recent mainnet block hash, making the starting point public rather than something organizers could secretly choose.

Testnet 5 also raises the minimum difficulty by about a million times compared with Testnet 4, so its launch required a public call for miners. From its first block, it enforces BIP54, a set of consensus rules that determine which blocks nodes accept.

That makes the network a live rehearsal for mining pools. Bitcoin Core has supported the relevant rules since version 29, but pools also need to update the software that builds their coinbase transactions. If a pool creates a block that breaks the rules, Testnet 5 nodes reject it, giving miners a chance to find problems without financial loss before the rules reach mainnet.

Bitcoin Optech reported about 1.5 petahashes per second mining on Testnet 5, with P2Pool V2 responsible for about a third of the early blocks. The launch is already putting the test to work: miners have to show their software can build compatible blocks, not simply say it is ready.

Source Intelligence

- Deep dive into what was said in the episodes

Bitcoin Optech: Newsletter #431 Recap • Nov 17

  • 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.
  • 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.
Also discussed on this episode: (17)

Safety (8)

  • 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.
  • 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 (3)

  • 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.
  • 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.

The Great Hashrate Heist | THE BITCOIN BRIEF 97 • Nov 16

  • Testnet 5 replaced Testnet 4 after developers could not patch Testnet 4's minimum-difficulty flaw, which allowed free-block spam. Anthony Towns mined Testnet 5's genesis block alongside mainnet block 975744, restoring a usable network for Bitcoin testing.
Also discussed on this episode: (22)

Robotics (1)

  • Max is using AI design tools to plan a kitchen he cannot source locally, and is exploring 3D printing to make the parts himself. He says modern printers can handle multiple materials, while q and a described using a roughly $200 Ender printer for basic household parts.

Custody (7)

  • Foundation's upcoming Passport Prime tinfoil hat mode removes Bluetooth firmware during onboarding and lets users create a seed without Envoy. Users can verify the device manually, then use QR codes; they can restore Bluetooth later by reinitializing the device.
  • Passport Prime retains two-factor codes, NFC, USB, security-key support, and file storage when Bluetooth firmware is removed, but manual time-setting can cause two-factor codes to drift. Foundation says a separate Bluetooth-free hardware device is possible but is not currently planned.
  • Foundation said Passport's legacy mode supports non-Bitcoin assets including Ethereum and Solana, with more options expected. q and a said Foundation does not plan to support generic hardware, which he compared with SeedSigner.
  • A New York lawsuit seeks control of roughly 3.8 million Bitcoin across 39,000 addresses by arguing that long-dormant coins are abandoned property. One wallet named in the case moved 75 BTC, showing that at least some supposedly abandoned coins still have active owners.
  • Blockstream and Thales launched an enterprise custody product using FROST threshold signatures inside hardware security modules. Taproot makes a spend appear on-chain like an ordinary single-key transaction, while the full private key is never assembled in one place.
  • A public iOS sandbox escape called Worse Query reportedly exposed local files across apps, potentially including wallet seed phrases. Binance warned about the risk; the hosts advised against installing new wallet apps and recommended keeping limited funds on phones.
  • Trezor Suite added a warning before sending to a never-used address to help catch address-poisoning attempts. Spectre added BIP 329 label imports and exports, Taproot support for BitBox02, and Spectre DIY imports; Lightning Dev Kit released security fixes.

Open Source (1)

  • Derek Ross is porting the AI-powered Omarchy Linux distribution to Android. Max said he planned to discuss the project with Ross, who was expected to appear on Freedom Tech Friday.

Mining (2)

  • An attacker compromised Luxor's Commander mining fleet software on November 15 and redirected miners to an attacker-controlled address through Ocean. CoreX estimated roughly 13 exahashes per second, about 64,000 machines and 1.5% of Bitcoin's network, were affected; Luxor had not confirmed those estimates.
  • Luxor patched Commander within two hours, said its mining firmware and customer data were untouched, and promised affected customers normal payment. The attacker received about 0.3 BTC in Ocean payouts; Luxor CEO Nick Hanson called the incident an AI-enabled attack, but the entry method remained unknown.

Privacy (2)

  • Ashigaru disclosed that an attacker altered unsigned lines in its release manifest after breaching the Git server on November 5. No signing keys were taken and no Bitcoin loss was identified; users were advised to check app URLs and wait for a verified fixed release.
  • A listener recommended Michael Bazzell's book Extreme Privacy: What It Takes to Disappear for practical privacy guidance. Max said the book was widely circulated in Bitcoin privacy circles around 2018 and may now be dated, while still containing useful principles.

Regulation (1)

  • The US Department of Justice said it has court authorization to seize or restrain more than $1.2 billion linked to the Binance theft attributed by the FBI to North Korea. More than $2.7 billion has been frozen through government and private-sector actions, largely involving issuer-controlled tokens; about 18,270 stolen BTC remains beyond those controls.

Lightning (3)

  • LN Markets made identity verification mandatory for every account. Its new volume tiers require photo ID and a liveness check below $25,000 in rolling 30-day volume, a financial questionnaire up to $125,000, and three months of proof of funds above that level.
  • LNbits traced its recent attacks to server-side request forgery bugs in legacy Python extensions, which let attackers reach internal services and sometimes take over entire servers. The team said autonomous AI agents may have run the attacks, but it could not confirm the tools used.
  • Lightning Labs released an experimental Pi coding-agent extension that pays for AI model responses over Lightning when an endpoint returns HTTP 402. Sellers set prices through Aperture, and the agent can pay per token without accounts or API keys; the repository had no tagged release yet.

Payments (1)

  • Dana Wallet added spending strategies, a send-max button, clearer broadcast feedback, and display choices for fiat or Bitcoin. Its update also changed how it resolves BIP 353 human-readable payment names; a host said he had not yet tested the wallet.

Digital Sovereignty (1)

  • A listener argued that self-hosting can reduce reliance on other people's infrastructure, but users need informed consent and clear explanations of the trade-offs. Max agreed that AI tools could help people make these technical choices without requiring expensive private-computing hardware.

Nostr (1)

  • Andrew said he is building a Bitcoin-agnostic, Nostr-gated website using Spacy's protocol and asked to discuss the project on air. The hosts said they would review it before deciding whether to invite him.

Corruption (1)

  • A listener contrasted the immediate consequences of allegations involving Jensen with the lack of justice for Epstein's victims. The comment framed the outcomes as unequal accountability, without providing further details about the allegations or the case.

BTC Markets (1)

  • RevHoddle urged Bitcoiners to diversify how they spend time, attention, and capital, arguing that reaching the finish line matters more than the size of a Bitcoin stack. The hosts endorsed the advice as a broader way to think about personal capital.