Today we shipped Capself; a Personal Development Operating System from Blindspotlab. The problem we kept seeing: people use AI, journals, habit apps, and goal trackers in isolation. 1/3

Dear BSL family, we've a new home. We've been thinking about giving BlindspotLab a new home since Sept 14th, when we incorporated our company with CAC. But due to some circumstances, our founder got busy with a client project, fell sick, and the doctor said he had to rest because he had been working without enough rest. That's what caused the delay in the new BlindspotLab design. But here it is now. Restructured, redesigned, and on a new host. Cheers to new beginnings! BlindspotLab, 25/09/2026

hello everyone, we’re migrating from our former host that’s vercel to cloudflare, and our website will not be online for some minutes. thank you BlindspotLab 21/09/2026

i think i can finally write about this. aitax.fun was my first paid client build as a developer. i met the project as a rough idea. no finished architecture. no complete game. just the direction of what the founder wanted to build. my job was to turn it into something that actually worked end to end. the product became a PVP Bitcoin UP/DOWN game on Robinhood Chain. so I built the frontend, smart contracts, the chainlink data streams integration, round automation, settlement, claims, refunds, Burn Accumulator, admin dashboard, health monitoring, indexing, wallet flows, production deployment, all connected together, and working end to end. but getting there was not smooth. one of the hardest moments came after we went live and rounds kept refunding instead of settling. at first, it looked like an oracle or RPC availability problem. it wasn't. i kept digging. the oracle's priceAt(boundary) function was correctly reverting with ReportUnavailable() when the required historical BTC boundary had not been stored yet. that revert was supposed to tell our coordinator: "fetch the authenticated chainlink historical report, submit it, then continue settlement." but our custom RPC transport was swallowing the EVM revert data. instead of seeing the exact ReportUnavailable() signal, the coordinator saw a generic RpcRequestError. so it treated the situation like an RPC failure. the chainlink report retrieval path never ran. and the round eventually reached its refund deadline. we watched multiple rounds refund. that part hurt. this was mainnet. people were using something I built. every failed settlement felt very different from a failing local test. i was tired, at some point, i was genuinely scared that I had built something that wasn't going to work reliably. but I kept tracing it: - revert bytes - RPC responses - oracle boundaries - coordinator state - retry timing - transaction receipts Until the actual failure became obvious: i fixed the transport to preserve EVM revert data. i matched the exact oracle failure condition instead of treating every failure the same. i changed failed settlement retries from the old long delay to a much faster recovery path. i added stage-aware error reporting. i hardened transaction persistence and recovery. then the lifecycle started doing what it was designed to do: entry → lock → oracle → settlement → claim → burn. that experience changed how I think about building production systems. a successful build is not when the UI looks finished, it is not when the contract compiles, it is not even when everything passes locally, it is when the full system survives reality. - networks fail, - providers time out, - transactions get weird, - external services behave differently from mocks, the important part is whether you can understand the system deeply enough to find the real failure instead of patching the symptom. i also built the operational side so the owner doesn't need to live inside Blockscout. contract parameters can be managed from the admin frontend with the owner wallet. settlement is automated. lifecycle functions remain permissionless. the BurnAccumulator is visible to everyone, and once its threshold is reached, anyone can trigger the burn. the contracts remain the source of truth. this started as my first client gig. there were moments I was tired. moments I was scared. moments I wondered whether i had taken on too much. but i learned more from shipping this system than I would have learned from another ten unfinished side projects. i met AITAX as an idea. now it is a working product. and after all those rounds that refused to settle... we're finally UP. 🚀

Hi, I’m Mojeeb, 29. AI native developer, product engineer, consultant and solo founder from Nigeria Spending most of my time building SaaS, AI Agent, Developer tools, and Productivity Apps. Looking to connect with VCs, Investors, founders and teams that need a cracked AI product engineer who ship at the edge of thought.

I'm still building with time everything will consolidate. building @BlindspotLab, an AI Native studio who helps founders build products from rough ideas. building arcapush.com a discovery platform for solo builders, and idea guys who ship everyday. building dearly.icu a greeting platform, who help you curate a well thought message for your loved ones building whate.app a meal intelligence, that help families, students, gym goers, nursing mother, tech entrepreneur, 9 to 5/entrepreneur cook without the decision fatigue of what to eat, the age long problem in the world. building capself.co a personal development operating system, that helps becoming the capable self, the only OS in the world that's not training with your data, rather than yourself. building tryrevel.xyz an SEO/product readiness audit, that let's you know where your competitors are ahead of you, and what you can work on. to solidify everything, i just registered my company "BlindspotLab" with the legal name "Blindspotlab Limited" i believe one or two or more of these products will make it to market with big audience in months, and years to come. I'm Mojeeb Titilayo, AI Native developer, product engineer, and strategist, building from the Federal Republic of Nigeria. BlindspotLab, 17/09/2026

Hello from you US to YOU!