
kamensec
@kamensec
Followers
916
Following
1K
Media
47
Statuses
560
Independent Security Researcher | judge @cantinaxyz | Secureum Mentor @TheSecureum | Ex Blockchain Security Engineer @sigp_io
Dubai 🇦🇪
Joined August 2020
Here are 5 of my audit 'strategies' framed as questions for staking protocols with slashing enabled. Bookmark this thread for your next staking / restaking / slashing audit as way to make sure you understand important dynamics.
2
4
63
Finding a good mentor ain't easy. But even world class athletes have coaches. Also the better you get, generally the harder it is to stomach someone telling you that you did something badly or you can do better. But again, a good coach knows how to do that well.
4
0
19
This is something especially noteworthy if you have dependencies out of your control, like in the case of staking / restaking, a lot of care should be taken when considering beacon chain quirks. All edge cases in the dependencies should be studied.
Most of the trickier bugs derive from logic, not from technical aspects. To write safe code: make sure your logic is solid before writing the code. To find logic bugs: reconstruct the logic and check if all paths are addressed.
2
0
7
Interesting seeing my past opinions on collaboration. I use to spam a lot of ideas, including what didn't work. After actually working with @0xCharlesWang, probably the biggest shift in my workflow in the past few months has been to prioritise working solo and quietly, saving.
@kamensec I like this approach. How does it fit with the usual engineering/research people demographic? . What I’m seeing:. > 20% are lone wolfs - If they communicate it’s short and not often. They prefer to work alone and bring that work dynamic into collaborative audits. They can find.
3
0
8
Damn this is some opsec for all you noisy annoying mechanical keyboard kids… and if that wasn’t enough check the video:
1
0
5
Hope you can learn from these, but in the end do what ever you want with this information.
0
0
3
3. "Your rich uncle died, you inherited his debt": This one hurts because I was looking for this exact issue. The classic msg.value doesn't change in a for loop which they obviously check for and the batchable function overlap is so close. but not quite. My advice to you, is
1
0
3
2. "Mint your own business": This one line still hurts me years later. After this mistake I went down a huff / assembly rabbit hole. Always check any assembly block 3-4 times do not accept code comments, do not assume anything actually works (this sounds stupid but theres deeper
1
0
4
1. "What for": the stupid for loop optimisation. The increment is done in the for loop block, but the continue skips the increment. For/while loops are a great place for dos vectors be on the look out for poorly set index increments.
2
0
5
The best portable second monitor you can buy:
sotsu.com
The SOTSU FlipAction Go 14" is a fusion of timeless design and precision engineering. With meticulous craftsmanship, state of the art anodizing finishes, and four understated color options, the...
1
0
6
Obligated to repost this!.
I learned this before becoming a judge. I once found something that was *almost* an issue. The code allowed anyone to completely drain the contract. However, the contract wasn’t meant to hold any funds, so there was no impact. I reported this issue as medium severity, and it.
0
0
2
If you are stuck in an endless travel/conference loop, maybe this one's worth the read for you!. When I think back over the start of my career, the fact that I travelled full time to some 30 countries in my first 2 years of auditing is something truly bittersweet. On one hand.
1
1
16
bug hunting is not easy work but sure beats losing 83 million dollars on hyperliquid. Stay scrappy. Stay locked in.
0
0
3
A year ago @devtooligan told me to use weaudit extension from @trailofbits. That was a goated improvement to my workflow. Sometimes you think you need some fancy AI workflow, but really you just need organisation and a little gamificatiion. Can't believe there's still.
4
1
31