In our previous blog post, Security Audit Reports: A Guide for Everyone, we provided a comprehensive guide on how to read a security audit report. We discussed the various sections of an audit report, what to look for, and how to interpret the findings to gain insights into the security
For this audit, we performed research, investigation, and review of Avalanche Core Web for Ava Labs followed by issue reporting, along with mitigation and remediation instructions as outlined in this report. To read the full report including our findings, click here: Report
In 2014, we published our first security audit report. Since then, we have completed more than 200 audits and published more than half of those. The primary audience of an audit report is the client’s project development team. However, stakeholders and other interested parties can also find value in reading
In January, we celebrated the 10-year anniversary of our first ever published security audit report. At the time of our first review, security consulting for privacy-enhancing and distributed technologies was a fledgling industry, and there were very few companies, like us, offering our specialized knowledge and expertise for security analysis
Ava Labs has requested that Least Authority perform a second security audit of their Avalanche Core Mobile Wallet. To read the full report, including our findings, click here: Report
Our team performed a comprehensive review of the d.id .bit Contracts. d.id is building an account system on the Common Knowledge Blockchain (CKB), a generalized bitcoin-like blockchain, founded by Nervos. To read the full report including our findings, click here: Report
Least Authority performed a security audit of World’s SMPC Protocol for the uniqueness check of iris codes. To read the full report including our findings, click here: Report
Our team conducted a security audit for Ava Labs of the AvalancheJS SDK, which handles transaction creation, importing and exporting, and state storage features for signed or unsigned transactions that are consumed by other applications. To read the full report, including our findings, click here: Report