Smart contracts are examined for areas where external code can execute improperly or harmfully.

Testing the range of potential input data used to call functions ensures that contracts are not susceptible to attack vectors exposed by the EVM Application Binary Interface.

A Security Specification Model is generated, against which contracts are tested for adherence to intended functionality.

Code execution is mapped out to all potential paths to assess different final states that can be achieved.

Contracts are work-shopped in cooperation with development teams to account for possible Worst Case Scenarios and related fallback mechanisms.

A report is compiled describing the depth and breadth of the audit, key findings, and specific fixes made by the project team.