Ritik Verma

313 posts

Ritik Verma banner
Ritik Verma

Ritik Verma

@RV_Programmer

Blockchain Engineer | Smart Contract Security & Web3 Development | DeFi | Exploit Simulation | Solidity | Foundry My github - https://t.co/EVDIuA3KVJ

Katılım Mart 2025
50 Takip Edilen45 Takipçiler
Ritik Verma
Ritik Verma@RV_Programmer·
@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
English
0
0
0
4
Ritik Verma
Ritik Verma@RV_Programmer·
@AshishAsmit Access control, mint limits, and edge cases like reentrancy or unexpected state changes
English
0
0
0
7
GitHub Projects Community
GitHub Projects Community@GithubProjects·
| ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄| | Share your GitHub profile. | |_____________| \ (•◡•) / \ / —— | | |_ |_
English
929
43
1.4K
137.3K
Ritik Verma
Ritik Verma@RV_Programmer·
@AshishAsmit For me it was moving from writing logic to writing invariants and attack scenarios. That’s when testing actually started catching real issues
English
1
0
1
14
Ashish Asmit
Ashish Asmit@AshishAsmit·
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
English
3
0
5
52
Ritik Verma
Ritik Verma@RV_Programmer·
Includes full audit report and exploit test cases in the repo.
English
0
0
1
36
Ritik Verma
Ritik Verma@RV_Programmer·
@TammyBuilds Exactly, once you write the exploit, you start thinking like an attacker, not just a developer. That’s where things really click.
English
1
0
1
9
Tammy.eth
Tammy.eth@TammyBuilds·
@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.
English
1
0
1
9
siddharth
siddharth@buildwithsid·
Drop your portfolio (or your best website) I'm gonna rate it.
English
676
3
404
84.7K
Ritik Verma
Ritik Verma@RV_Programmer·
@BABS96711 Solid call. I’d focus on understanding real-world exploits and writing PoCs. Finding bugs is one thing, proving impact is what matters
English
1
0
1
13
Ritik Verma
Ritik Verma@RV_Programmer·
@0xYasiransari Single-function is the basic one. Cross-function and cross-contract are where most real-world bugs hide
English
2
0
1
7
Sick
Sick@sickdotdev·
Drop your portfolio (or your best website) I’m gonna rate it. Last time 50000 people saw it. Consider this as marketing.
English
831
3
385
43.6K
Ritik Verma
Ritik Verma@RV_Programmer·
@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.
English
1
0
1
12
Wake
Wake@WakeFramework·
@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.
English
1
0
1
16
Ritik Verma
Ritik Verma@RV_Programmer·
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
English
2
0
2
80
Ritik Verma
Ritik Verma@RV_Programmer·
@bugbounty737 Using call now. transfer feels unsafe after gas changes. Just follow checks-effects-interactions and guard reentrancy
English
0
0
0
4
Ethical Hacker | Bug Bounty🤴
Ethical Hacker | Bug Bounty🤴@bugbounty737·
#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)
English
1
0
4
33
Ritik Verma
Ritik Verma@RV_Programmer·
@PeatPeater2 Deploy and verify, then scripting repetitive tasks like role assignments, config updates, and contract interactions. Saves a lot of manual steps
English
1
0
0
7
Ritik Verma
Ritik Verma@RV_Programmer·
@BensonDynasty_ Agree. Devs optimize for functionality, auditors optimize for failure. Breaking logic is always harder than writing it
English
1
0
1
8
Kingdavid
Kingdavid@BensonDynasty_·
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
English
3
0
3
46
Ritik Verma
Ritik Verma@RV_Programmer·
@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
English
0
0
2
13
shivam
shivam@10xshivam·
Share your portfolio I will rate it out of 10
English
236
0
112
14.2K