The latest articles on DEV Community by Faisal Khan (@faisal_khan_ebe05e79db3c3). https://dev.to/faisal_khan_ebe05e79db3c3 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2844012%2Fd1c551f8-f5df-4e22-93a6-3e2ebed4758d.jpg https://dev.to/faisal_khan_ebe05e79db3c3 en Faisal Khan Wed, 14 Oct 2026 16:49:38 +0000 https://dev.to/faisal_khan_ebe05e79db3c3/faisal-khan-blockchain-developer-solidity-react-26n0 https://dev.to/faisal_khan_ebe05e79db3c3/faisal-khan-blockchain-developer-solidity-react-26n0 <h1> Faisal Khan — Blockchain Developer (Solidity, React) </h1> <p>Hi, I'm <strong>Faisal Khan</strong> — 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.</p> <h2> What I do </h2> <p>My focus is the EVM stack: <strong>Solidity</strong> for smart contracts, <strong>Foundry</strong> for testing and deployment workflows, <strong>OpenZeppelin</strong> for audited building blocks, and <strong>React</strong> 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.</p> <p>My work revolves around two areas:</p> <p><strong>Solidity smart contracts.</strong> 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.</p> <p><strong>React dApps.</strong> 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.</p> <h2> Why Solidity + React </h2> <p>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.</p> <h2> What I'm building </h2> <p>A few repos I'm actively working on:</p> <ul> <li> <strong>VotingSystem-DApp</strong> — 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)</li> <li> <strong>Smart-Contract-Inspector</strong> — a project focused on inspecting and analyzing smart contracts, born out of my interest in contract security. (github.com/MFaisaltech/Smart-Contract-Inspector)</li> <li> <strong>solidity</strong> — my working collection of Solidity code: experiments, patterns, and practice contracts. (github.com/MFaisaltech/solidity)</li> </ul> <p>Everything is open source on my GitHub: <a href="https://github.com/MFaisaltech" rel="noopener noreferrer">https://github.com/MFaisaltech</a></p> <h2> The toolchain I use </h2> <ul> <li> <strong>Solidity</strong> — the contract language itself. I write with readability first: named functions, clear state layout, and comments that explain the <em>why</em>, not just the what.</li> <li> <strong>Foundry</strong> — 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.</li> <li> <strong>OpenZeppelin</strong> — audited building blocks instead of reinvented wheels.</li> <li> <strong>React + Web3</strong> — the frontend layer. Wallets, transaction states, loading spinners that respect pending transactions — the unglamorous details that decide whether a dApp feels usable or broken.</li> </ul> <h2> What I'm writing </h2> <p>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.</p> <p>Portfolio: <a href="https://v0-faisal-khan-blockchain.vercel.app/" rel="noopener noreferrer">https://v0-faisal-khan-blockchain.vercel.app/</a><br> X: <a href="https://x.com/FaisalOn_AI" rel="noopener noreferrer">https://x.com/FaisalOn_AI</a><br> LinkedIn: <a href="https://www.linkedin.com/in/faisal-khan-9658002a8/" rel="noopener noreferrer">https://www.linkedin.com/in/faisal-khan-9658002a8/</a></p> <h2> What's next </h2> <p>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.</p> <p>If you're learning Solidity, building dApps, or just curious about the space — follow along. I'm building in public.</p> solidity web3 blockchain react