How Sei smart contracts work
Sei runs EVM-compatible smart contracts, usually written in Solidity or Vyper, so the review covers both the EVM's known failure modes and the ways Sei differs from Ethereum mainnet.
Languages and tooling we review
- Solidity
- CosmWasm
- Rust
Sei vulnerability classes we check
Bug classes that come from how Sei works, checked on every Sei audit alongside the usual logic and access control review.
- Reentrancy through external calls and token callbacks
- Oracle and spot-price manipulation funded by flash loans
- Access control and initializer gaps in upgradeable proxies
- Signature replay and permit (EIP-2612) misuse
- Rounding and share-inflation errors in ERC-4626 style vaults
- Bridge and cross-chain message validation
Sei audit focus and capabilities
We tailor our review to the unique architecture and common pitfalls on Sei.
Why teams choose Cecuro for Sei
// 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