𝐂𝐫𝐲𝐩𝐭𝐝𝐚𝐫𝐤 🌑

𝐀𝐬𝐩𝐢𝐫𝐢𝐧𝐠 𝐅𝐮𝐥𝐥-𝐒𝐭𝐚𝐜𝐤 𝐁𝐥𝐨𝐜𝐤𝐜𝐡𝐚𝐢𝐧 𝐃𝐞𝐯𝐞𝐥𝐨𝐩𝐞𝐫 | 𝐖𝐞𝐛 𝐃𝐞𝐯 𝐄𝐧𝐭𝐡𝐮𝐬𝐢𝐚𝐬𝐭 Hey, I'm Cryptdark, a passionate web developer building sleek, responsive sites with HTML, CSS, JS, and modern frameworks. Currently honing my skills through portfolio projects like interactive animations and cutting-edge UI designs. My big goal? Level up to full-stack blockchain dev – diving deep into Solidity, smart contracts, and decentralized apps to build the future of Web3. Actively seeking internships in blockchain/web dev! If you're hiring or know opportunities, DM me. Let's connect and build something epic. #WebDev #Blockchain #InternshipHunt

@yusufthebdev For sure.. one day 😌.

@Cryptdark1 as long as we are consistent😁

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

Focused on reading reports and recreating attacks from past report. I dont even keep track of time again. The goal is to perform way better in the next contest I will participate in. An always happy to connect with other smart contracts auditors.

@anchabadze Keep going bro.. this is how we roll 💪

🎯 Day 336 of my #RoadToWeb3SecurityJobChallenge 🕰️ Hours worked: 6 hours 🔎 Focus: Learning 🛠️ Practical work: - Read several web3 sec articles - Read and studied several bug bounty writeups - Studied different vulnerabilities using Anki cards

@radcipher Participating in this one

Something is different on Monday. Audit Arena Week 9 drops with a full upgrade. New leaderboard. New submission console. Cleaner experience. Built from your feedback. Built for you. Same competition. Better everything. Monday 9AM UTC. Discord link in bio.

@pashov Guess I am doing it right

If I was just starting out as a security researcher in web3, I would've been learning the following, in this order: 1. Solidity & EVM 2. Hacking smart contracts, replaying exploits 3. AI - building Skills, utilising agents 4. Practice on every possible occasion Good luck🫡

@auditor_nate Will definitely set a time out for it. 💯

@Cryptdark1 Yeah do it brother, I set myself about two hours a week to tackle this challenge!!! It’s great fun

20th last week, 5th this week I am coming for number 1 next 💪

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.

one beast approach in bug bounty is to pick a constantly upgraded protocol, drink its code and stay dormant there. you may not ever find any thing, but this is always a risk. combine this approach for like 3 protocols and do some side plumbing KEK. thank me latter

@zerocipher002 This is huge.. nice one bro

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.

Read through many reports today.. if I am not audithing. Then I am researching on new attack patterns. This is what it means to be a security researcher. Always research !

@adeolRxxxx In the same shoe.. but its worth it !

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

@WebdevAnas @yusufthebdev @chainlink @code4rena yeah there is guardian contest, and ominivault and eStorm those two are in hacken proof i think. and this chainlink i think.

@Cryptdark1 @yusufthebdev @chainlink @code4rena 🤞 I hope, what you are saying is actually true.

🎯Day 12 of becoming a top Web3 security researcher ⏳ Hours worked: 5 hours 40 minutes 🔎 Focus: Auditing 🔧 Practical work: - On-going @chainlink audit on @code4rena - Focused on business logic bugs - Studied some auction attack vectors on solodit

@WebdevAnas @yusufthebdev @chainlink @code4rena i think they are still like 4 contest going on right now... they may have reduced alot, but definately not the last one.

@Cryptdark1 @yusufthebdev @chainlink @code4rena Bro the contest is becoming history now, I think this is the last contest right now.

@yusufthebdev @chainlink @code4rena 😅

@Cryptdark1 @chainlink @code4rena goosebumps😆

@yusufthebdev @chainlink @code4rena Very true bro.. I still remember when I got hook on a poc that keeps failing. Contest is ending in few hours 😅

@Cryptdark1 @chainlink @code4rena the pressure before a contest ends is real

I noticed that I waist so much time in writing poc. Keep on debugging for hours, I need to change that. What practice do u recommend I should do to make writing poc more efficient. Need to work on myself

@CreatorsOfChaos Thanks for this bro.. I will take note and implement in all my submissions, hence forth.🫡

Huge milestone, man! First one is always the hardest. But a word of advice from the trenches: the bug hunt market is brutal lately. To get this over the line, you need to leave zero room for doubt. Don't just submit a snippet. Log every state change, trace every call, and if it's a protocol, make sure your PoC deploys the full suite of contracts in devnet. Show them the exact 'before' and 'after' of the exploit. In this market, if it isn't documented to the point of exhaustion, it’s 'invalid.' Over-communicate the impact!

i think i will be submitting my very first finding in a contest today, already written the poc. i dont know if it will be valid or invalid.... but regardless, this is a big step forward for me. this shows i am improving, thats good enough for now.