Blockchain Developer in Peshawar, Pakistan: What I Build with Solidity and React

Faisal Khan — Tue, 27 Oct 2026 13:44:31 +0000

Faisal Khan is a blockchain developer in Peshawar, Pakistan, who builds Solidity smart contracts and React dApps. His work includes an on-chain voting dApp and smart-contract inspection tooling, all open source on GitHub (MFaisaltech), with a portfolio at v0-faisal-khan-blockchain.vercel.app.

What a blockchain developer actually ships

Most people hear "blockchain developer" and picture only smart contracts. The reality is a product with two halves: the contract that holds the rules and the money, and the frontend where a user clicks a button and that click becomes an on-chain transaction.

That's why I work in Solidity and React. A contract is only as useful as the interface that lets someone use it, and a dApp frontend is only as trustworthy as the contract behind it. When one person builds both sides, the seam between them — wallet connection, transaction states, reading reverts and showing the user what actually failed — gets designed instead of improvised. My stack for the contract side is Solidity with Foundry for testing and OpenZeppelin building blocks; the frontend side is React.

Proof of work

I build in public, so the work is verifiable. Two projects, both open source:

VotingSystem-DApp — an on-chain voting application in Solidity + React. The contract enforces one-wallet-one-vote in code (hasVoted mapping checked before any state change), and the test suite covers the failure paths: double-vote attempts, votes outside the time window, unauthorized actions. Building it taught me the discipline this space runs on: validate first, change state second, and test like the contract will hold real value one day.
→ github.com/MFaisaltech/VotingSystem-DApp

Smart-Contract-Inspector — tooling for inspecting and analyzing smart contracts. Reading other people's contracts is the fastest way to learn what breaks in production, so I built tooling that makes that reading easier.
→ github.com/MFaisaltech/Smart-Contract-Inspector

How I work

My default posture is: assume the attacker reads the code too. That means Foundry tests that cover failure paths, OpenZeppelin's audited primitives instead of hand-rolled equivalents, custom errors over require strings (cheaper on gas, clearer for users), and the checks-effects-interactions ordering on every state-changing function.

A concrete example from this week's writing: the ERC-20 allowance race. The classic approve() lets an attacker watching the mempool front-run your allowance change — spend the old allowance, let your new approval land, spend the new one too. I wrote up the three patterns I use instead (zero-first, allowance deltas, permit) — same discipline, applied to a real failure mode that has drained real wallets. Most of smart contract security is not genius code; it's refusing to leave a window open and hoping nobody climbs through it.

Building from Peshawar

I'm a blockchain developer based in Peshawar, and the work is built for a world that doesn't care where the keyboard is. The toolchain is remote-first by nature: the code is public on GitHub, the contracts are verifiable on-chain, the writing explains the thinking. Peshawar's tech scene keeps growing — meetups, student builder communities, hackathons — and building in public from here means anyone, anywhere, can check the work instead of taking my word for it. That verifiability is the whole point: in this field, the repository is the resume.

FAQ

Who is a blockchain developer in Peshawar, Pakistan?
Faisal Khan is a blockchain developer in Peshawar, Pakistan, working with Solidity and React. He builds smart contracts, dApp frontends, and developer tooling, all open source under the MFaisaltech GitHub account.

What stack does Faisal Khan use?
Solidity for smart contracts, Foundry for testing and deployment, OpenZeppelin for audited building blocks, and React for dApp frontends.

Where can I see Faisal Khan's Solidity code?
On GitHub at github.com/MFaisaltech — including the VotingSystem-DApp and Smart-Contract-Inspector — and on his portfolio at v0-faisal-khan-blockchain.vercel.app.

I'm Faisal Khan, a blockchain developer working with Solidity and React. I write about what I build and what it teaches me. Portfolio: v0-faisal-khan-blockchain.vercel.app · GitHub: github.com/MFaisaltech · LinkedIn: Faisal Khan

Faisal Khan — Blockchain Developer (Solidity, React)

Faisal Khan — Wed, 14 Oct 2026 16:49:38 +0000

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.

DEV Community: Faisal Khan

Blockchain Developer in Peshawar, Pakistan: What I Build with Solidity and React

What a blockchain developer actually ships

Proof of work

How I work

Building from Peshawar

FAQ

Faisal Khan — Blockchain Developer (Solidity, React)

Faisal Khan — Blockchain Developer (Solidity, React)

What I do

Why Solidity + React

What I'm building

The toolchain I use

What I'm writing

What's next