Smart Contract Security Researcher

Security reviews for complex protocols.

I review vaults, lending, staking, trading, wallets and infrastructure. My work includes audits through TrustSec, Zenith, Cantina and Spearbit, alongside competitive reviews and security research.

Public Track Record

Evidence-backed security work across competitive and private reviews.

$335K+

Code4rena awards

104

valid High findings on Code4rena

216

valid Medium findings on Code4rena

30+

Cantina review scopes

30+

Zenith review scopes

Public Review Portfolio

Find the experience that fits your protocol.

Browse reports and public review records by protocol, feature, provider or type of work. Competition entries include verified top-five finishes only, with placements shown alongside each entry.

101selected public records
63audit records
32top-five competition finishes
6judging records

Loading public records…

Download portfolio β†—
Protocol / reviewProvider / dateFeaturesSource

Multiple reviews of the same protocol are listed separately. β€œReview page” indicates a public summary or participation record. Features describe the published review scope. Sources checked on October 7, 2026.

Selected Competition Results

Public audit placements in adversarial review environments

Platform Project Placement Payout
Code4renaNouns DAOπŸ₯‡ 1st$31.7K payout
Code4renaMaple FinanceπŸ₯‡ 1st$21.5K payout
Code4renaLooksRare AggregatorπŸ₯‡ 1st$10.9K payout
Code4renaNFTXπŸ₯‡ 1st$10.7K payout
Code4renaRubicon v2πŸ₯‡ 1st$10.5K payout
CantinaGoat Tech Smart-contractsπŸ₯‡ 1st$28.1K payout
Code4renaFEI and TRIBE RedemptionπŸ₯ˆ 2nd$18.9K payout
Code4renaAura FinanceπŸ₯ˆ 2nd$18.1K payout
Code4renaCantoπŸ₯ˆ 2nd$11.6K payout
Code4renaBlur ExchangeπŸ₯ˆ 2nd$3.8K payout
Code4renaRubiconπŸ₯ˆ 2nd$3.5K payout
Code4renaPaladin Warden PledgesπŸ₯ˆ 2nd$5.7K payout
Code4renaJuicebox V2πŸ₯ˆ 2nd$11.1K payout
Code4renaLSD Network - StakehouseπŸ₯‰ 3rd$5.1K payout
Code4renaOokiπŸ₯‰ 3rd$5.1K payout
Code4renaQuickSwap and StellaSwapπŸ₯‰ 3rd$4.9K payout
Code4renaFractional v2πŸ₯‰ 3rd$4.8K payout
Code4renaFrankencoinπŸ₯‰ 3rd$4.4K payout
Code4renaIlluminateπŸ₯‰ 3rd$3.6K payout
Code4renaCanto Identity SubprotocolsπŸ₯‰ 3rd$3.3K payout
CantinaBeraborrow BlockendπŸ₯‰ 3rd$7.7K payout

Selected Private & Managed Reviews

Private review and managed-review work across recognizable protocols and clients

These are private audits, managed reviews, and internal review scopes rather than public competitions. The mix is intentional: the goal is to show repeated trust across wallets, L2s, bridges, trading systems, staking infrastructure, launch systems, and other protocol-specific codebases.

Selected protocols and clients

  • NFTX
  • Plume
  • Virtuals
  • Infrared
  • Valantis
  • Mitosis
  • Opinion Labs
  • Treasures
  • Kintsu
  • Beraborrow
  • Clober
  • LinkPool
  • Diva Staking
  • Juice Finance
  • Foresight
  • EdgeX
  • Aionex
  • IVX Finance
  • Palette Protocol
  • PaintSwap
  • Angstrom
  • Clanker
  • Theo
  • Thrackle
  • Ventuals

Coverage

  • Wallets & account abstraction
  • Rollups, bridges & cross-chain
  • Stablecoins & lending
  • DEXs, AMMs & orderbooks
  • Hooks, intents & execution systems
  • Perpetuals, options & trading venues
  • Staking, DVT & reward distribution
  • Governance, veToken & protocol migrations
  • Liquidity management & aggregators
  • Prediction markets & tokenized vaults
  • NFT rails & launch infrastructure
  • ...and other protocol-specific logic

Research & Talks

Conference-grade security research beyond smart contract audit platforms

Before focusing full-time on protocol reviews, I worked on broader security research across browser and blockchain infrastructure. That background shapes how I approach exploitability, hidden assumptions, and non-obvious system boundaries in smart contract reviews.

Selected talks and published research

  • Black Hat USA 2021 Research on exploiting a critical TRON vulnerability through blockchain infrastructure attack paths.
  • DEFCON 29 Follow-on presentation work grounded in the same exploitation and failure-analysis mindset.
  • Black Hat Europe 2020 Earlier systems-security research on subtle compiler behavior and non-obvious vulnerability surfaces.

Why this matters for protocol reviews

  • Browser security research: multiple Chrome vulnerabilities and practical experience with complex, stateful attack surfaces.
  • Blockchain infrastructure research: a critical TRON vulnerability and experience reasoning across components rather than isolated code snippets.
  • Direct carryover into audit work: exploitability-first reviews focused on trust boundaries and lifecycle transitions.

Expertise

Where I usually find material risk

Accounting mismatches

Broken solvency assumptions, stale accounting, share inflation, reward drift, and state sync failures across vaults, staking, and lending systems.

Liquidation and settlement edges

Collateral valuation, liquidation ordering, partial repayment, fee settlement, bad debt handling, and asynchronous fund movement.

Execution and liquidity logic

Routing assumptions, orderbook state transitions, hook-driven execution, liquidity management, and price-impact edge cases.

Cross-domain trust boundaries

Bridge message flow, replay surfaces, auth registries, settlement guarantees, and the assumptions hidden in cross-chain integrations.

Privilege and upgrade surfaces

Upgrade paths, signer permissions, emergency roles, wallet delegation, EIP-7702 and ERC-6492 flows, and governance-controlled behavior.

Protocol-specific business logic

The part static tools usually miss: custom launch mechanics, launchpad state machines, prediction logic, staking semantics, and integration-only failure modes.

Approach

Protocol-first review, not checklist-first review.

01

Model the system before reading line by line

I start from money flow, authority boundaries, upgrade surfaces, and lifecycle transitions so the review is anchored to how the protocol is supposed to behave.

02

Turn assumptions into concrete attack questions

I focus on where assumptions can be violated: accounting drift, stale state, incorrect settlement, unexpected privilege reach, and integration-induced edge cases.

03

Prioritize exploitability over surface-level noise

The goal is not to maximize issue count. The goal is to identify material exploit paths and validate them with concrete reasoning, PoCs, or invariants where useful.

04

Help the fix actually land correctly

I prefer concise findings with clear root cause, exploit conditions, and remediation guidance, followed by targeted fix review on the changed scope.

Working Style

Best fit for high-context protocol work where correctness matters more than volume.

Best fit: focused protocol reviews, pre-launch security reviews, upgrade reviews, and fix reviews on systems with real complexity in accounting, execution, or trust boundaries.