Code Warrior @dev_useee

You will encounter obstacles, but don’t let yourself be your first one.

What happens after a developer gets funded? The work changes in ways that are not always visible from the outside. There’s more time with difficult problems, rounds of maintainer feedback, more room to rethink contribution and stay with it. But what does that process look like from the developer’s side, and what changes when you have the time and support to stay with the work? Btrust’s Head of Engineering, Kelvin Isievwore, (@kelvinator05) and Grantees Rita Anene (@Camilla_rhi) and Oghenovo Usiwoma (@Eunovo9) share what happens after funding, from the work itself to the skills, relationships and independence that develop along the way. Read the full story here 👇🏾 x.com/btrustteam/sta…

Btrust @btrustteam

3 days ago

x.com/i/article/2105…

0 9 39 2K 3

Happy New Month everyone 🎉 Welcome to October, the first month of Q4. Q3 was a really productive quarter for me. I built, shipped, learned, and stayed consistent. Here are some highlights from Q3: 👉 Got a new workspace to improve my productivity 👉 Built and launched Coddle AI in public 👉 Scaled Coddle AI to 300+ users 👉 Built and completed Fastpay, a fintech mobile app 👉 Pitched successfully at a hackathon 👉 Stayed consistent with my 365 Days of Code 👉 Got new contracts to work on for different clients For Q4, the goal is simple: execute better, build more, and stay consistent. One thing I’ve learned about consistency is that you don’t always need motivation. Here are some tips: 1. Set clear goals. 2. Show up even when you don’t feel like it. 3. Make progress every day, even if it’s small. 4. And most importantly, don’t break the chain. Here’s to a productive Q4.

x.com/i/article/2104…

Building Infernos 🔥 permissionless open-model inference paid in sats. We’ve now got the core flow working: Request → 402 → Pay → Prove → Unlock → Infer ⚡ Rust/Axum node 🤖 Ollama open models 🔐 L402 + capability-gated authorization 💰 Session budgets + dynamic pricing

Code Warrior @dev_useee

a week ago

The frontend shell is now taking shape. Next up: connecting it to the Rust node and making the full protocol flow real. ⚡🦀 @bitshala_org @tech_lateef @Muhamma90584326 #lighting #bitcoin #opensource #Rust @devfolio

2 1 3 155 0

🌊 Streaming inference 🖥️ Next.js playground + WebLN integration We’ve also implemented the NWC Lightning backend, moving beyond Mock Lightning toward real sats. Next milestone: real Lightning E2E — pay an actual invoice, verify settlement through NWC, and unlock inference.

No accounts. No API keys. Pay for compute when you need it. 🔥 Building Infernos for #BOSSBattle2026 @bitshala_org @devfolio @tech_lateef @Muhamma90584326 @lightning #bitcoin #lighting #opensource.

4 weeks ago, I started building Fastpay, a fintech mobile app, in public. I’ve worked on fintech applications for companies before, so the idea of building another fintech app wasn’t because I wanted to learn what a wallet, card, or transfer flow looks like. I wanted something I could put in my portfolio that actually shows how I approach building a complete fintech product, from the mobile interface to the backend systems behind it. So I started Fastpay from scratch. The first few days were mostly about getting the foundation right: setting up the Flutter application, authentication, OTP verification, PIN sign-in, and the Go + Gin + PostgreSQL backend. Then the project started becoming much more interesting. I began building the actual financial flows one by one, though I focused on internal wallet infrastructure and mocked external payments: sending and requesting money, deposits, QR payments, cards, transactions, currency exchange, IBAN and SWIFT transfers, phone top-ups, and scheduled transfers. And with every feature, I had to think beyond the screen. How should the API handle the transaction? What happens if a request is sent twice? What data should the backend store? How should the mobile app respond to different states? How should authentication and authorization be handled? At the same time, I paid a lot of attention to the UX. I wanted Fastpay to feel better to use, not just function correctly. I spent time simplifying flows, reducing unnecessary steps, improving how information is presented, and making different parts of the app feel consistent. That has probably been one of the most valuable parts of building Fastpay: taking the fintech patterns I’ve already experienced and rethinking how I would design and build them myself. I’ve also built the less visible parts of the product: analytics, notifications, security and privacy settings, device and session history, personal details, notification preferences, language settings and other account management flows. I’ve been sharing the process almost every day for the last 4 weeks, documenting how the product has evolved feature by feature. Fastpay is still a portfolio project, and I’m not building it with the intention of launching it as a fintech company. I’m building it to push my engineering skills, experiment with different approaches, and have a project that represents the kind of software I’m capable of building, both technically and from a UX perspective. I’m wrapping up the Fastpay build this week, and I’m looking forward to sharing the final result and everything that went into building it. I’m Ahiakwo John, a fullstack web and mobile app developer with over 4 years of experience, passionate about using technology and AI to build useful products. I’m open to collaboration and opportunities.

