Cairo Smart Contract Auditor & Starknet Security Researcher

By Panther · Updated

I’m Panther, an independent Cairo security researcher and Starknet smart contract auditor. My public record includes an independent OpenZeppelin Cairo disclosure, tracked as CVE-2024-45304, and contest findings in Starknet Staking, ArkProject, and Chakra. I focus on contract state, access control, staking, bridges, and the assumptions that connect an administrative action to the state users actually rely on.

Request a security review →

Ownership, authority, and state transitions

A Cairo review needs to follow who can invoke each transition, what state remains afterward, and whether later calls can undo the intended security boundary. Two-step ownership, upgrades, staking state, and cross-contract interactions deserve lifecycle analysis rather than isolated function checks. For bridge and cross-chain scopes, the review must also account for authorization, message handling, and how remote state is trusted.

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. OpenZeppelin

    Independent disclosure. Cairo. public · CVE-2024-45304 Cairo contracts library. 1 Medium ↗ advisory

    Open canonical portfolio record · ↗ advisory

  2. Starknet Staking

    Public contest research. Cairo. Staking. 9th place. 1 High 1 Medium 1 Low

    Open canonical portfolio record

  3. ArkProject

    Public contest research. Cairo. NFT bridge. 20th place. 1 High 2 Medium 1 Low

    Open canonical portfolio record

  4. Chakra

    Public contest research. Cairo. Cross-chain settlement. unranked. 2 High

    Open canonical portfolio record

Primary reports and result sources

Relevant work, research and evidence

I independently disclosed the OpenZeppelin Cairo OwnableTwoStep issue published as CVE-2024-45304. A pending owner could accept ownership after renunciation because pending ownership had not been cleared. OpenZeppelin classified the issue Medium and fixed it in v0.16.0. My first-person writeup documents my disclosure; the official advisory and fix independently establish the technical issue and remediation. Separately, my Starknet Staking contest record includes one High, one Medium, and one Low; ArkProject records one High, two Mediums, and one Low; Chakra records two Highs.

What does the OpenZeppelin disclosure demonstrate?

It provides a public example of tracing an access-control invariant across multiple calls: renouncing ownership was expected to end administrative control, but a previously pending owner retained a path back in. My writeup explains the root cause and my independent disclosure. The linked OpenZeppelin advisory and fix provide the official technical description, Medium classification, and v0.16.0 remediation.

What should be in scope for a Cairo or Starknet security audit?

Send the repository and exact commit, compiler and dependency versions, deployment configuration, privileged roles, and any interacting contracts or L1–L2 message paths. For staking or bridge protocols, include the state machine, asset-accounting assumptions, and recovery behavior. The review should follow complete sequences such as nomination, renunciation, and acceptance, not only individual access-control checks.

Is an OpenZeppelin library dependency enough to establish protocol security?

No. Check the exact dependency version, known advisories, integration assumptions, and how application code uses each component. CVE-2024-45304 illustrates why a familiar ownership component still needs lifecycle analysis. A fixed library does not establish the safety of the rest of an application.

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