BlindspotLab

Good products rarely fail for lack of quality. They fail because the right people never hear about them. I’m building Ìhìn(@viaihin): a creator network that carries products to the people they’re built for, through voices those people already trust. Ìhìn is Yorùbá for news.

“Football belongs to the fans.” After Ronaldo’s 2008 Ballon d’Or topped the fan vote, I built THE GOLDEN RUN ⚽🏆 a free football game inspired by his road to 1,000 goals. Score. Compete. Climb the rankings. Chase 1,000. Play: goldenrun.fun

Ronaldo or you? Who's going to hit the first 1000 goals? goldenrun.fun

BlindspotLab get a new home, and i want to share with you everything i worked on layer by layer. the first is the Hero, redesigned with new BlindspotLab wordmark, new H1, six ambient icons, and new content for the hero.

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

Alhamdulillah. First in my bloodline to own a registered SaaS company. BlindspotLab Limited is official. This used to be a dream. Today, it’s real. A boy from the trenches. Iware to the world. It’s up from here. ❤️‍🔥

work in progress...

I have corrected the render issue on the pdf.

A new year of life. Grateful to God for the journey, the lessons, and the grace. Happy birthday to me. 🎂

Builder credibility is still mostly self-reported. A resume, portfolio, or post can say what someone shipped, but a grant committee, DAO, or hiring manager still has to investigate the GitHub trail. Admon turns a builder's public GitHub activity into a verifiable record bound to their wallet on Monad. Connect GitHub, review the public commits, repositories, streaks, stars, and account history behind the record, then mint the proof on Monad Mainnet. The car is a shareable visual signature generated from those traits. The actual product is the transparent, portable build history behind it. Rarity rewards sustained building. It blends capped commit volume with consistency, public repository breadth, stars, and account history. Built with Next.js, Prisma, Supabase, Viem, Wagmi, GitHub OAuth, and a custom SVG renderer. Minting uses a short-lived EIP-712 authorization specific to the verified GitHub profile and connected wallet. Try it: admon.peerfix.dev Built on Monad Mainnet for @buildanythingso Spark Hackathon.

StackBrief began as stack.md, a small skill for understanding an unfamiliar repository. But the deeper problem was this: before changing code, you need to understand the architecture around the change. That became StackBrief. StackBrief is the architectural brief before a code change. It is not another README generator, start from a file you are about to touch. See the routes, services, databases, APIs, dependencies, local files, constraints, and unknowns around it. Documentation tells you what a system was. A developer changing a route needs to know what that change touches now. That context is usually scattered across source files, manifests, route handlers, shared services, and the memory of whoever last worked there. StackBrief runs locally. No API key. No hosted model. No repository code sent to a third party for analysis. Its findings point back to source evidence: file paths and line references whenever static analysis can establish them. At the center is stackbrief.json: a versioned, machine-readable map of the repository. Projects. Directories. Files. Imports. Exports. Routes. Services. Databases. External APIs. Dependencies. Everything else should build from that canonical knowledge. This is a deliberate product choice, I do not want StackBrief to produce confident-sounding answers with no trace back to the code. When it cannot prove something statically, it says so. Runtime configuration, feature flags, production traffic, and product judgement stay with the developer. Today, StackBrief can scan a repository and generate a concise brief before a planned file change or around real staged Git changes. It is framework-aware, including Next.js and Express-style routes, but it is not tied to one framework or one coding agent. I used (@ChatGPTapp) GPT-5.6 to challenge the product idea, pressure-test the architecture, refine module boundaries, and remove unnecessary complexity. I used Codex to accelerate implementation, refactoring, testing, packaging, documentation, and the website. AI accelerated the work. It did not replace engineering judgement. From a documentation skill to a local-first repository tool: I went hard on the details because I want this to become something developers use before real changes, not just something that looks good in a demo. 364 downloads is an early signal. Still building. Try StackBrief on a repository you already know: npx @blindspotlab/stackbrief scan npx @blindspotlab/stackbrief brief --file path/to/file.ts links in the cs.

#NewProfilePic Hey mutuals, since the last time I saw you on my TL, I moved from Alpha Caller to the Founder of an AI-native Studio(@BlindspotLab) , and I have built 30+ Products across AI, Dev tools, SaaS, and Web3. Now: AI Product Engineer, and System Architect; shipping at the edge of thoughts. Can I meet you?

Launch Capself today, not another AI chat app. A Personal Development Operating System. below is 5 free, three month subscription of founding member code. (check the comment 👇 )

I launched Capself today, not another chatbot a Personal Development Operating System. Here's why the world needed it 🧵

Somewhere right now, someone remembers the exact sound their IBM PC made on boot. someone else remembers the price tag. the year. the room it sat in. those memories deserve a wall. IBM is 115 today. Share yours: ibm115.vercel.app (did you notice the other animation, apart from the typewriter like animation?)

While everyone is building trading bots for the @Bitget_AI hackathon I built the infrastructure they'll need to structure their strategies first. MÓOU 谋 : → natural language → structured strategy → risk score → playbook output. + Public API at usemoou.xyz/api/v1/compile + Docs at usemoou.xyz/docs + Free. No key required. Get Started: usemoou.xyz Before you trade, 谋. #BitgetHackathon

I shipped MatchMind for @GoogleCloud x @MongoDB hackathon i n 3days World Cup 2026. AI football intelligence agent. But the real story isn't the stack. It's the moment I realized I had built theatre and labeled it intelligence. @devpost 🧵