Yousef

I finally completed @CyfrinUpdraft Smart Contract Security Course!🎉 It was a lot but it's definitely worth it Special thanks to the team for the education😁🥂 Now we go harder👩🏾‍💻 profiles.cyfrin.io/u/yusufthebdev…

@Saren03_ cheers

I work and work and work and work and work and work and wo-

@nemesis_sol_ thanks bro

@yusufthebdev Keep going 💪🏼💪🏼

🎯Day 15 of becoming a top Web3 security researcher ⏳ Hours worked: 4 hours 🔎 Focus: Learning 🔧 Practical work: - Learnt about tokenized-vaults (ERC-4626) - Studied past audit reports - Learnt some AI integration to improve my workflow

@Cryptdark1 as long as we are consistent😁

Just submitted my first bug few days back.. But nevertheless.. Hi 🤧

@pranayraj069 game is game

The contest is over, and now I have to wait a month to read the report and get feedback.

@0xVoid_Web3 @milan_milanovic it’s always us vs the hackers, as long as there are attackers, there is always need for defenders

@milan_milanovic AI can generate contracts But it can't guarantee they're safe Someone still has to think like an attacker

When Opus 5.0 with 10M context is released, do you still have a job as a developer ?

@Web3_Vinay onto the next 🤝

🦖 Day 285 of learning blockchain 👾 Wrapped up a contest today. Starting shadow auditing mode now — picking a live DeFi protocol, reading the code like an attacker, tracing every token flow, every state change, every external call before looking at a single audit report. This is how pattern recognition gets built. Not from tutorials. Not from theory. From sitting with hard code until it starts making sense. The progress is not always visible day to day. But it compounds. To every warden grinding between contests — keep your head down. The reps matter even when nobody is watching. On to the next one. 🧱

@Cryptdark1 exactly! the motion compounds

I have made it a norms.. that I must improve every single day. Even if it is just a little. The me that participates in an audit a week ago, Cant be the same as the one writing this tweet now. Improve yourself every single day.

🎯Day 14 of becoming a top Web3 security researcher ⏳ Hours worked: 4 hours 🔎 Focus: Reporting 🔧 Practical work: - Submitted my last finding on @chainlink audit on @code4rena - Experienced what it felt like to be a security researcher - Stressful but fulfilling

@nemesis_sol_ @PatrickAlphaC we love him

that's crazy how @PatrickAlphaC is the "dad" of new web3 security reaserchers ! love this

@PatrickAlphaC the bench press is the most important

A battlechain hackathon would go so hard. Imagine a room full of devs with a billion AI agents blasting at contracts trying to steal money from each other. And a bench press in the corner.

Major cheat code for life: Don’t mourn the time you've lost, use the time you still have. Most people walk around haunted by a list of things they wish they’d done by now. They tell themselves it’s too late. It’s not. 6 months from now, it can still be a dream, or it can be real.

@zerocipher002 motivates me

Three years ago I submitted my first Web3 contest entry on Code4rena. Found one QA issue. Thought maybe I'd chosen the wrong career path. This year I collected $300,000 from a single critical bug report. This space rewards depth and patience in ways I didn't fully understand when I started.

@adeolRxxxx the time will pass anyway

Looking at the motion I wanna have this year, I have a clear path/vision already but Ik im gonna be miserable and not have a life to get it

Explaining a bug that you know is a bug humbles you sometimes

@0xVoid_Web3 @chainlink @code4rena exactly…took 70% of my time😂

@yusufthebdev @chainlink @code4rena Finding bugs is one skill Explaining them clearly is what makes you valuable

🎯Day 13 of becoming a top Web3 security researcher ⏳ Hours worked: 6 hours 🔎 Focus: Auditing & Reporting 🔧 Practical work: - Submitted my first finding on @chainlink audit on @code4rena - Read web3 security focused articles

@HackerOn2Wheels 😂😂😂

I trusted Claude as it guaranteed it found a real vulnerability I just needed to buy the premium feature to exploit it… it was actually right.

Most devs get this wrong in Solidity ⚠️ call - runs code in another contract delegatecall - runs code in your contract Same code Different storage ⚖️ Context is everything ⚡ Use delegatecall wrong… you don't just break things you lose ownership 💀

real