Bashiru Muyideen L
682 posts

Bashiru Muyideen L
@firstbml1
On-chain Researcher & ML Engineer Whale flows • Market intent • Liquidation risk Python | SQL | ML | Data pipelines Building whale-based price & risk sign
Lagos, Nigeria Katılım Ağustos 2015
730 Takip Edilen127 Takipçiler

@firstbml1 @AnalyticSages This a really great project boss.
English

@emkay_crypt1 @Somnia_Network Thank you boss. We will keep building useful products
English

Gm gm..
Q1 2026 is already gone.
Just like that.
While most people spent it looking for jobs opportunities that ghosted them, I did something different.
I stopped waiting for job offers and built hollowscan.com (live on @Apple & @GooglePlay Stores) instead, a product/business generating real monthly revenue on top of everything else I earn in tech.
Fr..
You've got skills. The question is what you're building with them?
Here’s an update btw..😉
🚨BR€AKING: AI can now build you a business in 24 hours.
Here are 8 insane Claude prompts to turn any idea into income in 2026 👇 (Save for later)
1. THE BUSINESS IDEA GENERATOR
"I have $500 and 10 hours per week. Analyze current market gaps, my skills in [your skills], and generate 5 business ideas I could launch this month. Include startup costs, timeline, and first revenue projections."
2. THE COMPETITOR DESTROYER
"Act as a market analyst. Research [competitor name] and identify 3 weaknesses in their offering. Then create a differentiation strategy I could execute with limited budget to capture their customers."
3. THE LANDING PAGE ARCHITECT
"Build a complete landing page copy for [your business idea]. Include hero headline, 3 benefit sections, social proof framework, FAQ, and 5 different CTA variations. Optimize for conversion psychology."
4. THE PRICING STRATEGIST
"Analyze pricing models in [your industry]. Calculate optimal price points based on value perception, competitor pricing, and target customer willingness to pay. Include 3 tier structures with psychological anchoring."
5. THE TRAFFIC GENERATOR
"Create a 90-day traffic acquisition strategy for [your business]. Include organic tactics, paid strategies, content distribution, and community building. Prioritize by cost-effectiveness and scalability."
6. THE CONTENT MACHINE
"Create a 30-day content calendar for [your business]. Include post ideas, hooks, optimal posting times, and content types (carousel, thread, video). Focus on viral potential and audience growth."
7. THE CUSTOMER AVATAR CREATOR
"Build a detailed customer avatar for [your business]. Include demographics, psychographics, pain points, desires, online behavior, and buying triggers. Use this to inform all marketing decisions."
8. THE SCALE BLUEPRINT
"I'm making $X per month with [your business]. Create a detailed plan to 3x revenue in 90 days. Include product expansion, pricing optimization, team building, and systems implementation."
I hope you've found this helpful.
Kindly like, repost and follow me @defi__josh for more.
Let's make Q2 2026 even better 😉

English

I also track:
• Top wallet concentration
• Median vs average whale size
• Shock score (network impact after whale events)
This helps separate real activity vs noise.
Built using Somnia’s reactivity real-time event layer:
@SomniaDevs
community: @AnalyticSages
English

@claudeai Who wants to do this in Lagos with me?
#ClaudeAILagos Meetup
English

We're launching Claude Community Ambassadors. Lead local meetups, bring builders together, and partner with our team.
Open to any background, anywhere in the world.
Apply: claude.com/community/amba…

English

@defi__josh @smartymetrics @0xTobey @_angelnath @FaveDigitalsHQ @ModestusOkoye @d_h_a_r_c @chris_onchain @ndii_ekanem @Pharmkev @ArojieEvans Option 2 as it is.
English

You have two choices today.
Choice 1️⃣:
Scroll the timeline.
Watch what everyone else is building.
Keep taking courses (paid or free).
Feel productive while learning.
Wait until a gig/opportunity shows up.
Say “I’ll start when the right opportunity comes.”
Day/week/month/year ends.
Choice 2️⃣:
Open your PC.
Apply what you learned (or what you're currently learning).
Write a query on @dune.
Generate a simple @FastAPI Python script.
Push a commit on @github.
Deploy on @Railway.
Vibecode a simple web app using @v0 that consumes the API you built.
Break things.
Fix errors.
Ship something small/simple.
Use AI tools to help you move faster.
No gig yet?
No problem.
Think of a SaaS idea.
A small tool.
A problem you can solve.
(Note: keep it simple and realistic… especially if you're just starting out.)
Use AI (e.g @claudeai) intelligently to help you generate ideas and actionable steps based on your interests.
==================================
Both paths take the same few hours.
The difference?
One keeps you waiting.
The other creates proof of work.
Most people stay stuck in learning mode.
But opportunities don’t check what courses you took.
They check:
Your GitHub heatmap
Your dashboards / portfolios
Your projects
...
So again…
1️⃣ or 2️⃣
Choose wisely 😉
.
Gm Gm ☀️
Happy new week ✨️

English

@defi__josh @Dune_Africa @AnalystLab_HQ @0xTobey @agaperste @arno39 @hagaetc @thecaptncrunch @mewwts @SamuelXeus @IamFantasy__ Good job. Keep building
English

Gm gm ☀️
I’m in a team that doesn’t joke with me at all.
I joined them as a Data Wizard. But because of how broad I am across Data, Web/Software/App development, Backend Development, DevOps and Infrastructure systems… I’ve gradually become their go-to Dev guy too.
I recently launched a mobile app (iOS & Android) I built from scratch 😇
Apart from my sweet mobile app synced with Telegram bot
t.me/Hollowscan_bot
(I and @smartymetrics launched x.com/i/status/20160… — he also contributed massively to the mobile build too. Guy is a genius.)
that’s currently live on Apple and Google PlayStore…
I’ve been connected with top UK clients. One of them even contracted me for £4,000 for a gig similar to what I built for HollowScan. You can check the app yourself 😉
Now here’s where this gets interesting…
==============================
📍Unpopular truth for aspiring Web3/Data analysts
==============================
Another generic copy-paste DEX dashboard on @Dune will not make you stand out.
You know the ones…
• same Uniswap volume charts
• same wallet count metrics
• same TVL trend lines
• same “top traders” tables
• same conclusions everyone already knows
Recruiters and serious builders have seen it many times.
And what it sometimes signals, fair or not:
❌ tutorial-only learning
❌ heavy dependency on existing dashboards
❌ little original thinking
❌ low exposure to real protocol questions
And no… the problem is not using tutorials (on @AnalyticSages for example) to learn Dune or project building.
The problem is stopping there.
Because real Web3 analytics work looks very different.
When I moved from tutorial dashboards to real analytics and real systems, I had to learn things tutorials never showed:
• decoding raw onchain activity properly
• sourcing complex tables across multiple chains
• defining metrics that actually answer business questions
• building reusable dependency-driven queries
• optimizing heavy queries so dashboards don’t break
• creating data pipelines other dashboards rely on
• connecting analytics to real products and real users
• thinking about behavior, incentives, and protocol health
That’s how I moved from “learning Dune” to building serious dashboards… to shipping full analytics apps… to landing real gigs and clients.
Even HollowScan wasn’t about titles.
It was about solving a real problem: people missing valuable deals because information was scattered and slow to act on.
So we built:
• real-time data sourcing
• backend automation
• structured pipelines
• Telegram delivery systems
• mobile app interfaces synced with data logic
No fancy titles. Just clear problem solving.
And this is the part many beginners miss:
Teams don’t hire dashboards. They trust people who can ask better questions, build real systems, and produce insights that drive action.
So if you’re early in your Dune/Web3 analytics path this month:
✔ learn from tutorials first
✔ but don’t stay there too long
✔ pick a real protocol and ask real questions
✔ analyze behavior, not just volume
✔ define new metrics
✔ build reusable logic
✔ publish original work consistently
That shift is what changes everything.
Fr…
Your Dune/GitHub profile is not a collection of tutorials.
It’s proof that you can think, build, and solve real Web3 problems end to end. 💯

English

@defi__josh @arno39 @hagaetc @mewwts @filippoarman @thecaptncrunch @agaperste @0xTobey @Dune_Africa @Adam_Tehc @ndii_ekanem Solving problems and not title chasing. On point
English

Gm gm ☀️
📍Stop chasing job titles. Start chasing problems to solve. 👌
This is something I wish I understood earlier.
When I was breaking into data and Web3, titles messed with my head. On my bio, I wanted to write all these 😅
↘︎ Data Analyst
↘︎ Blockchain Analyst
↘︎ ML Engineer
↘︎ Analytics Engineer
↘︎ Researcher
↘︎ Full-stack data dev etc…
But omoh… it’s too much noise.
@smartymetrics and I recently launched a SaaS linked to a TG bot
t.me/Hollowscan_bot
It sources sweet products at relatively cheap prices from popular stores in the UK, USA, and Canada like:
✔ Amazon
✔ eBay
✔ Keepa
✔ Argos
✔ Lewis
✔ Smyths
✔ Curry’s
✔ Miniso
✔ Waitrose
✔ Tesco
✔ Costco
✔ Sainsbury’s
✔ Hamleys
✔ Card Factory
✔ TG Jones
✔ Hobby Craft
… and several others.
And it drops:
• ⚡️ Real-time notifications
• 🖼️ Product images
• 🔗 Direct action links
• 📊 Full stock and price data
straight on Telegram.
Built using ethical hacking, dev ops, DB management, Python, and several other technical skills.
But here’s the funny part.
When we were building this, we didn’t wake up and say
“Let’s build a Data Analyst thing”
or
“Let’s act like ML Engineers today.”
We asked one simple question:
📍“What problem are we actually solving?”📍
And the problem was clear.
People were missing good deals
because information was scattered, delayed, or hard to act on.
So the work became:
• pulling data from multiple sources reliably
• cleaning and structuring it for real-time use
• designing logic that filters noise from signal
• building systems that don’t break when usage spikes
• pushing insights where users already live (Telegram)
• making actions frictionless, not fancy
No fancy titles. Just problem solving.
That’s when it clicked for me.
Most roles in data and Web3 aren’t defined by titles.
They’re defined by problems:
• Is this about surfacing insight from messy data?
• Is it about automation and speed?
• Is it about decision support?
• Is it about building systems that scale and stay reliable?
Once you see that, the noise disappears.
You stop worrying about what to call yourself.
And you start getting clear on what you can solve end to end.
That clarity compounds.
It’s the same mindset I use on @Dune.
The same thinking behind analytics apps.
The same thinking behind ML pipelines.
And now, the same thinking behind this SaaS.
And like @SamuelXeus said at @blockfestafrica:
“If you can solve a real problem, someone will pay for it.”
This SaaS is already doing that 😋
Not because of titles.
But because it solves something real, consistently.
That’s the lesson I wish more people learned earlier.
Don’t stress about what to call yourself.
Focus on what breaks.
Focus on what’s slow.
Focus on what people complain about.
Then build systems that fix it.
Fr…
Titles didn’t get us here.
Clean thinking did 😉

English

@defi__josh @Dune @Dune_Africa @SamuelXeus @0xTobey @AnalystLab_HQ @Adam_Tehc @arno39 @filippoarman @hagaetc @mewwts @Al_Grigor You skpped Excel and DAXs part
English

Everyone wants to be a Web3 Data Wizard— and the roadmap looks simple:
➡️ Learn SQL + Python
➡️ Build @Dune dashboards / Web apps
➡️ Do some projects
➡️ Apply for roles
➡️ Get hired… right?
But here’s the part no one really talks about:
The real work looks like this:
✅ Mastering SQL until it stops being “queries” and becomes logic
✅ Working directly with raw blockchain data (not cleaned datasets) like RPC nodes, or even using @envio_indexer for example, to index this data directly
✅ Turning transactions and on-chain activities into real user behavior that clearly answers questions like: "what happened?", "why did it happened?", "what could happen next?" and "what action can taken from the insights?"
✅ Writing reusable, dependency-driven queries on Dune
✅ Building data pipelines that other dashboards/apps rely on
✅ Using Python for automation, modeling, and backend logic
✅ Knowing enough ML to predict churn, not just describe activity
✅ Defining metrics clearly so they don’t change every week
✅ Shipping dashboards and full analytics apps
✅ Thinking in systems, not one-off charts
✅ Publishing work consistently, even when traction is quiet
✅ Weeks of silence after sharing links
✅ Rejections, ignored DMs, missed callbacks
✅ Then… one day… the work starts speaking for you 🎯
Omoh..in reality, the road nor straight..
The journey is really tough..
📌but here's a Reminder:
No shortcuts. Just consistency, clean thinking, and building things that actually run.
Gm ☀️

English