Abraham (@abeeujah) is a developer based in Nigeria 🇳🇬, whose Bitcoin open-source journey began through @BitDevsKaduna. He built his knowledge through @ChaincodeLabs’ protocol development seminars, the @FreeRoutingAf Kaduna Lightning Developer Bootcamp, and Bitcoin Core Principles by @libdesatoshi. He also completed the 2026 BOSS Challenge and was featured by @btrust_builders as one of eleven African participants whose journeys stood out. With the starter grant, Abraham will focus on testing, protocol libraries, and developer tooling across rust-bitcoin and rust-lightning, strengthening the building blocks developers use for Bitcoin and Lightning applications.

The frontend shell is now taking shape. Next up: connecting it to the Rust node and making the full protocol flow real. ⚡🦀 @bitshala_org @tech_lateef @Muhamma90584326 #lighting #bitcoin #opensource #Rust @devfolio

Been heads down building Infernos 🔥 We're building permissionless open-model inference paid in sats. Ask → 402 → Pay → Prove → Unlock → Infer Lightning payments, L402 authorization, capability-based access, bounded session budgets, and privacy by default.

Code Warrior @dev_useee

2 weeks ago

Exactly payment isn’t just billing here , it’s the authorization primitive. pay → preimage → prove → unlock the next step. That’s what makes L402 interesting for machine-to-machine workflows beyond just inference.

0 0 1 103 0

be there.

BitDevs Zaria @bitdevszaria

a week ago

Join us for the first Bitcoin Developers Meetup in Zaria, a space for developers, builders, and Bitcoin enthusiasts to connect, learn, and explore the technology powering a new financial and digital frontier. Register here: luma.com/zc84r9wn #Bitcoin #BitDevsZaria

1 2 6 843 0

x.com/i/article/2103…

We’re excited to announce the Q3 2026 Btrust developer grant recipients. 🚀 Ten Bitcoin open-source developers are receiving support: five starter grant recipients and five long-term open-source cohort members. This quarter also marks an important first: Btrust developer grants are going directly to developers outside Africa. Through our recent expansion of long-term grants across the Global Majority, we’re now supporting developers in Brazil 🇧🇷 and India 🇮🇳. Their work, alongside that of recipients in Nigeria 🇳🇬 and Kenya 🇰🇪, spans @bitcoincoreorg, mining ⛏️ infrastructure, Lightning⚡, wallet libraries, and privacy-preserving payments. Meet the recipients and learn about their work:

Btrust @btrustteam

2 weeks ago

x.com/i/article/2102…

2 24 64 8K 6

100 days of code to go 🥳 Consistency.

Ahiakwo John @ahiakwo_john

2 weeks ago

What did I work on Fastpay today? Today is Day 265 of 365 Days of Code. Today, I worked on the Analytics screen, giving users a better view of their income and spending activity. 👉 Added Expenses and Income analytics with totals, transaction counts, category counts, and tag

2 1 10 548 0