Code Warrior

Mobile Engineer Flutter & Dart || Bitcoin and LIghting || Opensource Contributor.

[Code Warrior @dev_useee]

Hello everyone 👋
My name is Usman Umar Garba I’m a 3rd-year Computer Engineering student and a Mobile Engineer (Flutter), actively building cross-platform applications.
I’m currently expanding into backend development with Python (APIs) and exploring Bitcoin &

[HUSTEEMAH @0xhusteem]

Join us for the upcoming Bitdevs meetup.
Come with your questions, come curious.

[Abubakar Nur Khalil @ihate1999]

You are not behind.

You’re just drowning in the list of things you know you need to do.

Lock in, anon.

[Abubakar Nur Khalil @ihate1999]

In my latest for @ForbesCrypto, I cover the recent stream of bitcoin hacks, the role of accountability and why users still flock to exchanges and ETFs

https://t.co/ukVcFDW1ZU

[Ahiakwo John @ahiakwo_john]

How I stay consistent with my 365 Days of Code challenge.

A lot of people have been asking me how I manage to show up every day, write code, build projects, and share updates everyday.

Here’s what has helped me:

1. I don’t wait for motivation.

Some days I’m excited to code. Other days, I just want to rest. I’ve learned not to depend on how I feel. I show up regardless.

2. I work on real projects.

I’m not just coding for the sake of completing the challenge. I work on products, experiment with new technologies, fix bugs, and build features. Having something meaningful to work on makes it easier to keep going.

3. I document my progress.

Sharing what I’m building publicly gives me a way to track my growth. When I look back at older posts, I can see how far I’ve come, and that motivates me to keep going.

4. I don’t try to do everything in one day.

I don’t just wake up and start coding randomly. I create a plan for what I want to build and break it down into features I can implement step by step. This gives me direction and helps me stay focused.

5. I focus on showing up, not being perfect.

There are days when things don’t go as planned. I’ve learned that consistency isn’t about having a perfect routine; it’s about finding a way to keep moving forward.

I’m currently on this journey, and one thing I’ve learned is that consistency becomes easier when you build a system around it instead of relying on motivation alone.

You don’t have to do something extraordinary every day. Just make sure you’re moving forward.

If you’re working on a long-term goal, start today. Document your progress, stay accountable, and keep going.

I’m currently building Coddle Learn, an open source platform for developers and techies to learn, practice and build their portfolio.

[GDG KADUNA CITY #DevfestKaduna2026 @gdg_kaduna]

Meet our dedicated bitcoin track mentors @200OKDeveloper @damola21mm @M_Aliyu_Shehu @Thevelopher @btrustteam @Geektutor @wtmkadunacity @WTMKadunaSouth @BitDevsKaduna #DevFest2026 #Devfest26 #DevFest #DevFestKaduna

[Btrust @btrustteam]

What goes into building a stronger Bitcoin ecosystem, beyond the code itself?

Our conversations with @StephTitcombe, @Murugi___ and @ihate1999 took us behind different parts of Btrust's work, from creating pathways for developers to grow, to communicating the work happening across the ecosystem and the vision guiding it all.

Each conversation offered a different perspective on what it takes to support the people building Bitcoin's future.

[BitDevs Zaria @bitdevszaria]

Big congratulations to @dev_useee and @Muhamma90584326 for emerging as winners of the Machine Money Track at Boss Battle 2026! 🎉👏

Their project, INFERNOS, showcases the power of permissionless AI inference powered by Bitcoin Lightning. ⚡₿
Congratulations to the winners

[Code Warrior @dev_useee]

@bitshala_org @btrust_builders https://t.co/RIdSUyXcpk. @tech_lateef @M_Aliyu_Shehu @Thevelopher @Muhamma90584326 @lightning

[Code Warrior @dev_useee]

🇳🇬🏆 We won the Machine Money Track at BOSS Battle 2026!
Huge thanks to @bitshala_org, @btrust_builders the organizers, judges, and everyone who supported us. We built Infernos — permissionless AI inference paid with Bitcoin Lightning. Here's the story behind our journey 👇 📝

[Bitshala @bitshala_org]

Next up, the Machine Money Track: Bitcoin + AI 🏆

The winner is Infernos by @dev_useee & team from Nigeria 🇳🇬

Permission-less AI inference, paid with Lightning.

Imagine being able to access AI compute and pay for it in sats, without needing anyone’s permission. That’s what makes projects like this exciting.

Congratulations to the Team! 🧡

🔗 https://t.co/IoZYR7wdyI

[GDG Ado-Ekiti | #DevFestAdoEkiti @gdgadoekiti]

@AdewumiSaheedA2 showed how agentic apps can transform manual invoice workflows with autonomous agents, powered by ADK, MCP, and AG-UI.

#DevFestAdoEkiti #DevFest2026 #GDGAdoEkiti

[Code Warrior @dev_useee]

Can open AI compute become a permissionless economic resource?
We don't think we've solved the whole problem.
But we built a working foundation for exploring it.
Permissionless AI Compute. Pay in Sats. Earn from Compute.
⚡🤖🇳🇬
#Bitcoin #Lightning #AI @bitshala_org @tech_lateef

[Code Warrior @dev_useee]

We fixed it by making the mock Lightning flow behave much more like the real protocol:
Invoice → payment hash → preimage → SHA-256 verification → settlement → L402 authorization
That forced us to separate:
Payment
from
Proof
from
Authorization.

[Code Warrior @dev_useee]

And the project is open source.
You can inspect the implementation, architecture, tests and development history here:
https://t.co/gTEIpWVdVq
We'd love people to read it, break it, review it and tell us what we got wrong.

[Code Warrior @dev_useee]

At one point our CLI could receive an authorization challenge, but the server rejected the payment proof.
The problem?
Our mock payment flow wasn't modelling the cryptographic relationship between the invoice and preimage correctly.

[Code Warrior @dev_useee]

What if AI compute could become a permissionless service that machines can pay for directly with Bitcoin?
Over the last few weeks, we tried to build exactly that.
Introducing Infernos.
Permissionless AI Compute. Pay in Sats. Earn from Compute. ⚡🤖
🧵👇

[Code Warrior @dev_useee]

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]

SDK + CLI
We also built the Lightning backend around an abstraction so different Lightning environments can be integrated without changing the core inference gateway.
The interesting part wasn't returning a 402.
The hard part was making the payment actually mean something.

[Code Warrior @dev_useee]

The payment proof unlocks a bounded capability. Under the hood, Infernos is built with:
• Rust
• Axum + Tokio
• Lightning/L402
• Open-weight models
• Ollama
• OpenAI-compatible APIs
• Session budgets
• Capability-based authorization
• Next.js playground
• Rust caller

[Code Warrior @dev_useee]

The caller pays only when it wants to use the compute.
Request → HTTP 402 → Lightning payment → Payment proof → Capability verification → Inference
We use L402 to connect the payment to authorization.
Payment isn't just a billing event.