Rust smart contract auditing for production programs
Manual and static review for Solana, CosmWasm, and Near: CPI reentrancy, unsafe Rust, authority paths, and economic exploits. Scope assessment in 48 hours. Severity ratings and fix guidance your eng team can ship against.
Audit Framework
What a Rust smart contract audit covers
Findings map to how Rust programs fail in production, including CPI spoofing and PDA seed collisions that a Solidity checklist usually misses.
Reentrancy & Cross-Program Invocation
CPI ordering bugs, reentrancy across program boundaries, and privilege escalation via remaining accounts. The Rust/Solana counterparts to classic EVM reentrancy classes.
Integer & Arithmetic Hazards
Overflow/underflow in checked and wrapping math, precision loss in fixed-point accounting, and fee-rounding that leaks value over volume.
Access Control & Authority Paths
Signer checks, PDA seed collisions, upgrade authority risk, and admin key compromise scenarios, mapped to concrete exploit paths.
Unsafe Rust & Memory Safety
Audit of `unsafe` blocks, FFI boundaries, and custom allocators. We treat every `unsafe` as an explicit trust boundary, not a style preference.
Economic & MEV Exposure
Oracle manipulation, sandwichable settlement paths, liquidations race conditions, and batch-payout edge cases under adversarial mempools.
Formal Invariants & Test Gaps
Property tests, fuzz targets, and invariant documentation you can hand to your next auditor or insurance underwriter.
Engagement
How the audit runs
Scope Assessment
Repo access, threat model interview, and a written scope memo (in-scope programs, out-of-scope, timeline, severity rubric) within 48 hours.
Static + Manual Review
Toolchain scans (Clippy, cargo-audit, custom detectors) followed by line-by-line manual review focused on state transitions and authority paths.
Exploit Prototyping
High/Critical findings get PoC tests where feasible, so your engineering team can see the failure path.
Report & Remediation Support
Severity-ranked findings, fix guidance, and one free re-review of remediated issues. Optional public attestation letter on request.
Deliverables
What you walk away with
FAQ
Common questions about Rust audits
QDo you audit Rust smart contracts for Solana specifically?
Yes. Most of our Rust audit volume is Solana (Anchor and native programs), with CosmWasm and Near engagements as secondary tracks. We also review cross-program and oracle integration code that lives outside the on-chain program but can break the security model.
QHow is this different from a Solidity audit firm that 'also does Rust'?
Rust and Solana failures look different from EVM ones: CPI spoofing, account discrimination bugs, and PDA seed collisions. Our reviews are staffed by engineers who ship Rust in production.
QWhat about queries like 'reentrancy attack contract address'?
If you are investigating a suspected exploit, we can run an incident-style review: reconstruct the call path, identify the vulnerable instruction, and recommend freeze or migration options. For active incidents, contact us immediately. Speed matters more than a polished report.
QHow long does a typical Rust smart contract audit take?
Small programs (1–3k LOC, single program) usually run 1–2 weeks. Multi-program DeFi or payments systems typically take 3–5 weeks depending on maturity of tests and prior reviews. Scope assessment always comes first so you get a fixed timeline before kickoff.
QCan you audit alongside our crypto payments or rails build?
Yes. Many clients engage us for both rails architecture and audit coverage. See our Web3 hub and the enterprise fiat-crypto rails guide. Combining build and independent review usually costs less than hiring two uncoordinated vendors after the fact.
Ready for a scope assessment?
Send the repo (or a private invite) and the threat model you care about. You get a written scope memo before any audit invoice.