The wallet connection war
Real-time analytics for a Solana liquidity protocol, built with Astro, Vue, and Anchor program integrations.
"It connects now. Nobody touch anything."
$2M+ TVL tracked
98% uptime
Avik Banik / full-stack dev
I build web apps, dashboards, weird experiments, and occasionally my own problems.
Full-stack dev from Kolkata. I work with Astro, Vue, Web3, Cloudflare, and whatever else the project threatens me with.
avik.dev/control-panel live
$ whoami
builder of useful interfaces, strange prototypes, and deploys that behave.
current task shipping
bugs found before users
wallet popup negotiating
deploy status still standing
03:14 pushed fix with suspicious confidence
03:18 Cloudflare said yes
03:21 opened chai refill ticket
ASTRO - VUE - CLOUDFLARE - WEB3 - DASHBOARDS - CHAOS MANAGEMENT -
KOLKATA - SHIPPING -
What I Do
Stuff people usually ask me to fix/build
Web apps that stop being vague ideas
Product flows, dashboards, admin panels, and frontends that need to feel fast without becoming a pile of mystery state.
- Astro
- Vue
- React
Web3 integrations with fewer jump scares
Wallet flows, protocol dashboards, token/NFT experiences, and the UI glue around contracts where users can actually understand what is happening.
- Wallets
- DeFi
- NFTs
Deployments that do not need a ritual
Cloudflare, workers, databases, build pipelines, and performance cleanup so the thing keeps working after the exciting demo.
- Cloudflare
- CI/CD
- Workers
Technical direction before the sprint gets weird
Scope, architecture, prototypes, and product cleanup for teams that need a clear path from “we should build this” to “it is live.”
- Architecture
- Prototypes
- MVPs
Selected Work
Things shipped without deleting production
Tiny app, suspiciously useful
Custom marketplace experience with authentication, gasless transactions, and a mint flow that got out of the user's way.
"I did not think this was possible this week."
10K+ mints
<1s mint time
The one with too many charts
Real-time analytics dashboard processing high-volume events with edge deployment and a calmer interface for repeat daily use.
"We do not talk about the first spreadsheet."
250ms p95 latency
99.9% availability
How It Usually Goes
Small process, fewer surprises
01
Untangle
Goals, constraints, users, scary edge cases, and what matters now.
-
02
Shape
Prototype the flow, choose the stack, and remove vague parts.
-
03
Build
Ship in visible chunks with demos before assumptions get expensive.
-
04
Launch
Deploy, monitor, document the useful bits, and clean up the mess.
Contact
Send the problem
Tell me what you are building, what is broken, or what needs to exist before Friday.