Shorter notes on product, method and this industry’s habits.
Not thought leadership. Mostly explanations of decisions we have made and arguments we have had about how this work should be done.
ChainwatchCrypto notes and writing
Short notes on product decisions, investigative method, and the habits of the crypto-recovery industry. The writing favours specific questions over general commentary, and states where a method stops working rather than only where it succeeds. Readers with a live case are directed to the free assessment rather than to more reading.
Why our homepage has no statistics on it
Every competitor opens with a recovery rate and a total-traced figure. Here is why ours does not, and what we put there instead.
Typed findings, and the argument we keep having about them
Separating fact from interpretation slows report writing down. It is worth it, and here is the specific failure it prevents.
The question we ask every vendor: what can you not do?
A short test that separates measurement providers from the rest of this market, and how we try to pass it ourselves.
Building a risk score you are allowed to disagree with
Publishing weights felt like giving something away. It turned out to be the most useful thing on the platform.
What we tell people when tracing will not help
Roughly the hardest conversation in this work, and why triage exists specifically to have it early.
Demo data, and why every number on this site is labelled
Unlabelled sample data in a fintech interface is a small lie that becomes a large one. Our rule, and how it is enforced in the build.
Full posts are published as they are written. Where you see a summary without a link, the piece is planned rather than published — we would rather show the intended subject than publish filler under a real headline.