Measured, not asserted: how a number earns its place
A false-positive rate without a denominator is a marketing figure wearing a lab coat. Here is how ours is produced.
Every vendor in on-chain security reports a false-positive rate close to zero. Almost none report the denominator, and a ratio without one tells you nothing.
How ours is produced
The harness runs in continuous integration on every merge, against corpora of real captured benign traffic rather than synthetic fixtures. A false-positive regression fails the build, and so does a recall regression. The number is a condition the codebase keeps satisfying in order to compile, not a measurement somebody took once.
Every detector carries its own evidence
Detectors ship with golden cases, positive and negative, all exercised on every run. Detection quality and coverage of input are tracked as separate axes: a detector that never fires can be precise or unreachable, and conflating the two reports a property of the data as a property of the detection.
What you can check yourself
Every alert ships as a threshold-signed, expiring attestation that you can verify without trusting us. Every screening verdict names the source it consulted and the time it consulted it, and where no live source was reachable the verdict is insufficient data, never a pass.
That last one costs a cleaner-looking dashboard and ships anyway, because a customer who believes something was screened when it was not has been misled at the moment it matters most.
More from the walls.
Post-block alerting is a receipt, not a defence
It tells you precisely how much you lost and exactly when you lost it. Both facts arrive too late to be worth anything.
6 min read
Your audit certified the code. The attacker is signing in as you.
Four incidents, four different mechanisms, and not one of them was a Solidity bug the auditors were asked to look for.
7 min read
Why the model is never the first line of defence
Software that guesses does not get to declare an emergency. The layer order is a commitment, not a preference.
5 min read
The next breach is already being dug.
Every engagement is scoped to your protocol by the team, and pricing follows that scope.