.jpg)
How Octane Saved $41,400 for Covenant
Hey, it’s Gio.
Recently, I talked about my bet with Covenant founder Alan Hampton.
His team was going through multiple rounds of audits and preparing for a public audit contest. They were moving, shipping daily, and needed real-time security intelligence. So Alan decided to try Octane’s CICD integration.
The result?
Octane uncovered real vulnerabilities early — including a critical permissive multicall path that let an attacker chain external calls as Covenant itself to drain user and protocol funds.
From there, Alan quickly became an Octane power user, running security analysis on each code change and catching everything from authorization gaps to edge-case math conditions.
Last month, Covenant completed its audit contest with zero high or medium severity bugs reported.
To be honest, even I was a little surprised that Covenant ended the contest with just informational findings.
How We Saved Covenant $41,400
Before we dive into the numbers, here’s how Alan actually used Octane — in his own words.
Alan didn’t just run a scan. He deeply integrated Octane directly into Covenant’s workflow.
“I spend about 2-5 hours a week with the product and have been using it for the past 3+ months. I’ve been able to remediate over 40+ vulnerabilities in that time.”
He emphasized Octane’s strength in catching the kinds of issues that matter most:
“The most impressed vs other AI tools I have used are its capacity to catch cross-contract bugs, and get context on what I am trying to do that even manual audits have not caught.”
By the time Covenant began its audit contest, the codebase had gone through 80+ scans, resulting in 107 total fixes, including two critical vulnerabilities caught and remediated in real-time.
Covenant budgeted $43,000 for its audit contest. Since Octane caught the critical and high-severity issues before code ever hit the contest, the findings reported were informational.
Their final payout for the entire contest? Just $1,600.
That means Covenant saved $41,400 — simply by shifting security left and eliminating vulnerabilities early.
After seeing the benefit from Covenant integrating Octane early, I want to make the same bet with you.
Make a Bet on Security
My goal at Octane is simple: drastically reduce onchain hacks by helping teams build and ship secure code.
And after seeing the results from teams like Covenant, I’m opening the same bet to everyone reading this blog.
Let Octane analyze your codebase.
If we don’t surface at least one meaningful finding in your initial scan, your first month is on the house.
No disruption to your workflow.
No waiting weeks for an audit report.
Just:
- Real findings in minutes
- Deep analysis across inherited contracts, dependencies, and complex execution flows
- Exploit scenarios that show exactly why something matters
- Continuous protection on every PR through your CI/CD pipeline