Use complementary methods
Manual review and automated tools surface different failure modes. I used them together rather than treating one scanner as the audit.
Case 07 · Smart contract security
FearsOff
The review followed permissions, balances and unusual state changes.
I performed smart contract security reviews for exchange and DeFi engagements through FearsOff, combining manual analysis, automated tooling and remediation guidance.
Result
Delivered audits and remediation guidance for engagements covering Crypto.com exchange contracts, HTX integration modules and Smardex AMM and liquidity contracts.
My part
What I did
A successful transaction is only one path through a contract. A useful review needs to challenge permissions, accounting and adversarial state transitions, then explain what the team should change.
01
Manual security review
Reviewed contract behavior, authorization boundaries and paths that affect assets.
02
Adversarial tooling
Used Slither, Mythril, Echidna and Manticore, with formal verification techniques on critical functions.
03
Actionable reports
Delivered findings with remediation and gas-optimization guidance for engineering teams.
How it worksSimplified walkthrough. No live transactions.
From contract review to actionable remediation
Scope + manual review
Identify the assets, privileged roles and state transitions that define the contract’s trust boundaries.
Assets + permissions + state transitionsThe review starts from what must remain true.Static analysis + fuzzing
Combine manual reasoning with automated tools to search for paths that violate those assumptions.
Manual review + adversarial testsTool output needs interpretation in the contract’s context.Finding analysis
Connect a suspected issue to a specific affected asset, permission or accounting path and prioritize its consequence.
Issue → reachable behavior → impactA finding must explain why the behavior matters.Audit reporting
Translate the technical finding into concrete implementation guidance for the team responsible for the contract.
Finding + remediation recommendationThe report must be usable by the engineers fixing the code.Trade-offs
Decisions I made
Make findings operationally useful
Reports connect the issue, consequence and proposed remediation so the delivery team can act on them.
Links and records
See the work
Career record
Exchange and DeFi audit scope
Client scope and methods are recorded in my CV. Engagements were performed through FearsOff.
Review walkthrough
Method and decision process
The workflow above explains my approach without revealing confidential reports, exploit details or unremediated findings.
Engagements delivered through FearsOff, as documented in my CV; the named organizations describe audit scope.
Audit reports and vulnerability details remain confidential.