Hi!
My name is Arslan. I am a Full-stack Blockchain Solution architect and developer with 5+ years of development experience. Including the crypto exchanges (P2P, CEX & DEX), blockchain forks (NFT Marketplaces, DAO), tokens creation (ERC-20, ERC-721 , ERC-721A,, ERC1155 BEP20, SPL-TOKEN), smart contracts, ICO, Defi & IDO
Using Solidity and Rust I have developed Dapp, smart contracts, and NFT's for Ethereum, Solana, Fantom and Binance Blockchain.
Additionally, I'm skilled with the backend technologies like Node.js, Web3.js, MongoDB, Express JS, etc. I do Backend, Frontend, DevOps, and Deployment.
My Blockchain Specialization Areas:
★ DEXes (like Uniswap, Sushiswap, Pancakeswap, dYdX, etc)
★ NFT Minting DApps and marketplaces (Ethereum, Solana, Terra, Immutable X, and others)
★ DeFi platforms (any dApp, Binance Smart Chain, Ethereum, EOS, Tron)
★ Stock exchanges (like Binance, Coinbase, etc)
★ Wallets (crypto/fiat)
★ Blockchain block explorers
★ Web Development for Custom Business Web Applications
★ Front-end and Back-end Development
★ Content Management Development
★ High-End Enterprise Web Applications
★ Blockchain Development
Here is a list of technologies that I use:
★ Solidity Dapp Development
★ Blockchain- Ethereum , Solana, Fantom, Binance
★ Node.js
★ Lamp Stack, Nginx
★ MySQL, Postgres — data structure, performance tuning
★ NoSQL: MongoDB, Redis, GCP
★ Frameworks: React, Nextjs, Nuxt
★ Redux, Redux-Saga, Material UI, Typescript
★ DevOps: AWS, Cloudflare, Digital Ocean, Vultr, Kubernetes, CI/CD Pipelines
★ HTML, Bootstrap, jQuery, Sass, Gulp, Webpack, etc. — responsive, mobile-friendly websites
★ Server-side and client-side optimization, web applications performance tuning
My approach to project execution is as follows:
★ Understanding the project requirements through calls and emails
★ Wireframing using tools like Balsamiq, InVision, Figma
★ Project Execution using Project Management Systems like Basecamp, Trello, ASANA, Active Collab, JIRA
10 GOOD PRACTICES I FOLLOW IN CODE MANAGEMENT:
1. Commit early, commit often; every commit provides a rollback position
2. Inspect changes before committing
3. Remember the axe-murderer when writing commit messages
4. While working in a team, must commit your changes – you can’t delegate it
5. Versioning Database
6. Making extensive – detailed notes in the check-in comments about why the changes were made
7. Ensure the working file is from the latest version of the source file
8. Only Check-out the file being worked upon
9. Review every change before committing; utilize the diff function!
10. Use the ignore button for files that should not be committed, consider adding pre-commit filters to prevent the wrong kinds of files (such as accidental check-in of personal user settings docs) from entering the source control