TON smart contracts
Contracts for tokens, payments, staking and game logic on TON, written with tests and a review step, and explained to you in plain language.
Smart contracts on TON are programs that hold state and move value according to fixed rules. We write them in Tact, a higher-level language that is easier to read and review, and in FunC where a project needs lower-level control or has to work with existing contracts.
TON contracts communicate by sending asynchronous messages, and each contract lives at its own address with its own storage. A single action can pass through several contracts, so design has to handle messages that arrive late, fail or bounce back. Fees and storage rent also work differently from EVM chains.
If your team knows Solidity, we explain where the habits carry over and where they do not, before any code is written.
We write the contract together with automated tests that cover normal use and failure cases, including bounced messages and wrong senders. We run them on the testnet before anything touches real funds, and we write deployment scripts so the steps can be repeated and checked.
For contracts that hold meaningful value, we recommend an independent audit by a specialist firm. We can prepare the code and documentation for it. See the related jetton token page and package ranges.
You receive the source code, tests, deployment scripts and a short document describing each contract, its messages and its admin powers. The contract is deployed from your wallet, and you hold the keys. The client owns the code and the accounts it pays for.
Deployed contracts are generally hard or impossible to change, and a bug can mean lost funds. Testing and a security review reduce risk but cannot remove it, and no one can promise that a contract is free of bugs. Regulation of tokens and payments differs by country. We build software, we do not give legal or financial advice, and licences and compliance are your responsibility.
Tell us if you need a bot, a Mini App, a game or a TON contract.
You get the plan, a typical timeline and a written price range.
You see working builds each week and launch with a tested release.
For most new projects we suggest Tact, because the code is easier to read and review. FunC is the better choice when you need tight control over gas and storage, or must interact with existing FunC contracts. We explain the tradeoff during scoping and pick one language per contract based on your needs, not on habit.
Only if upgrade logic is built in from the start, and that logic is itself a risk because it gives someone power to change the rules. We discuss the choice with you: fixed contracts are simpler to trust, upgradable ones are easier to fix. Whichever you choose, the admin powers should be written down and visible to your users.
We can review a contract and tell you what we find, but that is a code review, not a formal audit, and it does not certify anything. For a formal audit before launch, use a specialist security firm. We are glad to prepare documentation and tests for them so their time goes further.
A token contract with airdrop tooling sits inside our larger web3 package, typically $14,000 to $25,000 with delivery in about four weeks. Smaller contract work is priced after scoping. The number of contracts, the complexity of the rules and any audit preparation change the price. A written quote follows a scoping chat.
You do not need to read it, but you should understand what the contract can do, who can change it and what happens if something fails. We write that in plain language and walk through it with you before deployment. A founder who understands the admin powers makes better decisions after launch.
Ready to build on Telegram? Message us on Telegram or WhatsApp with what you want to build and your timeline. Chat on Telegram Chat on WhatsApp
