How Arbitrum smart contracts work
- Language
- Solidity and Vyper, plus Rust, C and C++ through Stylus
- Runtime
- Arbitrum Nitro: EVM-equivalent execution alongside Stylus WebAssembly contracts, settled on Ethereum as an optimistic rollup
Languages and tooling we review
- Solidity
- Foundry
- Hardhat
Arbitrum vulnerability classes we check
Bug classes that come from how Arbitrum works, checked on every Arbitrum audit alongside the usual logic and access control review.
- Retryable tickets and L1-to-L2 address aliasing in cross-chain calls
- block.number returning an L1 block estimate, not the L2 block
- Sequencer downtime assumptions in oracles and liquidations
- Withdrawal delays and challenge-period assumptions in bridges
- Cross-VM calls between Stylus (WebAssembly) and Solidity contracts
Arbitrum audit focus and capabilities
We tailor our review to the unique architecture and common pitfalls on Arbitrum.
Why teams choose Cecuro for Arbitrum
// 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