GitHub has been the home to Bitcoin Core and many other software projects in the Bitcoin industry for over a decade, but it was not the first collaborative version control platform to host the digital currency’s code, and it may not be the last.
Recent performance issues in GitHub have triggered a new wave of criticisms of the platform, reviving old concerns and dissatisfactions with its design and reliability. Matt Corallo, one of the longest-acting Bitcoin core contributors, took to X recently to announce the decision to migrate off the platform, not Bitcoin core’s code base yet, but the Rust Lightning dev kit, a code base he is closely involved with.
In an X quote retweet thread that goes back through multiple viral posts complaining about the platform, Corallo said, “our org currently has no CI (quality testing processes) because GitHub wrongly flagged a contributor, not an admin or maintainer, just someone new who opened a few pull requests. We’ve escalated it through corporate account managers and still basically nothing.” A week or so later, he added: “GitHub has decided our open-source project has been permanently banned with no explanation and no option to appeal, pointing to a ToS that clearly does not cover anything we’ve ever done.” – “I guess it’s time for Bitcoin projects to leave GitHub.”
The banned contributor appears to be Luis Schwab, who replied “I’ve had my account banned twice within a week “by mistake”. Relying on GitHub’s goodwill is not a good long term strategy.” Multiple other Bitcoin and crypto engineers replied with similar experiences, saying they too had migrated off the platform or been banned without recourse, like Roman Storm, who replied, “In 2022, GitHub locked my account over Tornado Cash sanctions. I’m a US citizen. They told me to get an OFAC license to access my own account. The sanctions were later ruled unlawful and overturned. The account is still locked. I’ve filed ticket after ticket – now they don’t even respond. Abolish GitHub.”
Corallo blames the AI wave on the recent mass banning of accounts and increasingly aggressive measures taken by the massive platform. The popularity of vibe coding has brought a new wave of attention, amateur projects and automated bot-like behavior to the already overburdened platform. Today, GitHub claims to host over 420 million repositories and over 4 million organizations worldwide. GitHub was acquired by Microsoft in 2018, which, to some, also explains its steady downfall.
Even Andrew Poelstra, another senior Bitcoin Core and Rust Lightning contributor, with over a decade of experience in the industry, wrote a devastating take-down of GitHub, defending the decision to migrate. “This site has an overwhelming amount of LLM slop, and they have no intention of stopping it, though they did write this insane blog post taking credit for FOSS as a way of acknowledging the problem,” he began, continuing to explain that the merging of code into the master repositories had now been “broken for several days.” This caused cascading issues that confused the “merge script,” a security program that makes sure updates to a code base are done properly.
The bug meant that tracking and merging pull requests — contributions from other developers — didn’t work as expected. “Tracking PRs is the one thing GitHub is supposed to do, and it’s broken. It’s no longer more convenient to stay here than to leave, which was the only reason we’ve stayed so long,” Poelstra continued. “The usual problems where diffs and comments are hidden, the site being slow and unreliable, the permissions model being insane and broken, the lock-in, the crappy and slow API, etc. [All of] which we could live with if the basic functionality worked, but it doesn’t.”
As a result, the next destination for Rust Lightning and perhaps other Bitcoin projects in the industry may be Forgejo, a lightweight GitHub alternative optimized towards self-hosting and high agency projects. Corallo confirmed to Bitcoin Magazine that “rust-bitcoin already started migrating to git.rust-bitcoin.org” and Rust Lightning would follow.
The repositories will likely continue to host a copy on GitHub, though no public statements have been made about any kind of long-term mirroring strategy of the code base, meaning it will eventually just live on their own site.