Our First Annual Report
What did year one of 2140 look like?
A little over a year ago, we introduced ourselves to the world with a simple promise: to support long-term Bitcoin development by giving talented developers the stability and community they deserve. Today, we’re sharing our 2025 Annual Report, a full account of how we’ve spent our first year turning that promise into practice.
So what did year one look like?
We opened our Amsterdam office, welcomed our first team members (Rob, Novo, Sadiq, and Sergi), and started building the collaborative hub we’d envisioned from the start. Our team dove into some of Bitcoin’s most important open technical challenges: Silent Payments integration in Bitcoin Core and libsecp256k1, the SwiftSync prototype, Kyoto (a BIP-158 light client), a new mining interface for Core, and ongoing work on libmultiprocess and libbitcoinkernel. We hosted a Silent Payments gathering that brought contributors from around the world to Amsterdam, and launched regular show-and-tell events to keep the broader community connected to our work.
It wasn’t without growing pains. Navigating work visas, onboarding across borders, and managing the operational complexity of a young organization all took more time and energy than we anticipated. We’ve documented those lessons honestly in the report, because we believe other organizations in this space can learn from them too.
Publishing this report matters to us. We’re a foundation built on trust, and the developers, funders, and community members who believe in what we’re doing deserve to see exactly how we’ve used the support we’ve received. That means transparency about what worked and what we’d do differently. We hope this report can serve as a blueprint for others looking to replicate this model and build similar Bitcoin development hubs elsewhere - more 2140-style collectives means a more geographically distributed, resilient, and sustainable Bitcoin development ecosystem.
We’re proud of what we’ve built, and we’re grateful to everyone who made it possible.
You can read the full report here: