I just launched my first Fiverr gig.
I am officially offering custom Python automation scripts and Telegram bot development.
You do not have to guess if I can deliver. My proof of work is already public. The multi-chain whale tracker I built to monitor Ethereum, Polygon, and Arbitrum in real-time serves as the live demo.
On-chain monitors, data pipelines, and custom alerts.
Let's build: https://t.co/MexjlUTCHA
#Python #Web3 #Automation
@meta_alchemist The fact that scammers had to resort to hijacking and mass-reporting just to compete tells you everything; they feared what $SPARK was becoming. Spark all the way.
Dropped my wallet, let's go!!
0x5eb48f79280ee316e416fa07fe3aecc807cb360c
@injective Definitely on. I have some questions about the new ambassadorship program; hope to get some answers. Also, would be really nice to learn about stablecoin adoption in AI agents
@injective That is pretty nice if you ask me. I guess widespread adoption is finally coming to Injective. And with this simple UX, literally anyone can navigate.
I just launched my first Fiverr gig.
I am officially offering custom Python automation scripts and Telegram bot development.
You do not have to guess if I can deliver. My proof of work is already public. The multi-chain whale tracker I built to monitor Ethereum, Polygon, and Arbitrum in real-time serves as the live demo.
On-chain monitors, data pipelines, and custom alerts.
Let's build: https://t.co/MexjlUTCHA
#Python #Web3 #Automation
Day 16 of building in Web3 from zero.
I automated the pipeline and hit my first major infrastructure bottleneck.
Here is today's technical breakdown:
Pipeline Automation: I set up GitHub Actions to trigger the whale fetcher every 12 seconds. The Render API stays live, and the database now refreshes continuously in the background.
Telegram Crash: I attempted to build a command menu for the bot (/set_filter, /start). It responded perfectly at first, but crashed the server after 30 minutes.
The Root Cause: An asyncio event loop conflict between the Flask API and the telegram.ext library.
The Fix: Decoupling the architecture. I am separating the Telegram bot into a standalone script, moving it to a different port, and shifting from polling to webhooks.
Building through failures.
Day 17 tomorrow.
Day 16 of building in Web3 from zero.
I automated the pipeline and hit my first major infrastructure bottleneck.
Here is today's technical breakdown:
Pipeline Automation: I set up GitHub Actions to trigger the whale fetcher every 12 seconds. The Render API stays live, and the database now refreshes continuously in the background.
Telegram Crash: I attempted to build a command menu for the bot (/set_filter, /start). It responded perfectly at first, but crashed the server after 30 minutes.
The Root Cause: An asyncio event loop conflict between the Flask API and the telegram.ext library.
The Fix: Decoupling the architecture. I am separating the Telegram bot into a standalone script, moving it to a different port, and shifting from polling to webhooks.
Building through failures.
Day 17 tomorrow.
Day 15 of building in Web3 from zero.
The multi-chain whale tracker is officially live in production.
Spent today debugging worker thread crashes, upgrading the infrastructure to Web3py v7, and deploying the Flask API to Render. The data is flowing.
The current live state:
~ Tracking $100K+ transfers across Ethereum, Polygon, and Arbitrum in real-time.
~ Dashboard auto-refreshes every 10 seconds with custom chain and amount filters.
~ Over 300 whales successfully logged and persisted via SQLite.
The open-source GitHub repo is linked in my bio. Multi-token support and Telegram bidirectional sync are coming up next.
Check out the dashboard here: https://t.co/Kc8SSDJPeX
Day 16 of building in Web3 from zero.
I automated the pipeline and hit my first major infrastructure bottleneck.
Here is today's technical breakdown:
Pipeline Automation: I set up GitHub Actions to trigger the whale fetcher every 12 seconds. The Render API stays live, and the database now refreshes continuously in the background.
Telegram Crash: I attempted to build a command menu for the bot (/set_filter, /start). It responded perfectly at first, but crashed the server after 30 minutes.
The Root Cause: An asyncio event loop conflict between the Flask API and the telegram.ext library.
The Fix: Decoupling the architecture. I am separating the Telegram bot into a standalone script, moving it to a different port, and shifting from polling to webhooks.
Building through failures.
Day 17 tomorrow.