@peak_bolt

@peak_bolt

Words of Wisdom

---

"Speed is crucial in the initial audit phase"

Build a mental model of the code base quickly by speed-reading the contracts and avoid deep-diving at this point.

You can note down the low hanging bugs and put TODO tags for complex logic to review at the subsequent passes.

"Maintain the momentum"

Maintain momentum and save time by working on the easy tasks first and not be slowed down by the complex issues that require deep thoughts.

At the same time, you will gain confidence on the code base and not be overwhelmed by the details.

"Spend bulk of the time on reasoning complex attack vectors"

Allocate as much time as possible to review the complex logic (math, multi-contracts interactions, novel design, etc). You need creativity, knowledge and a good mental model to find the most complex bugs. These are the ones that are not obvious and typically involves multiple step or specific edge case to exploit. With the saved time from the initial phase, you increase your odds of spotting the more complicated issues.