Faisal Khan — Blockchain Developer (Solidity, React)

Hi, I'm Faisal Khan — a blockchain developer from Peshawar, Pakistan, working with Solidity and React. I write smart contracts and build the dApp frontends that let real people use them.

What I do

My focus is the EVM stack: Solidity for smart contracts, Foundry for testing and deployment workflows, OpenZeppelin for audited building blocks, and React for the frontend layer. I like the full loop — writing a contract, testing it thoroughly, then shipping a clean Web3 UI that anyone can open in a browser and use.

My work revolves around two areas:

Solidity smart contracts. On-chain apps, contract security patterns, and the Foundry + OpenZeppelin toolchain. I also write about what I learn — my portfolio has articles on building an on-chain voting dApp in Solidity, five smart contract security patterns every beginner should know, and what React developers can carry over into Solidity.

React dApps. The other half of the stack. A smart contract is only half a product — the frontend is where users meet the chain. I build React frontends wired up to Web3, so the contracts I write are actually usable, not just code sitting in a repo.

Why Solidity + React

Most developers pick a side — contracts or frontend. I picked both, because the interesting problems live at the boundary: how a user clicks "vote" in a browser and that click becomes an immutable on-chain transaction seconds later. Understanding both sides makes each side better. My React experience shapes how I design contract interfaces, and writing Solidity changes how I think about state, cost, and trust on the frontend.

What I'm building

A few repos I'm actively working on:

• VotingSystem-DApp — an on-chain voting dApp written in Solidity, with a React frontend. Voting logic lives on-chain so every vote is transparent and verifiable. (github.com/MFaisaltech/VotingSystem-DApp)
• Smart-Contract-Inspector — a project focused on inspecting and analyzing smart contracts, born out of my interest in contract security. (github.com/MFaisaltech/Smart-Contract-Inspector)
• solidity — my working collection of Solidity code: experiments, patterns, and practice contracts. (github.com/MFaisaltech/solidity)

Everything is open source on my GitHub: https://github.com/MFaisaltech

The toolchain I use

• Solidity — the contract language itself. I write with readability first: named functions, clear state layout, and comments that explain the why, not just the what.
• Foundry — my testing and deployment setup. I test everything: happy paths, edge cases, and the attack paths I'm trying to close. A contract I can't test is a contract I don't ship.
• OpenZeppelin — audited building blocks instead of reinvented wheels.
• React + Web3 — the frontend layer. Wallets, transaction states, loading spinners that respect pending transactions — the unglamorous details that decide whether a dApp feels usable or broken.

What I'm writing

I write about Solidity and Web3 development — practical, beginner-friendly, and grounded in code I actually ran. Topics I cover: building dApps in Solidity, smart contract security patterns, and the React-to-Solidity learning path.

Portfolio: https://v0-faisal-khan-blockchain.vercel.app/
X: https://x.com/FaisalOn_AI
LinkedIn: https://www.linkedin.com/in/faisal-khan-9658002a8/

What's next

Short term: more Solidity repos, deeper work on contract security, and continuing to document everything in public. Long term: I want to be the kind of blockchain developer whose code people can read, learn from, and trust — open source first, always.

If you're learning Solidity, building dApps, or just curious about the space — follow along. I'm building in public.