Mira — v1 Core and Periphery

Audit report published Sep 2024. Fuel · Sway.

Findings at a glance

Severity	Count
Low	4
Informational	2
Total	6

Summary

Safe Edges reviewed Mira v1 core and periphery between 26 August and 11 September 2024. Six issues were identified: four Low and two Informational, with no Critical, High or Medium issues. At the time of the report one issue was resolved, three were acknowledged or accepted by the Mira team, and two remained open.

Read the full report (PDF).

Findings

Low (4)

• L-01 Deadline Depends on Block Number Instead of Timestamp — Acknowledged
• L-02 Lack of Revert in get_y Function Poses Convergence Risk — Open
• L-03 Strict Deadline Check Prevents Exact Block Height Matching — Resolved
• L-04 Single-Step Ownership Transfer in AMM Contract — Acknowledged

Informational (2)

• I-01 Prevalence of Magic Numbers in Codebase — Open
• I-02 Potential Infinite Loop in Pool Functions — Acknowledged

More published reports

Related services

Get a fixed quote in 24 hours

Send the repository and a commit hash through the contact form, message @bugtester25 on Telegram, or book a 30-minute scoping call. 200+ protocols audited · $4B+ secured · 0 hacks post-audit. Prefer email? info@safeedges.in.