Kaushal
Full Stack Developer & Smart Contract Engineer
Overview
Full Stack & Smart Contract Engineer @TheOpenAssets
Full Stack & Blockchain Developer @PayZoll
Want to work together? (Currently Open to Work)
Book a free call instantly.
About
I am a Full Stack Developer and Smart Contract Engineer dedicated to building production-ready decentralized applications with a focus on precision and performance.
- Frontend Excellence: I specialize in crafting intuitive UI/UX experiences using Next.js and TypeScript. I have built complex state-driven interfaces for projects like Alentra, focusing on seamless user onboarding and real-time data visualization.
- Robust Backend & Architecture: Experienced in designing scalable APIs and architecting optimized database schemas. For Meridian Finance, I engineered a secure backend infrastructure using Node.js and MongoDB to manage confidential bond lifecycles and ZK-credential verification.
- Spec-Driven Development: I follow a disciplined development lifecycle—prioritizing clear technical specifications and documentation before implementation. This approach ensures architectural integrity in high-stakes environments, as demonstrated in my work on TheOpenAssets execution layer.
- Smart Contract Engineering: 5x Hackathon Winner and BNB Chain Martian with expertise in Solidity, Foundry, and ZK Proofs. I specialize in privacy-preserving protocols and AI-integrated contract lifecycles like Zera.
Featured Builds
View all buildsGitHub Contributions
Stack
Blog(1)
Experience
- Built a B2B cross-border payroll platform on Stellar so companies pay employees globally in USDC/EUROC in seconds instead of 3–5 day bank transfers.
- Shipped the full product as founding engineer: TypeScript/Node.js (Express) backend, React/Vite frontend, PostgreSQL + Redis, and production deploy on GCP (GCE, Cloud Build) with Cloudflare Tunnel and PM2.
- Integrated Stellar Disbursement Platform as a multi-tenant payment rail — one isolated SDP tenant per organization — covering onboarding, CSV disbursements, status polling, retries, and wallet funding.
- Built just-in-time payroll: convert USD → stablecoin with decimal.js + CoinGecko rates, construct unsigned Stellar XDR on the server, have the org admin sign in-browser with Freighter, then settle on-chain. Private keys never leave the browser.
- Owned production reliability: dual-token auth (PayZoll JWT + SDP sessions in Redis), PIN-gated disbursements, Redis-lock crash recovery for in-flight payrolls, live SSE dashboards, parameterized PostgreSQL (GIN indexes, no ORM), AWS SES/Twilio, Google Drive KYC, OpenTelemetry, Winston, Helmet, and rate limiting.
- TypeScript
- Node.js
- Express
- React
- Vite
- PostgreSQL
- Redis
- Stellar
- SDP
- Freighter
- GCP
- OpenTelemetry
- Architected and fully implemented ERC-3643 (T-REX) fully on-chain for compliant RWA issuance, engineering identity-bound transfer controls, modular compliance enforcement, and upgrade-safe contract systems.
- Researched ERC-3643 and ERC-7518 to design interoperable, regulation-aligned RWA token primitives across institutional-grade on-chain frameworks.
- Engineered a chain-agnostic RWA execution layer across Mantle, OneChain, Creditcoin, and Stellar, abstracting settlement, custody logic, and lifecycle orchestration into unified cross-chain infrastructure.
- Built cron-driven backend automation for liquidation monitoring and deterministic time-weighted yield distribution aligned with on-chain state transitions.
- Won 3 hackathons competing under this project banner.
- Solidity
- ERC-3643
- ERC-7518
- RWA
- Mantle
- Stellar
- Creditcoin
- Hardhat
- Foundry
- Node.js
- TypeScript
Education
- C++
- Java
- Python
- DSA
- Systems Design
- Distributed Systems
- Software Engineering
- Blockchain
Issues I Resolved(1)
Issue
A junior developer’s local app was returning ERR_CONNECTION_REFUSED when accessed through https://app.xyz.dev.
Root Cause
The application itself was running correctly on localhost:4137. However, Portless was running in HTTP mode on port 1355 instead of serving HTTPS on port 443.
Since .dev domains are HSTS-preloaded, the browser automatically enforces HTTPS. It therefore tried to connect to:
https://app.xyz.dev → 127.0.0.1:443
but nothing was listening on port 443, resulting in ERR_CONNECTION_REFUSED.
Resolution
I restarted the Portless proxy with HTTPS support and configured it to use the xyz.dev TLD:
bunx portless proxy stop
bunx portless proxy start --tld xyz.dev
bunx portless trust
bunx portless doctor
The proxy was then able to bind to port 443 with elevated permissions.
Result
The local application became accessible through https://app.xyz.dev.
The issue was not with the application or Vite server; it was caused by the local HTTPS proxy configuration and .dev HSTS enforcement.
- HTTPS
- HSTS
- Portless
- Vite
