While auditing ambitfinance I wanted to give you all a little insight on what is important if you audit a codebase which has a few cross-contract interactions.

As you can see in the picture, it is important as a first step to highlight all incoming and outgoing calls for the specific contract you are auditing at this moment.

I always do that by visualizing these calls, as you can see. The next step will be to follow all incoming / outgoing calls and inspect which to which state transitions they lead in the related contracts.

A corresponding post to this topic will come within the next few days.

14 days, 88 pages of report, x high risk issues, xx medium issues, xx low issues later….

Theres actually no time to rest, the next audit is already waiting. Looking forward to work together with
BetBitX
for their token + vault contracts 🤝

The feeling of doing the resolution round, diffing the new vs the old file and you see a large red/green blob.

It never gets old. Lay back and assess the changes, often it looks more overwhelming than it actually is.

Hello ser how earn money with web3 security ser, tutorial pls?