UNGOVERNABLE (RSS Feed) on Nostr: What a Week | THE BITCOIN BRIEF 86 A bi-weekly news show informing you on the latest ...

What a Week | THE BITCOIN BRIEF 86

A bi-weekly news show informing you on the latest in Bitcoin, privacy and open source tech hosted by Ungovernables, Max and Q.

THIS IS THE TWEET Q WANTS YOU TO SEE: https://x.com/justh0dl/status/2086202393998291138

AOB

- What a fucking week
- KeyOS v1.3.1 now publicly https://foundation.xyz/blog/keyos-version-1-3-1-is-now-available
- Something exciting to share on Friday's FTF (delayed by 2 weeks)

NEWS

The Coldcard entropy catastrophe

Sources: https://blog.coinkite.com/entropy-technical-backgrounder/ / https://www.therage.co/everything-you-need-to-know-about-the-coldcard-hack/ / https://www.trmlabs.com/resources/blog/the-largest-hardware-wallet-exploit-of-2026-inside-the-usd-116-million-coldcard-hack / https://coldcard.rip/ / https://cktripwire.com/ / https://bitcoinmagazine.com/news/coldcard-victims-report-median-loss-1btc

EXPLAINER
The largest self-custody theft on record, and it traces back to a single wrong conditional. In March 2021 a build guard checked whether Coldcard's hardware random number generator was defined rather than whether it was enabled, so seed generation silently fell back to a deterministic software PRNG. Every seed made on an affected device from that point carried roughly 40 bits of entropy on Mk2 and Mk3, and about 72 on Mk4, Mk5 and Q, instead of the intended 128. That is guessable. Someone did the maths offline, derived the addresses, checked them against the public chain, and swept everything with a balance. Somewhere between 1,400 and 1,800 bitcoin gone, depending on whose forensics you trust, with a median victim loss of one BTC. The part people keep missing: updating the firmware does not fix an existing seed. A weak seed is weak forever.

ACTION FOR LISTENERS

