@cergyk
Last updated
Last updated
Get as many views of the code as possible- (history, coverage, run tests), a contract is never unidimensional The goal of a security review is to get insights overlooked by the developer. Reading the code directly is the most obvious way to do it but is also the way the developer thinks about the code.
Use the power of comparison, whether inside of a contract, or comparing a protocol design to a similar one.
Even without understanding the purpose of a piece of code, if we know that two different implementations are supposed to do the same thing, we can check for inconsistencies. Also as SRs we see a lot of different implementations for a similar projects so that is an advantage