How TON smart contracts work
- Language
- Tolk, FunC and Tact
- Runtime
- The TON Virtual Machine (TVM), where contracts are actors that only communicate through asynchronous messages
Languages and tooling we review
- Tolk
- FunC
- Tact
- Blueprint
TON vulnerability classes we check
Bug classes that come from how TON works, checked on every TON audit alongside the usual logic and access control review.
- State changed before a reply or bounce arrives in multi-message flows
- Unhandled bounced messages that leave balances inconsistent
- Gas and storage-fee exhaustion that freezes a contract mid-flow
- Jetton transfer notifications trusted without verifying the sender wallet
- Replay protection on external messages (seqno and expiry)
TON audit focus and capabilities
We tailor our review to the unique architecture and common pitfalls on TON.
Why teams choose Cecuro for TON
// 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