How Cardano smart contracts work
- Language
- Plutus (Haskell), Aiken and other languages that compile to Untyped Plutus Core
- Runtime
- The extended UTxO (eUTxO) model, where validator scripts approve or reject transactions instead of holding mutable state
Languages and tooling we review
- Aiken
- Plutus
- Haskell
Cardano vulnerability classes we check
Bug classes that come from how Cardano works, checked on every Cardano audit alongside the usual logic and access control review.
- Double satisfaction: one payment satisfying several validators in the same transaction
- Unbounded values or datums (token dust) that make outputs unspendable
- Missing checks on datum, redeemer and output addresses
- Minting policies that allow unauthorized minting
- Staking credentials on script addresses left unchecked
- UTxO contention on shared protocol state
Cardano audit focus and capabilities
We tailor our review to the unique architecture and common pitfalls on Cardano.
Why teams choose Cecuro for Cardano
// 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