The deadline came and went at 02:16 a.m. on July 24, 2026. Three hours earlier, India's Ministry of Home Affairs had issued an unusual ultimatum to GitHub: delete every repository, release, and line of code associated with Bitchat, a Bluetooth mesh messaging app backed by Jack Dorsey. The government cited "anti-national elements" and potential misuse. The clock ran out. Nothing happened—at least not what New Delhi expected.
Within 48 hours, Bitchat's codebase materialized on Radicle, a peer-to-peer network built specifically to resist this kind of pressure. No central server. No company to lean on. Just cryptographic signatures and a web of volunteer nodes scattered across the internet.
The sequence raised a question that reaches beyond one messaging app: Can decentralized infrastructure actually shield developers when governments decide their code is dangerous?
An Order in the Middle of the Night
India's Cyber Crime Coordination Centre issued what it termed an "order for reasoned intimation" at 23:16 IST on July 23. The target list was precise—three URLs pointing to Bitchat's iOS repository, its Android port, and a releases page hosting installation files. Legal justification came from Section 79(3)(b) of the IT Act, 2000, a provision normally applied to intermediary liability rather than content blocking.
The Internet Freedom Foundation immediately flagged the procedural choice as strange. Section 69A is India's standard mechanism for blocking online material, complete with safeguards and review processes. This wasn't that. The Internet Freedom Foundation called it "unconstitutional and authoritarian" in a statement reported by The Times of India on July 26. The government had, in effect, treated GitHub like a social media platform hosting illegal speech rather than a repository storing software blueprints.
By July 25, when AndroidPure tested access from a Delhi broadband connection, the repositories still loaded without issue. GitHub's public government-takedowns ledger—where the company typically documents blocking requests—showed no entry for the Bitchat order. Enforcement in India can be inconsistent, varying by ISP and sometimes by the hour.
Perhaps more telling: GitHub never publicly confirmed receiving the notice or outlined any response. The three-hour window closed in silence.
What Made This App Worth Censoring
Bitchat doesn't use the internet. It doesn't require servers, phone numbers, SIM cards, or user accounts. Messages bounce from phone to phone across Bluetooth Low Energy, forming a mesh that operates independent of infrastructure someone can switch off. Dorsey unveiled the project on July 6, 2025, publishing white papers and code through a GitHub organization called permissionlesstech.
The timing of India's takedown attempt was, if nothing else, conspicuous. Protests had been simmering around Jantar Mantar in Delhi, where authorities had imposed mobile internet blackouts with growing frequency. Bitchat's architecture allows encrypted messages—and, theoretically, Bitcoin transactions—to hopscotch through the mesh until some connected device can relay them to the broader network. CoinDesk summarized the notice tying usage to Delhi protests amid repeated internet suspensions.
Google Play showed one million downloads as of June 17, 2026, though the app carried a middling 3.7-star rating. Developer records listed Verse Communication PBC, a public benefit corporation in Portland, Oregon. Not exactly a shadowy operation, in other words.
From Broken to Battle-Tested
Security researchers pounced the moment Bitchat went live in July 2025. TechCrunch reported on July 9, 2025, that the app had launched without formal security testing—a cardinal sin for anything promising encryption and anonymity. Alex Radocea at Supernetworks published a detailed breakdown titled "Vibe Identity: An Obvious Flaw," highlighting authentication weaknesses and pointing toward the Noise protocol as a fix.
Dorsey's team responded quickly, perhaps faster than critics expected. By August 2025, Supernetworks confirmed the developers had migrated to Noise and secured iOS App Store approval. Version history through mid-2026 shows continuous hardening: signed public channels, Tor routing for users wanting internet privacy, proof-of-work spam filters, and integration with Cashu, an ecash system.
App Store records show version 1.7.0 landing on July 9, 2026—two weeks before the government order—with push-to-talk, mesh bridging, and delivery improvements. Whether those refinements made the app more threatening or just more functional is open to interpretation.
The Radicle Gambit
Radicle operates on a fundamentally different premise than GitHub. Instead of repositories living on Microsoft's servers, they're cryptographically anchored and replicated across a network of volunteer seed nodes. Think Git, but without the company in the middle. Developers work locally and sync changes through what the project calls a gossip protocol—nodes sharing updates peer-to-peer rather than checking in with headquarters.
On July 26, a Hacker News post titled "Bitchat is now on Radicle" accumulated 232 upvotes and 128 comments. The migration was explicit: if GitHub caves to government pressure, the code survives elsewhere. Multiple commenters drew direct lines to India's takedown attempt.
Radicle's design makes geographic censorship complicated, if not impossible. Code lives simultaneously on machines across continents. Shutting down access requires pressuring every seeding node individually, and new seeds can spin up anywhere with an internet connection. There's no CEO to summon to a hearing, no Terms of Service to rewrite under duress.
The project's FAQ—last updated May 21, 2026—explains that ownership and permissions derive from cryptographic keys rather than platform accounts. Anyone can clone and seed a repository. Authenticity comes from verifying signatures, not trusting GitHub's database to tell you who the real maintainer is.
Echoes of Earlier Battles
Governments have targeted Bluetooth mesh messaging before, though rarely by going after the code itself. FireChat surged to prominence during Hong Kong's 2014 protests, with CNN Money reporting on September 30, 2014, that users were installing it to coordinate when authorities throttled mobile networks.
Bridgefy followed a similar trajectory, gaining traction during protests beginning in 2019. TechCrunch reported on November 2, 2020, that Bridgefy added end-to-end encryption after researchers broke its original implementation. Academic papers presented at USENIX in 2022 documented vulnerabilities that persisted even after the fixes.
Briar—another peer-to-peer messenger supporting Bluetooth and Wi-Fi sync—released version 1.5.19 on July 13, 2026, continuing years of quiet development in the same regulatory gray zones.
What sets the Bitchat episode apart is the public, frontal assault on source code distribution rather than simply blocking app downloads. Dorsey's megaphone turned what might have been a quiet removal request into a test case. Whether intentional or not, that visibility forced the question into the open.
What Comes After Midnight Deadlines
As of late July 2026, Bitchat's GitHub repositories remained reachable on at least some Indian networks. The government's three-hour ultimatum came and went. GitHub never issued a statement confirming it received the notice, let alone explaining what action—if any—it took. The repositories stayed up.
The Radicle mirror exists, though actually using it requires developers to install Radicle tooling rather than simply clicking a browser link. The network's seed infrastructure remains less robust than GitHub's globally distributed CDN. Practical accessibility lags ideological promise, at least for now.
For developers working on censorship-resistant technology, the episode offers something more instructive than a simple win or loss. Bitchat crossed a threshold that matters: forcing governments to target not just distribution channels or app stores, but the underlying blueprints themselves. That's a harder fight to win quietly.
The technical machinery for unstoppable code hosting exists. Radicle works, as do similar systems like IPFS and Dat. Whether the broader developer community adopts them at scale—outside moments of crisis—is a different question entirely. Infrastructure only resists pressure if enough people actually use it.
In some ways, India's order may have done more to advertise Radicle's capabilities than years of technical evangelism could have managed. The code moved. It stayed accessible. Three hours turned into days, then weeks. The experiment continues, one seeded repository at a time.
