| name | ton |
| description | TON Blockchain — addresses, messages, TVM, cells, Blueprint, contracts, payments, API. |
| metadata | {"author":"Hairy","version":"2026.2.9","source":"Generated from https://github.com/ton-org/docs, scripts located at https://github.com/antfu/skills"} |
Skill is based on TON documentation (ton-org/docs), generated at 2026-02-09.
TON (The Open Network) is a decentralized blockchain with an Actor model (all entities are smart contracts), stack-based TVM, and cell-based serialization. This skill covers foundations, contract development with Blueprint, payments, and API access.
Core References
| Topic | Description | Reference |
|---|
| Addresses | Internal/external addresses, workchains, account ID | core-addresses |
| Messages | Message types, StateInit, deploy, transactions | core-messages |
| Cells & serialization | Cells, BOC, builders and slices | core-cells-serialization |
| TVM | Stack, data types, gas, instructions, get methods | core-tvm |
| TVM exit codes | Compute/action phase codes, testing | core-tvm-exit-codes |
| Fees & status | Storage/compute/forward fees, account status (nonexist, uninit, active, frozen) | core-fees-status |
| TVM registers | c0–c7, c4/c5 durable, c7 environment | core-tvm-registers |
Features
Development
| Topic | Description | Reference |
|---|
| Blueprint | create-ton, Sandbox, project structure | features-blueprint |
| Contract development | First contract, storage, messages, get methods, Tolk | features-contract-development |
| Tolk language | Types, message handling, lazy loading, IDE | features-tolk |
| Contract upgrades | setCodePostponed, setData, delayed and hot upgrades | features-upgrades |
| Standard wallets | V4, V5, Highload, comparison, use cases | features-wallets |
| Standard tokens | Jettons, NFTs, transfer, mint, burn, discovery | features-tokens |
| Signing | Ed25519, wallet/gasless/server patterns, TypeScript | features-signing |
Payments & API
Best Practices
| Topic | Description | Reference |
|---|
| Security | Integers, replay, accept_message, gas, random, front-running | best-practices-security |
