darkstar (@darkstarpp) profile picture
Mars
Joined September 2025
darkstar retweeted
One year in web3 security. The biggest lesson wasn’t technical. In a few weeks it will be a year since I left software engineering and became a web3 security researcher. Estimated earnings for that first year: around $200k. This past month I’ve been looking back at all of it: the findings, the misses, the dry spells, the discipline, and how I built my days so I could hunt hard and still live a healthy life. And honestly, the number isn’t the main thing I took away. The biggest lesson was about control. Most of the game is outside your hands In this space a lot gets decided after you hit submit. Someone finds the same bug and yours becomes a duplicate. The judge downgrades your severity. A project goes quiet and never pays. Someone on your timeline posts a five figure payout in the same week you found nothing. If your mood depends on those things, this job will eat you alive. I learned that the hard way. Epictetus put it simply. Some things are up to us and some are not. Our effort, our judgments and our actions are ours. Results, reputation and other people’s decisions are not. Most suffering comes from confusing the two. Your report is your arrow Think of an archer. He controls the preparation, the aim, the breath and the release. Once the arrow leaves the bow, it belongs to the wind. In bug hunting the arrow is the report. Everything before submit is yours: how deep you read the code, how many edge cases you test, how clear your PoC is. Everything after is not. So I changed how I define success. A good day is not a day with a finding. A good day is one where I did the work with full focus. If that’s the measure, you can’t fail. Aim high, then let go You have to aim at something, otherwise you don’t move anywhere. Aim with everything you have, but don’t tie your peace of mind to whether you hit. Stop comparing yourself to other hunters. Leaderboards and payout screenshots show someone else’s journey. The only fair comparison is you a year ago. When I look at that version of me, the gap is huge. That’s the real result. And before you complain about judging, ask yourself if your report was really as clear and complete as it could be. Usually there’s something you could have done better. Emotions are information, not orders The hardest part was emotional. Frustration when a valid finding gets rejected. Envy when others hit big. The rush when you think you’ve found a critical, then the crash when it turns out to be a known issue. Doubt in the middle of a long dry spell. Most of my worst days weren’t caused by what happened. They came from the stories I told myself about it: “I’m not good enough.” “I wasted a whole month.” You can’t choose the judging outcome. You can choose what you do the next morning. Self-control lives in the boring parts Discipline isn’t one heroic all-nighter. It’s the daily structure: fixed blocks of deep work, phone away going through past contest reports and what I missed sleep, training and real food good books time completely offline Your system decides your results more than your goals do. The hunter with the better system beats the hunter with the bigger dream. And health isn’t separate from the work. A tired brain misses bugs. Taking care of your body is part of the process. What I control: how much I work and study how precise and persistent I am how I react when things go wrong What I don’t control: whether someone finds the bug before me whether it gets paid what the final result will be One year in, I don’t feel calmer because the results got better. I feel calmer because I stopped asking the results to tell me who I am. Focus on the process. Let the rest go.
13
18
1
186
5,875
How do we consistently find bugs? 1. Understand the system: docs, architecture, user flows. 2. Map the attack surface: inputs, state changes, assumptions. 3. Break assumptions. That’s where exploits live. AI is with us in the process, helping us move faster, go deeper.
1
5
25
922
darkstar retweeted
Kicking off a hands-on series: AI for Web3 Security, Zero to Hero. Meant to be your starting point: build a real AI security agent, module by module, until you have a full harness of your own. Module 1 is up - your very first agent, from scratch.
11
26
9
173
14,356
darkstar retweeted
POV: you spent all your hard-earned money on AI tokens
8
11
201
5,565
Former Navy SEAL Jocko Willink said it right: “Other than death, all defeats are psychological. Never give up.”
27
556
5
4,226
69,591
There’s one thing our security researchers have in common: O B S E S S I O N They are obsessed with what they do. They work 90% of the time. They live and breathe it. There’s no shortcut - if you want real success, obsession is the price.
1
2
16
621
darkstar retweeted
This article is very interesting for designing your own AI tooling for BB hunting: use /goal instead of the attack vector. Use the impacts accepted by the BB program and create a goal around reaching them. Instead of going from attack vector → impact. Try going from impact → attack path. Go from zoomIn instead of zoomOut. blog.trailofbits.com/2026/07…
2
18
1
130
5,330
darkstar retweeted
Just off-ramped my USDC payment via @PayZoll Funds landed in my Indian bank account via J.P. Morgan Chase, along with a FIRA reflecting the paying company’s details. I’ll recommend it ahead for anyone receiving stablecoins in payments from their clients/companies. The rates are pretty good too. For more, you can directly communicate with @ItachiOnChain! Or visit payzoll.finance Definitely recommend it!
1
5
1
41
3,355
darkstar retweeted
Devs, here's how to stop missing criticals in your internal reviews. Not due to a lack of skill - but a lack of a system. After 150+ audits, here's my 5-check "never miss the basics" framework: 1. Who can call this function? (check every modifier) 2. What state changes before an external call? (reentrancy) 3. What happens with zero as input? (edge cases) 4. Can this be called twice? (replay) 5. What does the function NOT check? (missing validation) I've found more simple critical bugs from this checklist than from any advanced technique. Save this. Run it on your next PR. 🫡
1
9
2
59
3,461
darkstar retweeted
I created a small repo with instructions for an AI agent on what it should do when assisting me during an audit. I made it to fit my personal auditing workflow. It is only the first version and will be improved in the future, but I thought I would make it public so that anyone who finds it useful can use it: github.com/TheSchnilch/audit…
2
12
1,036
darkstar retweeted
🧵/1 There are already multiple free AI auditors for smart contracts But there are almost none focused on blockchain / DLT systems themselves: clients, consensus, execution, bridges, mempools, state sync, resource accounting, and protocol logic. I spent 7 weeks worth of ChatGPT Pro 20x tokens building DLT Auditor v1 Now I’m sharing it for free: github.com/RASHMOR1/dlt-audi…
6
18
121
10,468
darkstar retweeted
I used property testing during a Solana AMM audit. This blog post walks through the seven properties and their reasoning, the sequence-based test structure, and a case where my own test had a bug that looked like a real finding: s3v3ru5.github.io/posts/sola…
1
8
29
1,865
darkstar retweeted
This was a 10k USD simple but critical time-based sqli bug i found a while ago, with the help of bbradar.io notifications. > New target went live -> Instant Discord notification > Basic recon > Ghauri against api endpoints > Full db dump Sometimes its as simple as being first.
Finally confirmed!
3
18
212
13,420
darkstar retweeted
7/ If you’re starting out: 📍 Follow the funds 📍 Follow the trends 📍 Focus deeply That’s how I did it.
2
42
2,735
2
32
166
5,212
5 oracle bugs (from real audits) 🫡 - Redstone going back in time - Staking feeds - The boring one - Pyth confidence - 1 USDC/USDT == 1 USD Delve deeper into the findings here 👇 paragraph.com/@0x3b/oracle-b…
5
6
21
2,124
I am sure that this is the best 4-minute video you need to watch to understand the @solana Account Model youtu.be/fk8TibAJHes?si=u_O9…
4
1
64
3,962
darkstar retweeted
My friend built an AI agent. Took 2 hours. It scanned 10,000 endpoints, found critical vulnerabilities, wrote the report, and sent remediation steps automatically. Bug bounty payouts started hitting same week. $200k in 3 months. Zero manual work. The AI does recon, exploitation, reporting. All automated. He just reviews the output over coffee. Okay hear me out? This guy doesn't exist. I made all of this up. Because every other "I vibe coded and hit $500K MRR" post is also made up. Stop believing everything you see online, and start hacking real targets.
26
39
7
364
55,528