The geometry of code is a peculiar thing. It breathes in commits, sleeps in repositories, and dreams of being forked. But on a quiet Tuesday in New Delhi, a different kind of geometry unfolded — one of fear, haste, and digital amputation. Within three hours, three GitHub repositories belonging to Bitchat, a decentralized messaging application loosely associated with Jack Dorsey, were erased from the platform. The order came from the Indian government, citing that the software had been used to coordinate communications during internet shutdowns in protest regions. The code was silenced. But sound travels faster than silence.
Let me step back. Bitchat is not a household name. It is not Telegram or Signal. It is a small, open-source experiment in peer-to-peer messaging, designed to operate without central servers. Its aesthetic is raw, its interface minimal, its purpose singular: to allow people to talk when the network goes dark. Jack Dorsey’s name hovers near it like a signature on a manifesto — not as a builder, but as a patron of decentralized ideals. The project has no token, no sales, no hype. It exists only as code. And that code, stored on GitHub, became a liability.
Core to this story is an infestation of centralization that many in the Web3 space choose to ignore. We celebrate blockchain as an immutable ledger, but we host our source code on a single corporate platform owned by Microsoft. We preach censorship resistance, but we contribute to repositories that can be deleted by a government letter. Bitchat’s downfall is not its technology — it is the soil in which its seeds were planted. Based on my experience auditing governance tokens during the 2022 bear market, I’ve seen how deeply even the most decentralized projects rely on centralized infrastructure. The same pattern repeats: a protocol’s code lives on GitHub, its community lives on Discord, its name lives on Twitter. When pressure comes, the weakest link snaps.
The Indian government’s action is not novel. Section 69A of the Information Technology Act grants it sweeping powers to block content in the interest of national security. What is novel is the speed: three hours to identify, review, and remove three repositories. That suggests a pre-meditated strike, likely involving surveillance of how protestors were communicating. And here the game theory becomes cruel. Bitchat’s value proposition — its ability to function during internet shutdowns — is precisely what made it a target. The government saw not a communication tool but a threat to its ability to control information flow.
But let me twist the lens. The contrarian angle is uncomfortable: this censorship may be the best thing that could happen to Bitchat — and to the broader crypto ecosystem. I have watched too many projects die from obscurity. This incident injects a dose of urgency into the question of how we distribute our code. If GitHub can be compelled to remove repositories, then GitHub is not a safe home for public goods. The answer is not to beg for mercy from platforms, but to build new ones. I recall my 2017 days dissecting Golem’s Sybil resistance mechanisms; back then, the beauty was in the code itself. Today, the beauty must extend to the entire supply chain of that code.
Prune the dead branches, save the tree. The tree here is the ideal of permissionless innovation. The dead branch is reliance on centralized code hosting. Projects like Radicle, which use IPFS and a peer-to-peer overlay, offer a path forward. Bitchat itself could be mirrored there, and perhaps it already has been by anonymous forks. The geometry remembers: once a repository is cloned, it lives in a million shadows. The Indian government can delete the original, but not the copies. This is the essence of decentralization — not a technology, but a distribution of power.
The new insight here is not that governments can censor code, but that the crypto industry must treat code distribution as a first-class security concern, just as it does with private keys or governance tokens. Most projects audited by my team still store their source on GitHub with no backup on decentralized storage. That is a ticking bomb. Bitchat’s silence should be a scream for every developer reading this.
Takeaway: The soul of decentralization lives in its weakest link. If we want to build a parallel financial and social system, we must ensure every plank of its hull is forged from the same steel. Let Bitchat be the lesson that the protestors already know — the network is not the application, and the application is not the code. The network is the people who remember to fork.
