Overview#

In July 2025, Oku Trade, engaged Obsidian Audits for a 5-day audit of their custom order type smart contracts.

Following the audit and fix review, the same codebase underwent a public audit competition with Sherlock, being reviewed by 300+ participants.

This case study highlights how Obsidian’s audit identified and helped resolve a high severity issue and others in Oku Trade's codebase, resulting in no major vulnerabilities being reported in the audit competition.

Results#

Extract from Obsidian Audits' report, summarizing the issues identified during the review:###

A total of 13 issues were identified and categorized based on severity:

• • 1 Critical severity (found during the fix review)
• • 1 High severity
• • 1 Medium severity
• • 3 Low severity

The critical and high severity issues had the potential to cause significant financial loss or severely disrupt the protocol’s functionality. All high and medium severity issues were addressed, while low and informational issues were acknowledged or fixed where applicable.

---

Sherlock audit contest's results, conducted after Obsidian's audit and fix review:###

A single medium severity issue was found by participants in the audit competition. No critical/high severity vulnerabilities were found.

Contest report link: https://audits.sherlock.xyz/contests/1076