Professional TON Smart Contract Deployment & Development

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

1. Data collection — we study your business requirements and technical constraints.
2. Audit & analysis — we review existing code or draft architecture, including a full TON smart contract audit.
3. Design — we define contract interfaces, message flows, and storage layout.
4. Estimation — we provide a fixed price or budget range.
5. Development — we write contracts in Tact/FunC, with extensive inline comments.
6. Testing — we run unit tests on local TVM and deploy to testnet.
7. Deployment — we deploy to mainnet using Blueprint with secure key management.
8. Verification — we upload sources to verifier.ton.org and update explorers.

Timelines

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.

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.

Blockchain Infrastructure Deployment: Nodes, RPC, Indexing

Subgraph fell at 3:47 AM. By morning users saw outdated balances, transactions "hung" in the UI, support received 47 tickets in an hour. Cause: the handler in the subgraph failed on a transaction with a non-standard event log — and the entire index stopped. We have encountered such situations dozens of times. Our experience shows: blockchain infrastructure does not forgive gaps in observability. Guaranteeing uptime without multi-layered monitoring and fault-tolerant architecture is impossible. Over 8 years working with Ethereum, Polygon, and Solana, we have developed an approach that allows predictable deployment of infrastructure of any scale — from a single node to a multichain grid with dozens of subgraphs.

RPC Layer Architecture

Every dApp interaction with the blockchain goes through RPC — the JSON-RPC API provided by a node. Three options:

Managed providers — Alchemy, QuickNode, Infura, Ankr. Minimal operational costs, SLA, built-in monitoring. Limits: rate limits (Alchemy Free: 300 RU/sec), vendor lock, potential downtime during provider incidents. For most projects — the right choice at the start.

Self-owned nodes — full control, no rate limits, no third-party dependence. Cost: archive Ethereum node requires 2.5–3TB SSD, a strong server, and DevOps support. Sync from scratch on Ethereum via Geth/Nethermind — 3–7 days. Justified under high load or latency requirements.

Hybrid — self-owned node as primary, managed provider as fallback. Standard for protocols with high TVL. Proper load balancing can reduce costs by 20–30% compared to pure managed setup. Under high monthly request volume, hybrid saves significantly.

How to Set Up an RPC Layer Without a Single Point of Failure?

At least two providers, DNS round-robin with health check every 5 seconds, automatic fallback when latency >500 ms. In practice, this gives 99.99% availability during any provider failure. For protocols with high TVL, we recommend a custom HA-proxy (nginx or Envoy) in front of two managed providers.

Why Is a Hybrid RPC Scheme More Cost-Effective Than Pure Managed?

At high request volumes, managed providers can be very expensive; a hybrid using a self-owned node as primary and a managed fallback cuts costs significantly without losing SLA.

Ethereum Node Clients

