panther.audits
I find protocol-breaking bugs before mainnet. Deep expertise across Move, Rust/Solana, EVM, Cairo, TON, ZK, and AI security. Audited Aave, Deepbook, Decibel, Tensor, PancakeSwap, Venus, and 50+ others securing billions in TVL.
Audit firms I've worked with
Testimonials
// feedback from lead auditors and protocol teams
Best fit for
// where I add the most value for protocols and audit firms
Sui & Aptos Move depth
Object ownership, PTB composition, shared objects, abilities, resource accounts, upgrade paths, and Move-specific state corruption bugs.
Complex DeFi reviews
Lending, credit systems, perps, CLOBs, DEXes, vaults, staking, RWA, and cross-chain systems where accounting and liquidation paths need deep review.
Audit firm reviewer capacity
Private engagements under NDA, second-review support, contest-style depth, report-ready findings, and fast ramp-up on unfamiliar codebases.
Formal verification support
Invariant design, Certora CVL, Sui Prover, Move Prover, and property-driven review for protocol-critical accounting and access-control logic.
ZK and AI security review
Constraint soundness, proof-system assumptions, circuit edge cases, AI model attack surfaces, data integrity, output integrity, and ML supply-chain risk.
How I work
// structured enough for firm workflows, deep enough for protocol-critical code
Build the threat model first
Map trust boundaries, assets at risk, privileged roles, user flows, external dependencies, upgrade paths, and protocol-specific failure modes before hunting isolated bugs.
Prove the core invariants
Stress the accounting, solvency, access-control, oracle, liquidation, settlement, and state-machine invariants that must hold for the protocol to stay safe.
Attack real execution paths
Trace adversarial flows across deposits, withdrawals, liquidations, upgrades, callbacks, cross-chain messages, keeper actions, and partial-failure scenarios.
Deliver findings teams can act on
Each report is written with clear impact, root cause, exploit path, affected code, mitigation guidance, and PoC or test direction where the engagement allows it.
Languages & ecosystems
// multi-chain coverage across the highest-value platforms
defi_protocols
nft_infra
staking_restaking
xchain_infra
Top 3 finishes
// 6× top-3 placements in competitive audit contests
Proof points
// short examples of the bug classes and review depth I bring to audits
Wrong-address state reads would have bricked first non-EVM deployment
Configuration was stored at one address while getters read from another. The issue was confirmed as High severity and placed 3rd out of 409 auditors.
Forgotten ownership state could resurrect a previous owner
A subtle access-control cleanup issue in OpenZeppelin Cairo contracts became a public advisory and CVE-2024-45304.
Return-after-mutation pattern permanently corrupted order book state
A Move-specific control-flow bug where an error path used return after deleting state, committing the mutation instead of reverting.
Critical & High severity
// selected protocol-breaking findings across ecosystems
// independent vulnerability disclosures across L1/L2 protocols
From the blog
// deep dives into real vulnerabilities, audit war stories, and research
How to Audit a Perp Protocol on Sui Move
A practical checklist for Sui perps: object model risks, hot-potato request flows, PTB composition, shared collateral vaults, liquidations, and oracle/funding-rate attack surfaces.
read full post →The Upgrade Trap — How Versioned Objects Can Brick Protocols on Sui
How a common Sui upgrade pattern can permanently brick dependent protocols when immutable packages rely on migrated shared objects.
read post →The Move Bug That Would Have Bricked AAVE on Aptos
A $24K finding from the AAVE Aptos V3 audit on Cantina. Data stored at one address, every getter reading from another — dead on arrival.
read post →Ready to secure your protocol?
Q3 2026 audit slots, security consulting, formal verification, or collaboration. Move / Rust / Solidity / Cairo / Vyper / TON / ZK / AI security. Reach out on Twitter or Telegram — I reply within 24h.
- protocol name, ecosystem, and audit scope
- repo/docs access, estimated LoC, and target dates
- whether you need solo review, firm-side reviewer capacity, or formal verification support