🌉 I am excited to showcase the cross-chain token bridge I built!
The bridge connects Ethereum Sepolia ↔ Base Sepolia
✅ Lock on Ethereum → Mint on Base
✅ Burn on Base → Unlock on Ethereum
✅ Batch multiple actions into 1
Here’s the demo ⬇️
A simple testing checklist I now follow:
- Test on at least 2-3 mobile carriers in your target market
- Test on mobile hotspot (not WiFi)
What I learned:
- Always have a proxy strategy. If your users are global, some network somewhere will break your direct connection.
“Works on my machine” now has a new version:
“Works on my network.”
Spent hours debugging a “network bug” in my app’s closed testing release.
Turns out the app was fine.
JIO mobile network simply couldn’t reach my Railway backend, while WiFi worked perfectly.
I had to route my backend through a Cloudflare Worker proxy because JIO blocks Railway's IPs. The only path that worked was through a Cloudflare Worker.
Vite is great. But one thing I hate is how it doesn't show errors until you actually visit the page that imports the broken file.
It’s by design - unlike Webpack/Rollup, which scan the whole project upfront.
Fast dev vs early error detection - which do you prefer?
@w0rdgenerator I am still trying to process the view count!
Have been seeing this for a while, but this time thought of checking out the stats, and man...
How, just how!!!
Damn it....
Implemented the core feature of my app.
The v1 scope is to make the website offline first without any backend dependency.
Exploring dedicated workers, and index db.
I never thought rendering SVG would be this fun.
I started learning more on the SVG rendering concepts. Also building a small portfolio website to showcase the works.
@HunorBorbely - Man, you got the Goated tutorial on the concept. Loving every bit of the journey.