Ritik Verma

I built a fully decentralized chat app using GunDB with P2P messaging, end-to-end encryption, and zero servers. Try the live demo: d-chat.online #Web3 #DApp #GunDB #P2P #DecentralizedWeb #BuildInPublic

@CryptoBoil Thanks! I’ll definitely share it with you once it’s fully ready. Still refining a few things on the security side before putting it out

@RV_Programmer That's awesome can you share it with me in the dm

Every Web3 project starts with an idea… But not every project is secure. What are you building right now? Let’s talk security early. #Web3 #Solidity #SmartContract

@AshishAsmit Access control, mint limits, and edge cases like reentrancy or unexpected state changes

Deployed my first token on testnet today using OpenZeppelin to write the crypto currency contract. What’s the FIRST thing you’d test on a fresh contract? #Web3 #Solidity #Ethereum #OpenZeppelin #BuildInPublic #Testnet #Blockchain

@GithubProjects Building in Web3, smart contracts, DApps, and tools: github.com/Ritik505

|￣￣￣￣￣￣￣￣￣￣￣￣￣| | Share your GitHub profile. | |＿＿＿＿＿＿＿＿＿＿＿＿＿| \ (•◡•) / \ / —— | | |_ |_

@AshishAsmit For me it was moving from writing logic to writing invariants and attack scenarios. That’s when testing actually started catching real issues

Testing smart contracts completely changed my perspective today. The biggest takeaway is that testing is not about making the contract work. It is about trying your hardest to break it. What was your biggest lightbulb moment with security? #web3 #solidity #buildinpublic

Includes full audit report and exploit test cases in the repo.

Built and audited a DeFi Vault using Foundry Exploited real vulnerabilities: - Reentrancy - Share inflation Developed attack contracts, reproduced exploits, and validated secure fixes with tests. + audit report github.com/Ritik505/defi-… #Solidity #Web3 #SmartContractSecurity

@TammyBuilds Exactly, once you write the exploit, you start thinking like an attacker, not just a developer. That’s where things really click.

@RV_Programmer actually writing the exploit contract to reproduce the bug is how it really clicks. this is the kind of hands on practice i need to be doing more of.

@buildwithsid ritikportfoliodev.netlify.app

Drop your portfolio (or your best website) I'm gonna rate it.

@BABS96711 Solid call. I’d focus on understanding real-world exploits and writing PoCs. Finding bugs is one thing, proving impact is what matters

Due to the contest shortage, I'm considering starting bug bounty hunting again, for the second time since my journey began. I'll start by next week. What's your advice? #bugBounty #solidity #contest #smartcontracts #defi

@virentanti Forge. Once you get used to it, hard to go back

What do you guys use for testing your smart contracts? #web3‌‌ #solidity #hardhat

@0xYasiransari Single-function is the basic one. Cross-function and cross-contract are where most real-world bugs hide

Reentrancy isn’t just one bug. There are multiple variants most devs never learn. Do you know all 3? tinmyowin.gumroad.com/l/xttcp #Web3Security #Reentrancy #Solidity #BugBounty #DeFi

@sickdotdev Full-stack Web3 developer portfolio with smart contracts and dApps: ritikportfoliodev.netlify.app

Drop your portfolio (or your best website) I’m gonna rate it. Last time 50000 people saw it. Consider this as marketing.

@WakeFramework That’s a great point. I’ve been focusing on deterministic tests so far, but fuzzing would definitely help uncover edge cases I might miss. I’ll explore adding fuzz tests to the reentrancy module.

@RV_Programmer Attack simulations are the best teacher. If you want to push those reentrancy tests further, fuzzing generates edge cases you wouldn't write manually. Wake handles that in Python.

Built a Smart Contract Security Lab using Foundry Reentrancy Access Control bugs Integer underflow Each with: - exploit - fix - tests Focused on proving vulnerabilities through real attack simulations and secure fixes github.com/Ritik505/smart… #Solidity #Web3

@bugbounty737 Using call now. transfer feels unsafe after gas changes. Just follow checks-effects-interactions and guard reentrancy

💡 Modern smart contracts rely on call for reliability & control. Are you still using transfer or fully switched to call? 👇 #Solidity #Web3

#Day60 of learning Solidity 🚀 Sending ETH in Solidity? You’ve got 3 options: • transfer → simple, but strict (2300 gas, auto-revert) • send → safer control (returns bool, still 2300 gas) • call → flexible & recommended (no gas limit, returns success)

@PeatPeater2 Deploy and verify, then scripting repetitive tasks like role assignments, config updates, and contract interactions. Saves a lot of manual steps

Currently exploring Foundry scripting. What are the first real-world workflows you automate after getting comfortable with deploy scripts? #web3 #solidity #foundry #blockchain #smartcontracts #decentralized #ethereum

@BensonDynasty_ Agree. Devs optimize for functionality, auditors optimize for failure. Breaking logic is always harder than writing it

Unpopular opinion: Smart contract auditing is becoming harder than development. Devs can copy patterns. Auditors have to understand the pattern… break it… and prove impact. Agree or disagree? #solidity #Web3Community

@kacieahmed One of my projects: D-Chat A decentralized chat app running on a P2P mesh with end-to-end encryption and zero backend. d-chat.online

@10xshivam Full-stack Web3 developer portfolio: ritikportfoliodev.netlify.app Let’s see the rating.

Share your portfolio I will rate it out of 10