Pre-audit checklist
What to have ready before an audit starts, and the preparation that reliably cuts both the cost and the finding count.
Request itEngineering notes, vulnerability classes we keep finding, and the reference material we use internally. Published because the next team should not have to relearn it.
Every article is written by someone who worked on the problem, not by a content team reading a brief.
Vulnerability classes, audit method, and the bugs that keep reappearing across otherwise unrelated protocols.
4 articlesTokenising real-world assets, the standards that govern it, and designing rules a regulator can audit later.
3 articlesProtocol mechanics: liquidation design, oracle-extractable value, and cross-protocol accounting.
2 articlesIndexers, reorgs, backfills and cross-chain messaging, written from running them rather than reading about them.
2 articlesWork from further upstream, published before it becomes anybody's roadmap.
1 articleThe full index, newest first, across every area we write in.
All 12 articlesThree documents we use internally. Ask and we will send them, with no form and no sequence afterwards.
What to have ready before an audit starts, and the preparation that reliably cuts both the cost and the finding count.
Request itThe document we write before any contract is implemented. Yours to use, whether or not we build it.
Request itA redacted report showing how we classify findings, write proofs of concept and describe remediation.
Request itIf you are working through a problem in this space, tell us. It may well become the next piece.
hello@xoralabs.io