How Starknet smart contracts work
- Language
- Cairo
- Runtime
- The Cairo VM on a STARK validity rollup, with native account abstraction
Languages and tooling we review
- Cairo
- Scarb
- Starknet Foundry
Starknet vulnerability classes we check
Bug classes that come from how Starknet works, checked on every Starknet audit alongside the usual logic and access control review.
- felt252 arithmetic that wraps modulo a prime instead of reverting
- L1 handler functions that do not check the L1 sender address
- Account contracts with weak __validate__ and signature checks
- Storage collisions in components and in upgrades through replace_class
- Access control on upgrade and admin entry points
Starknet audit focus and capabilities
We tailor our review to the unique architecture and common pitfalls on Starknet.
Why teams choose Cecuro for Starknet
// Example finding severity: HIGH title: Missing access control on upgrade() impact: Arbitrary logic upgrade can brick the protocol recommendation: Restrict to time-locked admin + add emergency pause
