Our First External Audit, in Full: Every Finding Hexens Raised, and What We Did About Each One
Kerne Protocol kerne.fi
Listen to this summary
The final Hexens report on Kerne is public. Rather than post a badge and a link, we are publishing the response matrix: every finding, its severity, what we changed, and the two we deliberately did not rush a code change for, with the reasoning in full. That includes the finding that turned out to be a regression we introduced ourselves in an earlier hardening pass, and the part where our own first fix attempt was wrong and got caught in re-review before it shipped. The review covered five contracts. Every finding landed in one of them, the vault, and the stablecoin, the staked token, the peg stability module, and the escrow token drew none between them. Here is the whole thing, including…
More ways to use this
Open on another device
Scan to open this page. Your saved notes and account access are not included.
Fix Tenable One findings where developers work: Tenable and OpenAI Daybreak Defense Factory
Java4Shell (CVE-2026-114938): Frequently asked questions about OpenJDK remote code execution vulnerability
php2shell one week later: Why one exploit doesn’t work everywhere