Execution clients: Geth (most used), Nethermind (C#, fast sync), Besu (Java, enterprise), Erigon (fastest sync, efficient archive mode ~2TB instead of 3TB).

Consensus clients (post-Merge): Lighthouse (Rust), Prysm (Go), Teku (Java), Nimbus (Nim). Each node after The Merge requires a pair of execution + consensus clients.

For DevOps: eth-docker — Docker Compose configurations for all client combinations. Setting up monitoring via Grafana + Prometheus is mandatory; a standard dashboard is available in each client's repository.

The Graph: Event Indexing

The Graph Protocol — decentralized indexing. A subgraph describes which events from which contracts to index and how to transform them into a GraphQL schema.

Subgraph structure:

• subgraph.yaml — manifest: contract addresses, startBlock, events to handle
• schema.graphql — GraphQL schema of entities
• src/mapping.ts — AssemblyScript event handlers

dataSources:
  - kind: ethereum
    name: UniswapV3Pool
    network: mainnet
    source:
      address: "0x88e6A0c2dDD26FEEb64F039a2c41296FcB3f5640"
      abi: UniswapV3Pool
      startBlock: 12370624
    mapping:
      eventHandlers:
        - event: Swap(indexed address,indexed address,int256,int256,uint160,uint128,int24)
          handler: handleSwap

AssemblyScript handlers — not TypeScript. No nullable types, no closures, no many standard APIs. An error in the handler stops the subgraph indexing on that transaction. Important: add try-catch for operations that can fail (e.g., store.get() for an entity that may not exist).

How to Avoid Subgraph Indexing Stops?

Graph Node logs are monitored in real-time; on hasIndexingErrors = true an alert fires and an automatic node restart (via systemd or Kubernetes). Typical downtime on error — 150–300 seconds to recover. Additionally, for production we set up a watchdog that restarts Graph Node if subgraph lag exceeds 50 blocks.

Choosing Between Hosted Service and Decentralized Network

Graph Hosted Service (free, centralized) is deprecated in favor of Subgraph Studio + Graph Network. For production: deploy on Graph Network with GRT curation signal — the subgraph gets indexers proportional to curation.

Alternatives to The Graph: Ponder (TypeScript, self-hosted, easier to debug), Envio (ultra-fast indexer, supports EVM + non-EVM), Subsquid (TypeScript, own network), Moralis Streams (managed, webhook-based). Our experience shows: for high-load projects with unique logic, Ponder or Envio are more effective — they give full control over the process and do not require GRT tokenomics.

Webhooks and Real-Time Notifications

Alchemy Webhooks and QuickNode Streams allow receiving events in real-time via HTTP webhook or WebSocket. For monitoring addresses, new transactions, mints — this is faster than polling RPC.

Tenderly — platform for monitoring and alerts. You can set up an alert for a specific contract event, balance change, function call with certain parameters. Transaction simulation via Tenderly API is invaluable for debugging.

Monitoring and Observability

Minimum monitoring stack for a protocol:

On-chain: OpenZeppelin Defender Sentinel — watches contract events, triggers webhook or Autotask when conditions are met. Forta Network — community-maintained bots detect anomalies (large withdrawals, flash loans, governance attacks).

Infrastructure: Grafana + Prometheus for nodes, Datadog or Grafana Cloud for managed metrics. Alerts on: node is 10+ blocks behind, RPC latency >500ms, subgraph lag >100 blocks.

Uptime: Better Uptime or PagerDuty on RPC endpoint and subgraph health endpoint (The Graph provides _meta { hasIndexingErrors, block { number } }).

Why Is Monitoring Without Tenderly Insufficient?

Tenderly provides transaction simulation and detailed traces — critical for debugging subgraph and smart contract errors. Forta focuses on network anomalies, not your infrastructure. The combination of Tenderly plus a custom Grafana dashboard covers 90% of incident scenarios.

Multichain Infrastructure

A protocol on 5 chains = 5 separate RPC endpoints, 5 subgraphs, 5 monitoring configs. Manageable but requires deployment automation.

For subgraph multi-network deployment: graph deploy --network mainnet, graph deploy --network arbitrum-one etc. with a unified codebase and network-specific addresses in separate config files.

Chainlink CCIP and LayerZero for cross-chain messaging require monitoring of both chains and transactions on intermediate relayers. A reorg on the source chain after a confirmed mint on the target chain is a classic bridge problem. Solution: wait for finality (on Ethereum ~15 minutes after Merge for economic finality) before confirming on the target chain.

Infrastructure Setup Process

1. Audit current stack — determine chains, request volume, latency and availability requirements.
2. Architecture design — select providers, load balancing, redundancy.
3. Subgraph development — manifest → schema → handlers → testing on local Graph Node → deploy to testnet → mainnet.
4. Monitoring configuration — Tenderly alerts, Grafana dashboard, PagerDuty integration.
5. Documentation and runbook — what to do when: subgraph falls behind, RPC downtime, node desync.
6. Handover to operations — team training, access transfer, first month support.

What's Included

• Deployment of managed or self-hosted Ethereum, Polygon, BNB Chain nodes
• RPC layer setup with primary/fallback and load balancing
• Subgraph development and deployment for your protocol
• Monitoring connection (Tenderly, Grafana, alerts)
• Runbook and operations documentation
• Team training (up to 4 hours online)
• 30-day support after delivery

Timeline

All projects are managed in a GitHub/GitLab repository with CI/CD; configuration code stays with you. Order infrastructure deployment — we'll show how to cut costs by 20–30% without losing reliability. Get a consultation — we'll demonstrate how we deployed infrastructure for a protocol with large TVL on Ethereum and Arbitrum. Contact us.