🚨PSA for LND + BTCPay Server users🚨 Don’t assume you’re safe after upgrading. You’re going to want to explicitly destroy your macaroons and macaroons.db and recreate them fresh. This also applies to auth mechanisms for other LN backends. Also, if you generated a hot on-chain wallet in BTCPay you want to move those funds.

There is a critical vulnerability being actively exploited on BTCPay Server, which can result in the loss of funds. Please update your BTCPayServer to 2.4.2 by going to Admin Dashboard -> Server -> Maintenance -> Update & verify the 2.4.2 version string in the footer. If you are unable to update right away, turn off your BTCPay Server to prevent unauthorized access until you can update.

NEW EPISODE: With @craigraw of @SparrowWallet discussing the latest updates on the desktop Bitcoin wallet. As well as Silent Payments, and more... piped.video/tWrmpfLHSgY

Silent Payments as the next step forward | SLP748 In this episode, @craigraw of @SparrowWallet returns to discuss why Silent Payments is a pragmatic step forward compared to massive address re-use today. We talk Frigate, multisig UX stands in 2026, building Bitcoin wallet software solo, and the ongoing challenges of distribution and platform risk. Timestamps: 00:00 - Intro and Apple’s Walled Garden 05:30 - Pragmatism in Bitcoin 06:30 - Silent Payments: A New Era for Bitcoin Transactions 08:40 - Biggest Challenge in Bitcoin Privacy today 12:03 - Why Address Re Use is so prevalent today 13:40 - Contrasting Silent Payments and Lightning Address 16:00 - The Benefits of Silent Payments Far Outweigh Incremental Complexity 19:00 - The Future if the Bitcoin Community Doesn’t Move on this 22:45 - Privacy vs Convenience 25:40 - Putting SP and Lightning Address together 28:30 - The Scanning Challenge for SP and Frigate 37:20 - Hardware Reqruirements for Frigate 41:00 - Can Hardware Wallets Support SP? 49:55 - Bitcoin Multi Sig in 2026 51:30 - Craig on Miniscript use - Inheritance, Timelocking 53:20 - Miniscript refresh privacy concern 55:30 - Miniscript for managed solutions 59:00 - Multi Sig Quorum Registration 1:01:00 - Mixed Vendor Multi Sig setups 1:04:00 - Wallet Labelling BIP 1:06:44 - Bitcoin Adoption: Balancing Purism and Pragmatism 1:09:00 - What to do about bad regulations or laws? 1:12:00 - Could Government Target Silent Payments? 1:13:39 - Sustainability of Sparrow Wallet Development

Update: the App Review Board has confirmed that my Apple Developer account will not be terminated. Sparrow on macOS is safe. Thank you to everyone who shared and reached out in the past 24 hours - I'm grateful. And credit to @Apple for reviewing the appeal and reaching the right outcome. The deeper problem hasn't gone away: apps impersonating @SparrowWallet are still reaching users and putting their funds at risk. I'll keep working to protect people from those scams, and I hope to do so alongside @Apple. Thank you all.

My attempt to protect users from scam apps on the @AppStore has gotten my Apple Developer account flagged for termination - ironically, for "dishonest activity". Unless it's reversed by June 30, all new installs of Sparrow Wallet will fail, and development on macOS will end. The context: since 2023, more than a dozen fake "Sparrow" apps have appeared on the App Store, as recently as April this year. Users have contacted me after losing their savings, in some cases their life savings, to these impersonators. I'm the developer of the real Sparrow Wallet, a desktop app, and I hold the registered US trademarks for the name and logo. I have publicly warned @Apple and the community about these fake apps from early 2024, but they keep appearing. The app @Apple flagged was a placeholder that was never published. Its only purpose was to warn users that Sparrow is desktop-only and that other "Sparrow" apps aren't mine. This approach may have been misguided, but there was nothing dishonest about it. I'm confident this is an automated misclassification that Apple would reverse on review - but I may be terminated before a human ever looks at my appeal. The cost would fall on @Apple's own users: blocked installs and no updates for a tool people rely on, which opens the door for more fakes. If you value Sparrow, a repost would help. @AppleSupport

🇿🇦 SOUTH AFRICA PROPOSES INSANE CRYPTO CONTROLS, POSSIBLE FORCED SALES South Africa National Treasury and South African Reserve Bank have introduced draft Capital Flow Management Regulations that could dramatically restrict crypto use. The proposal would require disclosure of crypto holdings above an unspecified threshold and could allow the government to force holders to sell assets for rand. Under the draft, investors may not buy, sell, lend, or transfer crypto above the threshold without permission, except through approved providers. Transactions would require a stated purpose, and using funds outside that purpose could trigger mandatory resale. Cross-border transfers and payments using crypto would be banned without approval. Authorities would also gain powers to search individuals, demand declarations, and seize assets suspected of violating the rules. Critics say the changes raise serious constitutional concerns around privacy, property rights, and freedom of association, calling them among the most aggressive updates to South Africa’s decades-old exchange control system.

Citadel Dispatch 199: @craigraw - @sparrowwallet We discuss silent payments, a new bitcoin address system that eliminates address reuse, removes the gap limit, and aligns privacy with convenience. serve.podhome.fm/episodepage…