- Move funds to a brand new seed BEFORE upgrading firmware (Lopp's guidance, on reports of update problems).
- Use high fees. If you see your own coins in the mempool, the attacker opted into RBF and you can outbid them. Window is minutes.
- Multisig users: consider a private mempool like Marathon's Slipstream.
- Keep the device; the UID may prove ownership in any recovery process.
- Updating does NOT fix an existing seed. A weak seed is weak forever.
- You are exempt only if you added 50+ fair independent private dice rolls, or used a strong unique BIP39 passphrase stored separately.

BTCPay Server: unauthenticated LND macaroon theft, actively exploited

Sources: https://blog.btcpayserver.org/security-advisory-btcpay-server-2-4-2/ / https://github.com/btcpayserver/btcpayserver/releases/tag/v2.4.2 / https://www.coindesk.com/tech/2026/08/08/another-bitcoin-infrastructure-exploit-hits-this-time-draining-merchant-lightning-nodes / https://www.tftc.io/btcpay-server-v2-4-2-lnd-macaroon-exploit-lightning-nodes-drained

CRITICAL FRAMING NOTE: this is ONE story, not two. The "BTCPay bug" and the "LND credential exploit" are the same event. The vulnerability is the macaroon leak. The Aug 8-9 wave of coverage is follow-up hardening, not a new incident. Do not present them separately.

REMEDIATION (updating alone is NOT enough)

- Update to v2.4.2. Verify "2.4.2" in the footer.
- Update NBXplorer to 2.6.10+.
- Revoke and regenerate LND macaroons. Updating stops new theft but does nothing about already-stolen credentials. Deleting files is insufficient; the macaroon root signing key must be destroyed at node level. v2.4.2 does this automatically for standard Docker deployments. Custom reverse proxies, separate Tor services or port forwarding must rotate manually.
- Move funds out of any BTCPay-generated on-chain hot wallet and recreate it.
- Update LND to 0.21.1. Audit for unrecognised channel closures, unknown peers, unexplained balance changes.

SIDE EFFECT WORTH FLAGGING: v2.4.2 removes public LND API access on Docker deployments, which breaks remote wallet connections such as Zeus connecting to your own BTCPay node. Intentional, no restoration timeline published.
BREAKING CHANGE: Greenfield Basic authentication disabled by default five minutes after account creation (#7492). BTCPay: "We are not aware of any user impacted by this breaking change, as API Keys authentication is generally used."

Boltz suspends all swaps indefinitely
Sources: https://x.com/Boltzhq/status/2084311537502630319 / https://canary.boltz.exchange/ / https://thedefiant.io/news/defi/bitcoin-bridge-boltz-halts-swaps-indefinitely-citing-ai-assisted-attacks / https://www.tftc.io/boltz-bitcoin-swaps-suspended-ai-attacks / https://www.bullbitcoin.com/blog/boltz-has-suspended-its-swap-services-your-funds-are-safe-here-is-what-it-means-for-bull-wallet-users

CORRECTION TO THE COMMON FRAMING: Boltz has not shut down. It suspended swap services indefinitely. And the canary sequence runs the opposite way to the rumour: lapsed → suspended → renewed clean.

The Bitcoin Red Team
Sources: Calle and Rob Hamilton on Nostr/X / https://bitcoinmagazine.com/business/bitcoin-red-team-finds-85-critical-flaws-across-390-open-source-repos-after-coldcard-exploit / https://www.coindesk.com/ / https://www.tftc.io/ / https://opensats.org/funds/red
SUMMARY
This is the story that explains the other four. After the Coldcard exploit, Calle and Rob Hamilton pointed frontier AI models at the open-source Bitcoin stack and started auditing everything. In 108 hours, 25 developers scanned 501 projects and produced 7,958 findings, 1,280 of them rated high or critical, at a compute cost north of 58,000 dollars. They found the BTCPay bug's neighbours, and Boltz cited exactly this dynamic when it switched itself off. The uncomfortable symmetry is that the same capability doing the defending is what an attacker almost certainly used on Coldcard in the first place. And the bottleneck turns out not to be finding bugs, it is telling anyone: only 19.5% of the projects they scanned even have a http://SECURITY.md file, and only 13.1% list a security contact. The scanners move at machine speed. Responsible disclosure is still hunting around for an email address.

BIP-110: the fork that mined two blocks and froze
Sources: https://bip110monitor.com/ / https://petertodd.org/2026/bip-110-code-review / https://bitcoinmagazine.com/technical/bitcoins-bip110-moment-three-possible-scenarios / https://blog.lopp.net/a-laymans-guide-to-bip-110/ / https://www.strategy.com/media/articles/110-reasons-bip-110-is-a-bad-idea / https://www.coindesk.com/tech/2026/08/09/controversial-bitcoin-fork-bip-110-mines-two-blocks-then-stops

RELEASES

Bitcoin core / protocol

- https://github.com/bitcoin-core/secp256k1/releases/tag/v0.8.0 - 2026-08-03Adds a native Silent Payments (BIP-352) module directly into the crypto library nearly every self-custody wallet builds on, plus up to ~11% faster signature verification. Quietly the most consequential positive release of the fortnight: it lowers the bar for every wallet to ship reusable static receive addresses.
- https://github.com/bitcoinknots/bitcoin/releases/tag/v29.4.knots20260508 - 2026-08-08Non-urgent maintenance: fixes a chainstate DB bug causing repeated large rewrites, and adds corruption-detection safeguards around BIP-110 mandatory signaling. No critical fixes. (No Bitcoin Core release in window; latest is v31.1 from 2026-07-08.)

Hardware / signing

- https://github.com/Coldcard/firmware/releases/tag/2026-07-31T1248-v4.2.0 - 2026-08-03The patch for the entropy catastrophe. Affected ranges: Mk2/Mk3 4.0.1 through 4.1.9; Mk4/Mk5 all before 5.6.0; Q all before 1.5.0Q. Companion fixes shipped the same day: https://github.com/Coldcard/firmware/releases/tag/2026-07-31T0519-v5.6.0, https://github.com/Coldcard/firmware/releases/tag/2026-07-31T0517-v1.5.0Q, https://github.com/Coldcard/firmware/releases/tag/2026-07-31T1609-v6.6.0X, https://github.com/Coldcard/firmware/releases/tag/2026-07-31T1605-v6.6.0QX. Updating does NOT fix an existing seed - changelog says Mk3 users "must regenerate any seeds made on earlier versions as their entropy is critically low at just ~40 bits." TAPSIGNER, OPENDIME and SATSCARD unaffected.
- https://github.com/selfcustody/krux/releases/tag/v26.08.0 - 2026-08-04Maintainer odudex is stepping down and the project may be archived. "Krux was not created by me: Jeff started it and passed it on to me, and now it is my turn to pass the torch." On succession: "Krux may be carried on by another maintainer, if a proof-of-work backed Krux contributor accepts the role. Otherwise the Krux project will be put in sunset mode and gracefully archived in a few months." Cause is hardware, not drama: "K210 chips are no longer produced, and Canaan dropped the Kendryte line entirely." Substantial release regardless: fixes a heap buffer overflow in the camera entropy module, adds stricter PSBT fee-calculation checks, replaces the Python UR stack with a faster C module, and makes Krux Installer fully offline.
- https://github.com/frostsnap/frostsnap/releases/tag/v0.3.0 - 2026-08-05FROST threshold-signing device ships reproducible/deterministic builds and "a fresh release signing key as part of an overhauled release-signing pipeline." Well timed in a fortnight where "can you verify what is running on your signer" is the whole conversation. Catch: the new key breaks in-place Android updates, so direct-APK users must uninstall, reinstall, and re-visit their threshold devices to restore.
- https://github.com/trezor/trezor-suite/releases/tag/v26.7.4 - 2026-08-04Lowers minimum Normal-priority fee rate to 0.2 sat/vB and ships updated Safe 7/5/3 and Model T firmware with security improvements.
- https://github.com/BitBoxSwiss/bitbox-wallet-app/releases/tag/v4.51.4 - 2026-08-07Bundles new BitBox02 firmware v9.26.5.
- https://github.com/cryptoadvance/specter-desktop/releases/tag/v2.1.11 - 2026-08-09Genuinely security-relevant: adds auth and CSRF protection to the HWI bridge settings, restores validation of active API tokens so revoked JWTs are rejected, and warns that Specter's auth layer does not encrypt the data folder. Also ships an in-app Coldcard Mk3 seed-entropy advisory.
- https://github.com/proto-at-block/bitkey/releases/tag/source%2F2026-08-02-0031 - 2026-08-02Block's consumer hardware wallet, routine source drop.

Lightning

- https://github.com/btcpayserver/btcpayserver/releases/tag/v2.4.2 - 2026-08-07Actively exploited, funds already stolen. "This release contains fix of a critical vulnerability that is being actively exploited. You need to update as fast as you can." Unauthenticated remote .macaroon disclosure for LND, plus a TOTP 2FA bypass via Greenfield Basic auth. Requires NBXplorer 2.6.10. Breaking change: Basic auth disabled by default five minutes after account creation. See News item 2 for full remediation.
- https://github.com/lightningnetwork/lnd/releases/tag/v0.21.2-beta.rc1 and https://github.com/lightningnetwork/lnd/releases/tag/v0.20.3-beta.rc1 - 2026-08-08Not security releases and not related to the BTCPay exploit. Migration/stability fixes only: KV-to-SQL payment migration edge case, channeldb migration recovery, invoice handling, data races, bounded memory on graph sync.
- https://github.com/ZeusLN/zeus/releases/tag/v13.1.3 - 2026-07-27Adds LND v0.21.1-beta support for embedded and remote nodes; patches known vulnerabilities in the ws, js-yaml and markdown-it dependencies. (Note: Zeus also shipped an unreleased swap-security sprint on 08-04 - verify…

https://op3.dev/e/dts.podtrac.com/redirect.mp3/pdcn.co/e/pscrb.fm/rss/p/serve.podhome.fm/episode/df3c7f87-bdab-41fe-1438-08dbf068e250/63922126232619255741fb3e75-3373-4bb9-9698-b8c09c8e6a2d.mp3

https://serve.podhome.fm/episodepage/ungovernable/what-a-week-the-bitcoin-brief-86