@0xadrii

@0xadrii

LSW at Sherlock | Zenith at Code4rena

Words of Wisdom

---

"Focus on understanding 100% of the system"

It is compulsory to know how everything should behave.

Once you get that kind of understanding of the protocol, you'll be able to understand how tweaking certain values or pushing the system to unexpected states might lead to vulnerabilities.

"Put on the developer's shoes"

This has worked like a charm to me.

The idea here is to be able to think how everything should behave prior to actually diving in the implementation. This will allow you to identify things missing in the protocol, or to check unexpected behaviors that might lead to bugs.

"Have patience and learn from each contest"

Although it might seem that the auditing part of the contest brings you the most learnings, it is in the escalations and results phase where you'll actually grow.

See what you missed and incorporate that knowledge.