i went to check dusk's third-party security score since they market "ten audits before mainnet" pretty heavily, and certik's skynet score for dusk sits at 62 out of 100. i went in expecting that number to roughly track the audit count — actually, i had to stop and reread certik's methodology page because i assumed a security score would basically just be an audit tally, it's not, it's six separate categories blended together.
the audits themselves are real, dusk's own audit repo and zellic's migration contract report are both public, zero vulnerabilities found there. so the individual audits aren't in question. it's more that a stack of clean audit reports and a single composite trust score are answering different questions, and marketing copy tends to treat the two as interchangeable when they're not.
to be fair, i don't have a clean benchmark for what a "good" skynet score looks like for an l1 at dusk's stage, so i can't say 62 is bad, just that it's not obviously explained by the audit history alone.
does anyone know which of the six skynet categories is actually pulling that number down for dusk specifically? 🧐
#dusk $DUSK @Dusk
the audits themselves are real, dusk's own audit repo and zellic's migration contract report are both public, zero vulnerabilities found there. so the individual audits aren't in question. it's more that a stack of clean audit reports and a single composite trust score are answering different questions, and marketing copy tends to treat the two as interchangeable when they're not.
to be fair, i don't have a clean benchmark for what a "good" skynet score looks like for an l1 at dusk's stage, so i can't say 62 is bad, just that it's not obviously explained by the audit history alone.
does anyone know which of the six skynet categories is actually pulling that number down for dusk specifically? 🧐
#dusk $DUSK @Dusk
