Skip to content
Rust smart contract audits

Rust smart contract audits for Solana, CosmWasm and Stylus

Rust auditors matched to your runtime, not just your language.

in RFP budgets posted
$1.2M
saved, 44.5% vs single direct quotes
$525K
vetted firms quoting on the platform
70+
first quotes typically land within the hour
<1 hour

Rust audits by runtime

Select a Rust smart contract runtime
  1. Runtime 01

    Solana

    Programs receive every account as input, so most critical Solana bugs are missing checks on accounts the caller supplied.

    • Missing owner or signer checks
    • One account type passed off as another
    • Arbitrary cross-program invocation
  2. Runtime 02

    CosmWasm

    Contracts talk through messages and submessages. Reply handling and cross-contract calls are where state goes wrong.

    • State changed before a failing submessage
    • Unvalidated addresses
    • Unbounded iteration that halts a contract
  3. Runtime 03

    Arbitrum Stylus

    Rust contracts that call and are called by Solidity contracts. Reviewers need both models: EVM semantics and Rust's.

    • Reentrancy across the Rust and Solidity boundary
    • Storage layout mismatches
    • ABI encoding errors between languages
  4. Runtime 04

    NEAR

    Cross-contract calls are asynchronous, so state can change between a call and its callback.

    • State assumed unchanged across a callback
    • Callbacks callable by anyone
    • Failed promises that leave funds stuck
  5. Runtime 05

    Soroban

    Explicit authorisation and storage lifetimes are Soroban's own failure points.

    • Missing or misplaced authorisation
    • Data expiring from temporary storage
    • Token interface misuse
  6. Runtime 06

    Off-chain Rust

    The services that build transactions, crank programs or relay messages. If they can be manipulated, correct on-chain code still does the wrong thing.

    • Manipulated transaction building
    • Keepers acting on stale or forged data
    • Relayers trusted without verification

    Running nodes or validators too? See infrastructure security reviews.

52firms on Procur3 audit Rust.

  • OShield
  • Slot Zero Security
  • No.Witness Labs
  • Sigma Prime
  • CredShields
  • Shred Security
  • VulSight
  • Egis Security
  • CD Security
  • Adevar Labs
  • HackenProof
  • Burra Security
  • AuditWare
  • Guvenkaya
  • Monethic
  • +37 more
  1. 01

    Post

    Share your runtime, framework and scope once.

  2. 02

    Compare

    Firms that audit your runtime quote with price, timeline and team.

  3. 03

    Select

    Award the audit and track delivery in one place.

When a Rust program needs an audit

The same triggers as any contract audit, with a few that are specific to Rust runtimes.

  • Your program holds or moves user fundsAccount-validation bugs are cheap to find and expensive to miss.
  • You've written native Solana Rust without AnchorEvery check Anchor would generate is now yours to write.
  • You call other programs or contractsCPIs and submessages pass trust across a boundary.
  • The program is upgradeableWhoever holds the upgrade authority can replace the code.

How to choose a Rust audit firm

  1. Have the reviewers audited your runtime?

    A Solana auditor and a CosmWasm auditor look for different bugs. Ask for published reports on your runtime, not just in Rust.

  2. Does the scope include the code that builds transactions?

    Clients, keepers and relayers decide what the program is asked to do. If they're out of scope, say so in writing.

  3. Is fuzzing or property testing included?

    Rust has good fuzzing tools. Ask whether the quote includes them, and for which instructions or messages.

Procur3 helped us find specialized Rust auditors for our smart contracts on Solana. The experience statistics really supports with decision making and cut our review time by weeks.

Multihopper

Security isn't an afterthought for TermMax. Thanks @procur3 for helping us run a clean RFP to find specialized Daml auditors ahead of our Canton Network launch.

TermMax

Frequently asked questions

What is a Rust smart contract audit?

A security review of on-chain programs written in Rust, such as Solana programs, CosmWasm contracts and Arbitrum Stylus contracts. Reviewers read the code line by line against the runtime's execution model, test it, and report vulnerabilities by severity, then review your fixes.

Does Rust's memory safety make smart contracts safe?

No. Memory safety removes one class of bug, but most serious on-chain findings are logic errors: missing account checks, wrong authorisation, broken accounting. Rust also wraps integer overflow silently in release builds unless overflow checks are enabled, which reviewers check for.

How is a Solana audit different from a Solidity audit?

Solana programs are stateless and receive every account as an input, so the main risk is trusting an account the caller supplied. In a Solidity audit, reentrancy and storage issues lead, because Solidity contracts hold their own state. The bug classes, tooling and reviewer experience differ, so match the firm to the runtime.

Do I need an audit if I use Anchor?

Yes. Anchor generates many account checks, which removes common mistakes, but only for the constraints you declare. Missing constraints, business logic, arithmetic and cross-program calls still need review.

Which Solana audit firms are on Procur3?

Firms with published Solana audits are compared in the Best Solana smart contract audit firms 2026 guide. When you post a request, firms that audit Solana programs are matched to it.

Is it free to request Rust audit quotes?

Yes. Posting a request and comparing quotes is free. You agree the price and terms with the firm you choose.

Get Rust audit quotes from firms that know your runtime.

Post your program once and compare quotes side by side.