Your signal. Your price.
BISQ 2.1.14 tightened offer and invoice checks, enforced seller reputation limits, signed storage, and isolated Tor connections by identity. Zeus 13.2.3 checks that an LSP-wrapped invoice matches the approved invoice, preventing a provider from silently changing the payment.
Corsico 0.3 keeps Lightning spending keys on a separately flashed LilyGo T-Display board and confirms payments over Bluetooth; its Spark-based design lets Spark operators co-sign. KQuality 6.5 added multiple accounts per seed and a faster Fulcrum-powered sync engine, while Bitcoin C Tool 2.4.1 fixed mobile layout issues.
The Cash App advertisement said customers can buy Bitcoin without fees on recurring purchases or purchases above $2,000, then withdraw on-chain or over Lightning at any time. It also advertised a $21 new-customer bonus for users who sign up with the stated code and send at least $5 to a friend within two weeks.
Marty Bent’s Block ad described Cash App Bitcoin services, Lightning payments through Square, and Bitkey self-custody with multisignature recovery. The Aven ad promoted credit backed by Bitcoin without selling it, with fixed-rate borrowing and cash back.
Curry says he upgraded StartOS to version 4.0 for built-in WireGuard networking; the upgrade required a filesystem change and delayed his Lightning services. Jones notes that Helipad can replay old Lightning records in the background after a database migration.
The hosts thank supporters for PayPal donations, including contributions from $5 to $30, and True Fans and Lightning contributions denominated in sats. Curry says listener donations help keep the machines running.
SF is a graphic designer whose Bitcoin work includes the first two Bitcoin Focus magazine editions, logos for Bitcoin projects, and the widely reused Notre Dundas logo. SF also makes free art, a Bitcoin tarot machine, and Lightning fortune cookies.
SF routes Wavlake song payments through LNbits: a Wavlake track costs 210 sats, with 90% going to the original artist and a 5% kickback to the radio. Regular library requests cost 21 sats as an anti-spam fee, with longer tracks priced higher.
SF lets guest DJs register their own pages and Lightning wallets, and can stream live sessions through an RTMP server. Live donations accumulate until a session ends, then go to participating DJs who provide Lightning addresses; the radio also pays copyright collection agencies.
SF moved away from the old bot’s shared user wallets as European rules for services that hold or transmit value grew more demanding. The current radio requires users to connect their own Lightning wallets, and SF said funds remaining in the old bot should become withdrawable.
SF was preparing to experiment with Liquid swaps when a hack froze swaps, and said Adam had reported that service restoration was nearing. SF took the incident as a reason to stick with on-chain Bitcoin and Lightning.
Michael calls Lightning interesting but says it was marketed beyond what it could readily deliver; Vlad says it is useful for private transfers but not a complete scaling answer. Vlad’s old routing node lost money despite channels to major hubs, while custodial Lightning remains a concern for wider use.
Vlad says Hoddleonaut blocked him after Vlad interviewed Roger Ver, amid claims that the interview was paid promotion; Vlad denies receiving payment and says he offered Ver tough questions. Hoddleonaut had launched the Lightning Torch, whose handoffs tracked routes, countries, and custodial versus self-run wallets.
Elias described LDK 0.3.0-rc3 as the next mainline release candidate and LDK 0.2.7 and 0.1.13 as patch releases with bug fixes and security hardening. He encouraged testing the 0.3 branch, avoiding mainnet before release, and upgrading existing users promptly.
LDK fixed a channel-reestablishment flaw that could let a peer deny receiving an acknowledged commitment update, prompt LDK to resend a commitment, and steal forwarded HTLC funds. Other fixes address Electrum sync missing confirmed spends and LSPS2 attackers inducing an LSP to forward funds without receiving the corresponding payment.
LDK also fixed a restart path where stale channel-manager and channel-monitor state could mishandle committed HTLCs and lose funds. Elias’s change makes short-channel-ID alias negotiation the default for new private channels, removing an old compatibility option.
Bitcoin Core 32.0-rc3 has a testing guide and needs testers. Core Lightning 26.06.9 is a security release covering channel establishment, splicing, HTLC handling, and access control; BTCPay Server 2.4.5 blocks private-network webhook destinations by default and tightens invoice and refund permissions.
Core Lightning backported security and reliability fixes, including preventing a post-splice force close from publishing a revoked commitment and matching on-chain HTLCs by both script and amount. A make-secret flaw also let authorized callers derive the master secret and forge unrestricted RPC tokens.
Eclair added checks against excessive fees in dual funding and splicing: it independently verifies Bitcoin Core-built transactions and rejects peer-proposed RBF fee rates above Eclair’s calculated maximum when Eclair pays. LND fixed 32-bit fee aggregation that could understate fees in BOLT11 invoices with blinded paths.