WEDNESDAY, JUN24
1. Apple vs Sparrow Wallet, 2. Run your own Electrum server, 3. $17.5B nuclear revival, 4. GitHub bans a Bitcoin project
From Proto and Bitkey - part of the Bitcoin ecosystem at Block, Inc.
1. sparrow
Apple threatened to terminate the developer account behind Sparrow, one of the most respected desktop bitcoin wallets, before reversing the decision on appeal a day later, Bitcoin Magazine reported. Sparrow creator Craig Raw disclosed on June 22 that Apple had flagged his account for termination by June 30, classifying as dishonest a placeholder app he had submitted to warn users that more than a dozen fake Sparrow apps were impersonating his software and draining funds. Sparrow is desktop-only and distributed from Raw’s own website, but his Apple Developer certificate signs the macOS build, so termination would have broken new installs and ended Mac development. After bitcoiners flooded Apple with appeals, the App Review Board confirmed on June 23 that the account would stand. The episode resolved well, but the underlying problem persists: scam wallets keep clearing App Store review while the developer flagging them faced removal. For self-custody users, it is a sharp reminder that platform gatekeepers, not open protocols, decide what software reaches phones.
-EDITOR·OP_DAILY2. electrum
A widely shared exchange among bitcoin educators renewed focus on a practical sovereignty setup: pairing a hardware wallet with a personally operated Electrum server so a user verifies transactions against their own full node rather than a third party’s. Podcaster Stephan Livera framed the combination as real bitcoin sovereignty, and developer skot, known for the open-source Bitaxe miner, amplified the point. The technical idea is that most wallets, even with self-custodied keys, query someone else’s server to learn their balance and transaction history, leaking address information and trusting that server’s view of the chain. Running your own Electrum server closes that gap, letting the wallet talk only to infrastructure the user controls. For a freedom-tech audience, the reminder matters because self-custody is often treated as solely about key control, when privacy and verification depend equally on whose node you trust. The setup demands more effort, but it removes a quiet dependency that undercuts the independence self-custody is meant to provide.
-EDITOR·OP_DAILY3. nuclear
The US Department of Energy has announced a $17.5 billion loan commitment aimed at reviving American nuclear power, a major federal push to expand baseload generation as electricity demand surges from data centers and artificial-intelligence computing, per Bitcoin Magazine. While not a bitcoin story directly, the development bears on the energy dynamics that shape mining, since nuclear offers the kind of steady, carbon-free power that both miners and AI operators increasingly compete for. The surge in electricity demand from computing has revived interest in nuclear after decades of stagnation, with technology firms signing power deals and governments backing new capacity. For an audience tracking the energy-and-compute collision, the loan signals that policymakers now treat power generation as strategic infrastructure for the computing economy. Bitcoin miners, long criticized for energy use, have argued they can support grid economics and fund power development; a federal nuclear revival reframes the broader question of who builds and pays for the generation that energy-hungry industries require.
-EDITOR·OP_DAILY4. github
Bitcoin Core contributor Matt Corallo reported that GitHub has permanently banned an open-source project he works on, with no explanation and no appeal path, citing a terms-of-service clause he says does not cover anything the team has done. Corallo, who builds full-time open-source Bitcoin and Lightning software at Spiral, framed the decision as a signal that Bitcoin projects should leave GitHub. The post follows earlier complaints that GitHub wrongly flagged a contributor and knocked out the organization’s CI. For builders shipping permissionless money, centralized code hosting is becoming an operational risk alongside custody and compliance. The episode echoes the same lesson surfacing across the freedom-tech stack this week, that the platforms developers rely on, from app stores to code hosts, can revoke access without warning or recourse. Distributing source through self-hosted or decentralized alternatives is increasingly treated not as ideological preference but as basic operational resilience for projects that cannot afford a single point of failure.
-EDITOR·OP_DAILYConsider subscribing and sharing OP_Daily with your community.