Understand the system
Map roles, assets, trust boundaries, and intended invariants before reading for bugs.
About & method
Methodical by design.
Adversarial by nature.
Good security work makes a system easier to trust: test the risky paths, preserve the evidence, and write remediation that a developer can use.
Approach
How a review actually runs.
Review the attack surface
Trace high-risk flows manually, then use targeted tooling to validate assumptions.
Test and challenge
Write proofs of concept for credible findings and test edge cases that matter to users.
Report with clarity
Turn technical evidence into practical remediation guidance with severity and impact explained.
Toolbox
Targeted tooling, applied where it counts.
SolidityFoundrySlitherHardhatEthers.jsSolana
Start a review
Bring the context that makes testing count.
Scope
Share the repository, program list, and the exact systems or flows that need attention.
Risk context
Point to trusted roles, asset movement, integrations, and assumptions that cannot fail.
Environment
Provide authorized local or fork-based testing details. Production testing is never assumed.