Review launch critical paths.
Trace fund flows, privileged roles, upgrade controls, oracle dependencies, signer assumptions, and integration paths before mainnet usage.
- Ship or hold verdict
- Critical path review
- Retest notes
Ethereum and Solana security research
We audit Solidity and Vyper contracts on Ethereum, Solana programs, DeFi accounting, bridges, wallets, relayers, APIs, and exploit reports. You get reachable attack paths, asset impact, remediation guidance, and retest notes.
Client outcomes
For Ethereum and Solana teams shipping contract changes, program upgrades, DeFi releases, bridges, wallet flows, protocol integrations, or bug bounty reports.
Trace fund flows, privileged roles, upgrade controls, oracle dependencies, signer assumptions, and integration paths before mainnet usage.
Confirm reachability, preconditions, attacker costs, asset impact, and the smallest safe remediation path.
Reproduce reports on forked state or controlled fixtures, confirm severity, asset impact, and disclosure notes.
Review transactions, roles, on chain configuration, logs, and reachable exploit paths after alerts or incidents.
Services
Specialized in Ethereum contracts, Solana programs, DeFi accounting, bridges, wallets, relayers, oracles, RPC, and API surfaces that trigger asset movement.
Solidity and Vyper review for access control, proxy upgrades, storage layout, external calls, liquidation logic, and invariant breaks.
Rust and Anchor review for account validation, CPI boundaries, signer checks, PDA derivation, instruction ordering, and token flows.
Analyze vault shares, AMM math, lending and liquidation paths, rewards, oracle assumptions, fees, and slippage.
Assess message verification, replay protection, chain routing, signer prompts, relayer authorization, RPC and API permissions, and refunds.
Launching on Ethereum or Solana?
Audit surface
Ethereum contracts, Solana programs, DeFi accounting, bridges, wallets, relayers, oracles, RPC, and API paths.
Review access control, proxy upgrades, storage layout, state transitions, external calls, oracle usage, and invariant breaks.
Focus: reachability, fund flow impact, minimal safe fix.Engagement model
Confirm chain, repos, addresses or program IDs, asset flows, roles, permitted testing, timeline, and success criteria.
Build the trust map: admins, signers, PDAs, proxies, oracles, relayers, state transitions, and external services.
Validate reachability with PoCs, fork tests or Anchor fixtures, invariant reasoning, and economic impact analysis.
Deliver affected code, preconditions, exploit path, severity, asset impact, remediation guidance, and verification steps.
Review patches, changed assumptions, regression risk, and remaining exposure before launch or disclosure.
Reporting
Each finding states affected code, preconditions, exploit route, asset impact, remediation, and retest evidence.
handoff:
status: reproducible
engineer_action: patch_accounting_boundary
stakeholder_action: defer_launch_until_retest
retest: ready_after_fix
Operating standards
Work starts from approved targets and produces evidence without disrupting production systems or exposing unnecessary data.
Testing begins after target ownership, addresses, program IDs, endpoints, and permitted techniques are confirmed.
Findings stay with approved stakeholders. Public references require explicit consent or coordinated disclosure context.
PoCs demonstrate impact without unnecessary fund movement, destructive actions, or data exposure.
Start an engagement
Include chain, repo, contract addresses or program IDs, docs, app or API links, authorization, timeline, and required decision.