Vyper Smart Contract Auditor & Security Researcher

By Panther · Updated

I’m Panther, an independent smart contract security researcher with Vyper review experience through a PancakeSwap engagement with Pashov Audit Group. The September–October 2025 scope covered exchange contracts, swap and liquidity mechanics, accounting, and access control. The report remains private; the linked engagement record identifies the delivery partner, dates, and disclosed scope.

Request a security review →

Review the Vyper implementation and the exchange it operates

For a Vyper DEX scope, I follow how token transfers, reserves, liquidity shares, fees, rounding, external calls, and privileged operations interact across deposits, swaps, and withdrawals. The compiler version, dependency versions, deployment settings, and supported token behavior need to be part of the scope. Language-level checks complement the economic accounting review; using Vyper does not by itself establish that a pool’s asset flows are safe.

Selected engagements and findings

Selected portfolio records retain their original roles, outcomes and disclosure status. Firm reports describe team-wide work; private engagements and triage are labeled separately from public findings.

  1. PancakeSwap

    Firm-side / private security review. Vyper. DEX Exchange contracts, swap and liquidity mechanics, accounting, and access control. Pashov Audit Group. private report

    Open canonical portfolio record

Relevant work, research and evidence

The canonical private engagement ledger records PancakeSwap as a Vyper DEX review with Pashov Audit Group in September–October 2025. Its disclosed scope is exchange contracts, swaps, liquidity, accounting, and access control. No public Vyper report or individual severity breakdown is claimed for this engagement. My wider Solidity and DEX pages provide related EVM and trading-system context, while keeping those records separate from Vyper-specific evidence.

What Vyper audit experience does your portfolio support?

The supported Vyper-specific record is the PancakeSwap firm-side review with Pashov Audit Group. It establishes the named engagement, delivery partner, dates, and disclosed DEX scope; the report remains private. I do not use Solidity contest placements as evidence of public Vyper findings. For a new request, the repository and exact scope determine whether the review is a fit.

Can a security review include both Vyper and Solidity contracts?

Yes, when both are explicitly included in the agreed scope. The review should cover each implementation and the calls, asset transfers, permissions, and assumptions between them. Shared EVM execution does not remove the need to review language-specific behavior, compiler versions, and the full integration.

What should I send for a Vyper DEX audit request?

Include the repository and commit, Vyper compiler version, deployment configuration, pool or pricing model, token assumptions, liquidity and fee formulas, dependencies, privileged roles, and target dates. Explain any external integrations or unusual token behavior so the scope can follow the actual asset and authorization boundaries.

Work directly with an independent researcher

Send your ecosystem, repository or documentation, approximate scope, and target dates. I work directly with protocol teams and contribute to security-firm engagements. We agree on the scope, deliverables, and disclosure terms before review; private reports stay private unless publication is permitted.

Discuss your audit scope with Panther or inspect the complete portfolio.

Related security expertise