Starknet Smart Contract Audit
Security review for Starknet projects, including Cairo contracts, DeFi protocols, wallet accounts, bridges, and chain-specific attack paths.
Starknet audit focus
A Starknet smart contract audit should review code behavior and the execution model that surrounds it. CTDSEC checks how the protocol manages assets, state transitions, authorities, external calls, upgrades, and network-specific assumptions.
The review starts with the frozen commit and then follows the paths that can affect user funds, protocol solvency, governance execution, bridge safety, and emergency controls.
| Runtime | Cairo VM |
|---|---|
| Languages | Cairo |
| Frameworks | Scarb, Starknet Foundry, OpenZeppelin Cairo |
| Primary intent | starknet smart contract audit |
Network-Specific Security Considerations
Important Starknet review points that generic checklists often miss.
- felt arithmetic and type conversion
- account abstraction and signature validation
- L1-L2 messaging assumptions
- storage layout, class upgrades, and component composition
Typical Audit Targets
Common Starknet systems that need manual security review.
- Cairo contracts
- DeFi protocols
- wallet accounts
- bridges
- governance systems
Related Starknet Audit Services
These pages help search engines and users understand the surrounding audit topic cluster.
Smart Contract Audit FAQ
Short answers for teams preparing an audit scope.
What makes a Starknet audit different?
Starknet uses Cairo VM, so the audit needs to account for felt arithmetic and type conversion and account abstraction and signature validation.
Which Starknet contracts can CTDSEC review?
CTDSEC can review Cairo contracts, DeFi protocols, wallet accounts, bridges, governance systems when the codebase, documentation, tests, and deployment assumptions are available.
Does CTDSEC only audit Starknet?
No. CTDSEC audits smart contracts across many ecosystems and keeps chain-specific pages connected to the broader smart contract audit process.
Request a Starknet smart contract audit
Send the repository, target network, language, documentation, and timeline so CTDSEC can scope the review accurately.