Abdul Q.

If you need someone who can take a Web3 product from "we have an idea" to "it's live and handling real money on-chain," that's what I do. I'm a blockchain and backend engineer with almost six years in crypto — right now running backend for a P2P crypto trading platform and leading engineering for a Solana-based AI agent marketplace, at the same time, for two different companies. Most of my work lives at the point where application code meets the chain: on-chain escrow and settlement, ERC-4337 account abstraction (so your users don't need to hold gas or manage keys), 0x Protocol swap routing, custom relayers, and on-chain indexing so your app reads clean data instead of hammering an RPC endpoint. I've shipped this across Ethereum, Polygon, Arbitrum, Base, Optimism and Solana, and before that spent close to two years deep in zero-knowledge work — building a ZK-compression SDK for Solana and architecting a Circom tooling framework from scratch. Underneath all of that is solid backend engineering: microservice architectures built with TypeScript and NestJS, REST and GraphQL APIs, event-driven services, and data layers on PostgreSQL and Redis, deployed on AWS with proper CI/CD, monitoring and error handling. So if your project is a straightforward backend build with no chain involved, I can do that too — but where I add the most value is when the two need to work together. What I can help you build: - Smart contract backend integration — escrow, settlement, trade state machines synced against on-chain events - Account abstraction (ERC-4337) — gasless, wallet-abstracted transaction flows - DEX and swap infrastructure — limit orders, TWAP execution, quote/routing integrations - On-chain indexing — Substreams-based pipelines instead of RPC polling - Zero-knowledge tooling — Circom, zkSNARKs - Backend systems — TypeScript/NestJS, REST/GraphQL APIs, microservices, event-driven architecture, PostgreSQL/Redis, AWS deployment and CI/CD I work best with teams that want an engineer who can own a piece of the system end to end — not just write the ticket in front of them, but think about the state machine, the failure modes, and what happens when the chain and the database disagree. I communicate early and often, flag risk before it becomes a fire, and I'm used to working async across time zones (currently juggling teams in Canada and Dubai). If your project involves smart contracts talking to a real backend — escrow, swaps, account abstraction, indexing, or general Web3 infrastructure — I'd like to hear what you're building.