I'm Collins. I build software from Enugu for people everywhere.
My first real project was a big one. In 2019 I joined a joint contract with UNICEF and the Enugu State Ministry of Education, designing and building an education website that over 2,000 schools went on to use.
Then came the apprenticeship years: full-stack PHP work at Oracus NG, followed by almost three years leading the frontend team at GridApe, an email marketing platform.
These days I wear three hats. I co-founded Boundless, I'm CTO at Threadify, and I'm building Useroutr. Most of my work lives where products meet money: ledgers, payment rails and smart contracts, and the screens people use to touch them.
Lately a lot of my curiosity goes into AI. I built QueryMaster, which lets you chat with your own files using OpenAI embeddings and Pinecone, with its backend on Zoho Catalyst functions. I've shipped pull requests to AI agents for Bitcoin SV and Starknet, and AI coding agents are now part of how I build every day.
Along the way I've written TypeScript, Rust, Cairo, PHP, Python, C++, Dart and plenty more. I also keep a foot in open source across the Stellar, Starknet and Bitcoin SV ecosystems. Off the clock you'll find me on a run (20K is my longest so far), dropping into Fortnite, or a few episodes deep into an anime.
Available for new projects
How I think about systems
Eight ideas I keep coming back to when I design software, and the work where you can see each one.
- Idempotency
- Exactly-once
- State machines
Money moves exactly once
Retries are a fact of life. Payment paths should be safe to run twice, with explicit states and deterministic logic, so a repeated job can never double-charge or double-credit.
- Double-entry
- Append-only logs
- Auditability
Ledgers only grow
Balances are derived, never edited. Entries are append-only and mistakes get compensating entries, so the history always adds up and every posting balances.
- Least privilege
- RBAC
- Blast radius
Least power, by default
Indexers that can read the chain but can't move money. Seven university roles that each see exactly what they should. If a part gets compromised, it can't do much.
- Multisig
- Signature verification
- DoS resistance
Trust the quorum
No single signer should approve a cross-chain message. Require two of three, reject duplicates, and refuse junk before doing anything expensive.
- Event-driven
- Background workers
- Retries
Queues absorb the chaos
Webhooks fail, chains stall and providers time out. Durable background jobs keep the work moving and make every step safe to retry.
- STRIDE
- Threat modelling
- Shift-left security
Threats belong in version control
A threat model in a diagram drifts. Next to the code, it gets reviewed in pull requests and enforced in CI like everything else.
- On-chain vs off-chain
- Smart contract design
Contracts only where they earn it
On-chain code is expensive to run and hard to change. Keep it for what has to be trustless, and run everything else off-chain.
What I work with
GitHub counts 25 languages across my 117 repos. Pick anything below to see where I've used it.
Languages
Systems & theory
Backend
AI
Frontend & mobile
Blockchain
Cloud & tooling
Auth & security
Experience
Seven years, six stops, one very long commit history.
- Dec 2024 — Now
Boundless
Co-founder
Nov 2023 — NowThreadify
Chief Technology Officer
Formerly Threadflow.
Sep 2023 — Apr 2026GridApe
Team Lead, Frontend
Led the frontend team building GridApe's dashboard.
- FApr 2026
Freelance
Web Developer

Sep 2019 — Mar 2022UNICEF & Enugu State Ministry of Educationcontract
Web Developer & Graphic Designer
One joint contract. Built and shipped an education website used by over 2,000 schools.
- OAug 2020 — Jan 2023
Oracus NG
Full-stack Web Developer Assistant
Off the clock
The part of the week with no pull requests.
Gaming
Fortnite
Drop in. Build fast. Repeat.
