Key Findings<\/strong>:<\/p>\n\n\n\n

The issues found in the code were LOW or INFORMATIONAL findings. This shows that the overall risk profile of the application at the time of this assessment is low.The following are the major themes and issues identified during the testing period. These, along with other items, within the findings section, should be prioritized for remediation to reduce the risk they pose.<\/p>\n\n\n\n

Safe math was used often, but should be used more consistently throughout the code to prevent potential vulnerabilities from being introduced in future updates.<\/p>\n\n\n\n

Insurance policy coverage duration, claim expiration dates and claim payout dates may be affected by a lack of precision when dev Epochs are used in place of UNIX time.<\/p>\n\n\n\n

Single administrator accounts have significant capabilities. These functions should be limited by requiring multiple signers to prevent collusion. We have been informed that this is currently occurring off-chain, but this should occur on-chain in the future for transparency.During the test, the following positive observations were noted regarding the scope of the engagement:<\/p>\n\n\n\n

The code is well organized.<\/p>\n\n\n\n

Client contacts were very amenable to conducting joint secure code reviews with the Kudelski Security smart contract auditing team.<\/p>\n\n\n\n

Anchor framework usage is very consistent and follows the recommended syntax.<\/p>\n\n\n\n

Critical issues in architecture or code logic were discussed immediately via teleconference.<\/p>\n\n\n\n