Your team just built a new DeFi protocol. You're coming from EVM, and now you face TON's async architecture—no synchronous calls, only messages. Storage rent will burn your contract if not funded. And your first deployment attempt fails because you forgot to compute the address from StateInit. This is where we step in.
We help projects deploy smart contracts on the TON blockchain: from development in FunC and Tact to testnet and mainnet deployment with full verification. Our team has 5+ years of blockchain development experience and 20+ successful TON projects. We'll assess your project in one day.
Problems We Solve
- Storage rent mismanagement. Many developers underestimate the cost. A contract with 500 bytes of data pays
0.0075 TON per year ($0.015). We calculate the exact reserve needed and implement auto-top-up logic. - Gas optimization. TON's TVM has different cost models than EVM. Loops and persistent data access can spike gas. We optimize get-methods and minimize internal messages, achieving up to 76% gas reduction (e.g., a multisig wallet from 0.05 TON to 0.012 TON per execution).
- Async messaging complexity. Synchronous logic requires splitting into request-response pairs. We design message flows that avoid deadlocks and ensure atomicity.
How We Do It
Our stack: Tact for typical contracts (Jetton, NFT, staking), FunC for gas-critical components. We use Blueprint for build and deployment, @ton/sandbox for local TVM emulation, and verifier.ton.org for source verification.
Case study: A multi-signature wallet contract was consuming 0.05 TON per execution due to inefficient get_wallet_address calls. By caching computed addresses in persistent storage and inlining the getter, we reduced gas to 0.012 TON—a 76% improvement. The contract now runs for months without top-up.
Our Process
- Data collection — we study your business requirements and technical constraints.
- Audit & analysis — we review existing code or draft architecture, including a full TON smart contract audit.
- Design — we define contract interfaces, message flows, and storage layout.
- Estimation — we provide a fixed price or budget range.
- Development — we write contracts in Tact/FunC, with extensive inline comments.
- Testing — we run unit tests on local TVM and deploy to testnet.
- Deployment — we deploy to mainnet using Blueprint with secure key management.
- Verification — we upload sources to verifier.ton.org and update explorers.
Timelines
| Contract Type | Development Time |
|---|---|
| Simple (counter, storage) | 1–2 days |
| Medium (Jetton, NFT) | 3–5 days |
| Complex (AMM, staking) | 1–2 weeks |
Deployment of a ready contract (testnet + mainnet + verification) takes from 2–4 hours. Cost is calculated individually after analysis. Contact us to get a quote.
What's Included
- Smart contract development (FunC/Tact) based on your requirements
- Unit tests in TypeScript with TVM emulator
- Testnet deployment and debugging
- Mainnet deployment with verification on verifier.ton.org
- Documentation and interaction guide
- 7-day post-deployment support
Compilation and Tests
npx blueprint build npx blueprint test Tests run locally with @ton/sandbox—no network needed. Example:
import { Blockchain, SandboxContract, TreasuryContract } from '@ton/sandbox'; import { Counter } from '../wrappers/Counter'; describe('Counter', () => { let blockchain: Blockchain; let deployer: SandboxContract<TreasuryContract>; let counter: SandboxContract<Counter>; beforeEach(async () => { blockchain = await Blockchain.create(); deployer = await blockchain.treasury('deployer'); counter = blockchain.openContract(await Counter.fromInit()); await counter.send( deployer.getSender(), { value: toNano('0.05') }, { $$type: 'Deploy', queryId: 0n } ); }); it('should increment', async () => { await counter.send(deployer.getSender(), { value: toNano('0.01') }, 'increment'); expect(await counter.getValue()).toBe(1n); }); }); Deployment to Testnet and Mainnet
import { toNano } from '@ton/core'; import { Counter } from '../wrappers/Counter'; import { NetworkProvider } from '@ton/blueprint'; export async function run(provider: NetworkProvider) { const counter = provider.open(await Counter.fromInit()); await counter.send( provider.sender(), { value: toNano('0.05') }, { $$type: 'Deploy', queryId: 0n } ); await provider.waitForDeploy(counter.address); console.log('Deployed at:', counter.address.toString()); } Run npx blueprint run --testnet or --mainnet. Blueprint will ask for seed phrase or Tonkeeper connection via QR.
Jetton and NFT Implementation
Standard tokens on TON follow TEP-74 (Jetton) and TEP-62 (NFT) TEP standards on GitHub. Architecture differs from ERC-20: each holder gets a separate JettonWallet contract. The main JettonMaster only mints and stores global data. Wallet address is computed via getWalletAddress(ownerAddress). Blueprint provides ready wrappers from TON Foundation—we don't write from scratch.
Verification and Audit
After deployment, we verify the contract on verifier.ton.org. We upload sources and proof-of-compilation, and the service confirms bytecode matches. Once verified, explorers like tonviewer.com show the code and allow calling getter functions. We also perform security audits including a full TON smart contract audit using static analysis tools to identify vulnerabilities.
Common Mistakes to Avoid
- Forgetting to send extra TON for storage rent. Allocate 0.1–0.5 TON on deploy.
- Using sequential messages when parallel is possible (gas waste).
- Not handling the bounce flag—bounced messages can break state.
- Hardcoding addresses instead of computing from StateInit.
Why Tact over FunC?
Tact reduces development time by 60% compared to FunC, making it ideal for most projects. However, FunC can be 2–3x more gas efficient in critical loops, so we use it for gas-optimized components.
Our team has 5+ years on the market and 20+ TON projects delivered, ensuring reliable and secure deployments.