Matt Corallo Urges Bitcoin Projects to Exit GitHub After Rust Lightning Ban

Matt Corallo and other senior Bitcoin developers are urging projects to migrate away from GitHub following what they characterize as a ban on Rust Lightning development. The movement advocates for self-hosted Forgejo solutions, citing GitHub's unreliable tracking, broken merge scripts, and hidden diffs as critical infrastructure concerns for decentralized projects.

The call for exodus from GitHub represents a significant tension point between Bitcoin's decentralization ethos and practical reliance on centralized infrastructure. Matt Corallo's advocacy reflects growing frustration within the developer community about GitHub's operational reliability and transparency, particularly for projects handling sensitive cryptographic code. The specific mention of broken merge scripts and hidden diffs suggests technical issues that could create security vulnerabilities or obscure critical changes in Bitcoin infrastructure, amplifying concerns about trusting a single entity with project governance.

This movement has deeper roots in Bitcoin's ideological commitment to decentralization. GitHub, owned by Microsoft since 2018, represents exactly the type of centralized chokepoint Bitcoin was designed to circumvent. Previous tensions over content moderation and platform policies have periodically surfaced concerns within the crypto community. The Rust Lightning controversy appears to have catalyzed existing frustrations into concrete action, with developers viewing self-hosted alternatives as more transparent and sustainable for long-term development.

ForGejo adoption would fundamentally alter how Bitcoin projects coordinate and maintain code. This shift has cascading implications: developers must invest resources in hosting infrastructure, projects lose GitHub's integration ecosystem and visibility, and the community fragments across multiple platforms. However, the decentralization trade-off aligns with Bitcoin's core principles and potentially strengthens independence from corporate influence.

Looking ahead, watch whether major projects like Bitcoin Core follow this migration or maintain dual repositories. The technical execution of alternative platforms and their security features will determine viability. This trend could accelerate if GitHub faces additional policy controversies, potentially fragmenting the developer ecosystem but reinforcing Bitcoin's commitment to censorship resistance.

• →Senior Bitcoin developers urge migration from GitHub to self-hosted Forgejo due to technical and operational concerns
• →Concerns include broken merge scripts, hidden diffs, and unreliable change tracking affecting code integrity
• →Movement reflects Bitcoin community's ideological commitment to decentralizing development infrastructure away from corporate platforms
• →Fragmentation across multiple platforms may increase operational overhead but strengthens independence from centralized control
• →Outcome depends on whether major projects adopt alternatives and whether Forgejo solutions prove technically robust and secure