{"id":248,"date":"2022-05-20T12:00:06","date_gmt":"2022-05-20T10:00:06","guid":{"rendered":"https:\/\/ackeeblockchain.com\/blog\/?p=248"},"modified":"2025-02-19T14:26:58","modified_gmt":"2025-02-19T12:26:58","slug":"helio-protocol-audit-summary","status":"publish","type":"post","link":"https:\/\/ackee.xyz\/blog\/helio-protocol-audit-summary\/","title":{"rendered":"Helio Protocol Audit Summary"},"content":{"rendered":"

Helio<\/a> engaged Ackee Blockchain<\/a>\u00a0to review and audit<\/a> their protocol between May 16 and 20, 2022<\/strong>. The entire audit process was conducted with a total time commitment of 5 engineering days<\/strong>.<\/span> We now publish a summary of our results.\u00a0<\/span><\/p>\n

Methodology<\/b><\/h4>\n

First, we took the time to understand the entire Helio platform.<\/span><\/p>\n

Reviewing the specifications, sources, and instructions provided to us is essential to ensure we understand the project’s size, scope, and functionality. This is followed by a detailed manual code review, which is the process of reading the source code line by line to identify potential vulnerabilities.\u00a0<\/span><\/p>\n

When the code review is complete, we run client’s tests to ensure the system works as expected and potentially write missing unit or fuzzy tests using our testing framework <\/span>Trdelnik<\/span><\/a>. We also deploy programs locally and try to attack and break the system.\u00a0<\/span><\/p>\n

Scope\u00a0<\/b><\/h4>\n

We audited commit <\/span>8a6b1a20551cde8cff68d55e43baa5524692e82c<\/code> <\/span><\/i> of the heliofi\/helio-protocol<\/code><\/span>\u00a0repository.<\/span><\/p>\n

During the security review of the <\/span>helio-protocol<\/span><\/i> program<\/a>, we paid particular attention to the following questions:<\/span><\/p>\n