There's something quietly surreal about being recognized for contributing to open source on the same day you're standing in front of a room teaching someone else how to write their first Rust program.
I've had a few weeks to sit with that now.
BTrust recently named a group of â‚¿OSS Challenge alumni still finding ways to contribute to Bitcoin open source, months after the program officially ended. Seeing both @nkatha_kaburu and myself on that list was a generous acknowledgment, and a reminder that the end of a program is rarely the end of the story.
What made that day even more special was where we were when the post went live: standing side by side at Dada Hub, co-leading a two-day Rust workshop together. We weren't just passing through as alumni anymore. We were, in a very real way, part of what the pipeline produces when it actually works.
Two days, twelve sessions
That day at Dada Hub, we were running a Rust workshop: two days, twelve sessions, structured so that every concept was followed immediately by an exercise.
It was also the first of many. Dada Devs is running this as an ongoing series at Dada Hub, not a one-off, which matters more than it sounds like it should. One workshop teaches syntax. A series is how people actually stay.
Day 1: Foundations and Control Flow
Day 1 was all about breaking syntax barriers and unlearning sloppy habits. We focused on getting participants comfortable fighting and understanding the Rust compiler.
- Core concepts: Syntax basics, variables, integers, branching, loops, panics, and integer overflow.
-
Hands-on exercises: Participants worked through compiler errors and filled in
todo!()stubs until the test suites turned green, getting comfortable with a language that punishes carelessness but rewards precision. - The "Dust & Overflow" mini-exercises: Building simple CLI routines to parse numbers, calculate basic satoshi conversions, and manually check for dust limits before running into arithmetic panics.
Day 2: Memory Management and Ownership
Day 2 moved into the heart of Rust's guarantees: ownership and memory management
- Core concepts: The borrow checker, references, lifetimes, and automatic scope management.
-
Hands-on exercises: Participants debugged ownership conflicts, worked with mutable borrows, and read their way out of real compiler errors like
error[E0308]. - Capstone 1 (BTC/Sats Calculator): Building a robust input parser that converts BTC amounts into satoshis while handling dust threshold flags safely.
Explore the workshop materials: the full curriculum, slides, and exercise stubs live in our GitHub repository.
All these were small projects, but the right ones: the kind that quietly teach you why Rust insists on checked_add over plain arithmetic in financial code, because silent overflow is lost money. That's the whole ethos of the language in one sentence, and it's the same ethos this community has been building around, one study session and one PR at a time.
🎬 Watch the workshop highlights: our short recap video captures the
energy in the room at Dada Hub.
What the timing actually says
Looking back, what strikes me most isn't the recognition, it's the timing. Dada Devs said it plainly: open-source contributors aren't built overnight. What BTrust saw in us, the PRs, the tools, the continued contributions, didn't come from one program or one moment. It came from Mastering Bitcoin study sessions, GitHub fundamentals, peer reviews, late nights, and a community that kept investing long before any spotlight arrived.
That consistency is the thing worth naming. It is easy to celebrate a milestone. It is harder, and more important, to build the kind of environment where milestones become possible in the first place.
To the Dada Devs team, and to every community quietly doing this work before the world notices: this is what it looks like when the investment pays forward.
And to the participants from that workshop, still fighting the borrow checker and staring down error[E0308]: you're earlier in this story than you know. There are more of these coming. Come back for the next one.
Top comments (0)