Pre-auditThree days of senior audit time for $1,500, credited in full toward your Zealynx audit.3 audit days, credited toward your auditSee how →
Solana Audit

Solana audits, account by account.

Senior manual review of your Anchor or native Solana program. Account validation, PDA logic, and CPI safety, paired with Trident-based fuzzing and our internal AI audit agents.

Anchor · native · senior auditors only · reports public by default

Why this exists

Solana’s power is its account model. So are its bugs.

Most Solana exploits come from one of three places: missing account validation, wrong signer checks, or an unsafe cross-program invocation. They’re subtle, and the framework only protects you from half of them. We read every account constraint and every CPI, and we fuzz the rest.

Scope

What’s in the audit.

What we check
Tools
Programs we audit
How pricing works

Scoped to your program.

Solana audits are sized to instruction count, account-graph complexity, and integration surface. No fixed packages. Talk to us for a scope and quote.

Start smaller
Want to see how we work first?

The Founder Security Sprint is a three-day senior pre-audit of your highest-risk code for $1,500, credited in full toward your audit when you go ahead.

See the Sprint →
FAQ

Questions.

We audit both. Anchor saves us time on the boilerplate (account constraints are encoded), so the review can go deeper into business logic. Native programs need more manual coverage of validation patterns.

Yes. We use Trident-based fuzzing for stateful property checks and invariant violations. Fuzz harnesses are delivered alongside the report.

CPI surface is a first-class scope item. We review the full set of inner instructions you invoke, the signer/PDA accounts you pass through, and what happens when the callee behaves adversarially.

Yes, including Token-2022 extensions (transfer hooks, transfer fees, confidential transfers, etc.). Token program integration is a common source of subtle bugs.

We review the Solana side of the bridge (the program) and the trust assumptions on the messenger (Wormhole, LayerZero, etc.). The off-chain relayer/keeper side is best paired with our Application security audit.

It depends on program size, account complexity and integration surface. Your proposal states the schedule, the review team and the fix-verification pass before anything starts.

Ready when you are

Ready to audit?

Tell us about your system and target date. We'll review your request and get back to you to confirm scope and next steps.