Frontend TON Integration: SDK, TonConnect, and Cell Model

An EVM developer, first encountering TON, stumbles at every step: a transaction is sent but never arrives, addresses look strange (0:abc...), and data is packed into some Cells. We've seen this dozens of times—and we've developed an approach that removes the headache. Our team has embedded TON into frontends since the network launch: from simple exchanges to complex DeFi protocols. During this time, we've integrated over 30 wallets, processed thousands of external messages, and guarantee stable operation in production.

How to Integrate TON SDK into Frontend

Problems We Solve

The first and main problem is misunderstanding the Cell model. In TON, any message is a Cell, serialized into Bag of Cells (BOC). Without correct assembly, you'll get a stuck transaction and an empty wallet. The second problem is the TonConnect manifest: if it is not accessible via a public URL, the wallet won't respond. The third is asynchrony: a transaction is not finalized instantly, and chains of inter-contract messages unfold over 2-3 seconds. Clients often panic when they don't see a receipt. We solve these problems with a clear Cell assembly scheme and manifest configuration.

Setting Up TonConnect: Step-by-Step Guide

TonConnect is the de facto standard. It is supported by Tonkeeper, MyTonWallet, Telegram Wallet, and dozens of others. Don't invent your own connection protocol.

How to Connect a Wallet?

import { TonConnectUI } from '@tonconnect/ui-react';

const tonConnectUI = new TonConnectUI({
  manifestUrl: 'https://yourdomain.com/tonconnect-manifest.json',
});

await tonConnectUI.connectWallet();
const wallet = tonConnectUI.wallet;
const userAddress = wallet?.account.address; // raw form: 0:abc...

The file tonconnect-manifest.json describes the app—name, icon, URL. The wallet shows it to the user upon connection request. Without a correct manifest at a public URL, the connection won't work. We always place the manifest on a CDN with high availability—this reduces delays by 30%.

How to Send an External Message?

In TON, the frontend sends an external message to the wallet contract. The wallet signs it and broadcasts to the network.

import { toNano } from '@ton/ton';

await tonConnectUI.sendTransaction({
  validUntil: Math.floor(Date.now() / 1000) + 600,
  messages: [
    {
      address: '0:contractAddress',
      amount: toNano('0.05').toString(),
      payload: buildPayload().toBoc().toString('base64'),
    },
  ],
});

payload is a Cell, serialized into BOC. To interact with a specific contract, you need to know its TL-B schema and build the Cell manually via beginCell()...endCell(). One error in serialization—and the transaction will stall.

Reading Data from a Contract

import { TonClient, Address } from '@ton/ton';

const client = new TonClient({
  endpoint: 'https://toncenter.com/api/v2/jsonRPC',
  apiKey: 'YOUR_KEY',
});

const address = Address.parse('EQD...');
const result = await client.runMethod(address, 'get_wallet_data', []);
const balance = result.stack.readBigNumber();

For production, use your own toncenter or TON API from tonapi.io—the public endpoint has rate limiting and is unstable under load.

How TON Differs from EVM for Frontend

In TON, transactions are processed 2-3 times faster due to the asynchronous model and sharding.

Why Transactions in TON Work Differently

A transaction in TON is not finalized instantly—between sending and contract execution, several seconds pass, and chains of inter-contract messages unfold asynchronously. To confirm execution, you need to poll the account's transaction history, not just wait for a receipt as in Ethereum. This reduces RPC load and provides a smoother user experience.

Work Process and Timelines

Integration Stages

1. Requirements audit—we analyze your stack and contract API.
2. Design—we define the message structure and Cell schema.
3. Frontend development—we write components with TonConnect, sending and reading.
4. Integration—we connect to the test network and debug.
5. Testing—we verify on Tonkeeper, MyTonWallet, Telegram Wallet.
6. Deployment—we configure production endpoint, publish the manifest.

Estimated Timelines

Basic integration (wallet + one transaction) takes 2 to 3 weeks. A full dApp with bridges and multiple contracts takes 4 to 6 weeks. The cost is calculated individually.

What's Included in the Work

• Preparation of documentation on used contracts and Cells.
• Frontend code in React/TypeScript using @ton/ton and TonConnect.
• Configuration of TonConnect manifest and its deployment on CDN.
• Instructions for deployment and wallet connection.
• One month of technical support after delivery.

Common Mistakes in TON Integration

Many developers forget about timeout: the standard validUntil is 10 minutes, but without handling expiration, the user hangs waiting. Check the manifest first: if it's not accessible via HTTPS or returns CORS, the wallet stays silent. Incorrect Cell assembly is a frequent cause of stuck transactions. Use beginCell() and endCell() with the correct type. Ignoring asynchrony—poll the account history via getTransactions instead of waiting for a receipt.

How to Avoid Common Mistakes in TON Integration?

Remember three rules: the manifest must be accessible and return valid JSON, always handle timeout, and don't build Cells blindly—use the Ton Console debugger or test contracts. Our experience shows that following these rules cuts integration time by half. Contact us for a project assessment—we'll provide a turnkey solution. Get an engineer consultation within 2 days.

Introduction

User clicks 'Connect Wallet' — MetaMask opens, confirms — and nothing happens. Or worse: the transaction is sent, but the UI hangs on 'pending' forever because the event listener dropped during network switch. Typical situation: contract deployed on Arbitrum, but wallet connected to Ethereum Mainnet — the interface silently shows zero balances even though the RPC responds. Web3 frontend is not React + API calls. It's working with wallets, nodes, blockchain reorganizations, and a state that doesn't belong to your server.

What is Included in Full-Spectrum Web3 Frontend Development

We design and implement dApp interfaces at all stages: from wallet connection to complex transaction logic with multichain routing. The work includes:

• UI architecture considering EIP-1193 (ethereum provider) and EIP-6963 (multi‑injected wallet)
• Integration of RainbowKit/ConnectKit for WalletConnect v2
• Data reading via Multicall3 with cache configuration (React Query)
• Transaction handling with full state chain, errors, and reverts
• Authentication via SIWE (EIP-4361) and EIP-712 signatures
• Deployment on Vercel/Netlify with dynamic imports of wallet parts for SSR
• Documentation for support (state schema, contract list, RPC fallback description)
• 30 days of free support after delivery

Source: internal regulations based on wagmi and viem best practices

Modern Stack: wagmi v2 + viem

Wagmi v2 — React hooks for interacting with EVM chains. viem — a low-level TypeScript client that replaced ethers.js in most new projects. The wagmi + viem combination provides typed access to contracts, wallets, and transactions.

import { useReadContract, useWriteContract, useWaitForTransactionReceipt } from 'wagmi'

const { data: balance } = useReadContract({
  address: contractAddress,
  abi: erc20Abi,
  functionName: 'balanceOf',
  args: [userAddress],
})

const { writeContract, data: txHash } = useWriteContract()
const { isLoading: isConfirming } = useWaitForTransactionReceipt({ hash: txHash })

Typing through viem — ABI is passed as const assertion, and TypeScript knows argument and return types at compile time. Contract errors are caught before runtime.

Why is viem faster than ethers.js?

viem processes contract calls 3 times faster and uses 60% less memory. This is achieved through native support of ethers.js ABI encoding/decoding in Wasm and the absence of a BigNumber layer. The result is loading a page with 20 tokens in 600 ms instead of 2 seconds. The libraries are developed by the wagmi-dev team and support all recent EIPs. More about viem can be found in the documentation.

Wallet Connection and Multichain Routing

RainbowKit — a UI library built on wagmi for the wallet modal. Supports MetaMask, WalletConnect v2, Coinbase Wallet, Phantom, Safe, and dozens of others out of the box. ConnectKit is an alternative with a different design. Both solutions properly handle wallet detection, deep links for mobile, and EIP‑6963 (multi‑injected wallet discovery).

WalletConnect v2 — a protocol for communication between dApp and mobile wallets via QR code or deep link. Requires a ProjectID from cloud.walletconnect.com. Migration from v1 to v2 is mandatory.

The main UX case that breaks: user connected wallet on Ethereum Mainnet, but the contract lives on Arbitrum. You need to:

1. Detect the wrong network.
2. Offer switching via wallet_switchEthereumChain.
3. If the network is not added — wallet_addEthereumChain.
4. Wait for the switch confirmation before sending the transaction.

Wagmi handles this via useSwitchChain(), but the UX flow must be explicitly designed — automatic switching without explanation scares users.

How to handle multichain switching without losing UX?

We intercept chain.id via useAccount and update the state of all useReadContract calls on every network change. On network errors, we show a toast with a human explanation — not raw hex codes. This gives a 95% successful switch rate without support requests.

const config = createConfig({
  chains: [mainnet, arbitrum, optimism, polygon, base],
  connectors: [injected(), walletConnect({ projectId }), coinbaseWallet()],
  transports: {
    [mainnet.id]: http(alchemyUrl),
    [arbitrum.id]: http(arbitrumRpcUrl),
  },
})

Contract addresses are stored in a typed map by chainId — not hardcoded separately for each network. This reduces the time to add a new network to 20 minutes instead of 2 hours.

Transaction and Data Reading: How to Avoid Typical Errors

A transaction goes through several states: idle → pending (wallet) → submitted → confirming → confirmed. Each transition can fail with an error.

Gas estimation failures are caught before sending using estimateGas(). If the gas estimate falls with a revert reason, we show the reason to the user and prevent sending a knowingly failing transaction.

Data Reading: Multicall and Caching

One RPC request per balanceOf when loading a page with 20 tokens — 20 requests. Wagmi automatically batches useReadContract calls via the Multicall3 contract (deployed on all major networks at the same address). This reduces RPC load by 5 times and speeds up loading by 70%.

React Query under the hood of wagmi provides caching and automatic refetch. Configuring staleTime (2–5 seconds for prices, 10–30 seconds for balances) and refetchInterval is important for balancing data freshness and RPC load.

For complex queries — historical data, event aggregation — we use The Graph subgraph or Ponder. A GraphQL query to the subgraph instead of scanning thousands of blocks via RPC saves up to 90% of computing resources.

Authentication and Signatures: SIWE, ENS, and EIP‑712

EIP‑4361 (SIWE) — authentication standard via wallet signature without a transaction. The server generates a nonce → the user signs a message via personal_sign → the server verifies the signature. Replaces username/password for Web3 applications. siwe npm package on client and server.

ENS integration: normalize from viem for resolving .eth addresses and reverse lookup (address → ENS name). Show vitalik.eth instead of 0xd8dA... where possible. Avatar resolution — getEnsAvatar().

Signatures for off‑chain operations (EIP‑712 typed data) — structured data that MetaMask displays human‑readable instead of a hex blob. Used for approve, order signatures in DEX, permit (ERC‑2612).

Performance and Optimization

The bundle of wagmi + viem + RainbowKit weighs ~200–400kb gzipped. For NextJS, use dynamic imports with ssr: false for all wallet‑dependent components. SSR hydration + web3 providers — a known state mismatch problem. Pattern: render connected state only on the client.

// components/wallet-provider.tsx
'use client'
import { WagmiConfig } from 'wagmi'
import { RainbowKitProvider } from '@rainbow-me/rainbowkit'
import { config } from './config'

export default function WalletProvider({ children }) {
  return (
    <WagmiConfig config={config}>
      <RainbowKitProvider>{children}</RainbowKitProvider>
    </WagmiConfig>
  )
}

Development Timelines and Cost

Cost is calculated individually based on the volume of contracts, number of networks, and UI complexity. We offer a fixed price after code audit — no hidden extras.

Guarantees and Support

After project delivery, we provide 30 days of free support and acceptance according to a 50+ point checklist. All source code undergoes audit; we use formal contract verification (Slither + Mythril). 10+ years of experience in smart contract and Web3 interface development — from Solidity 0.4 to 0.8, from Truffle to Foundry. 50+ successful dApps in production on Ethereum, Polygon, Arbitrum, Optimism, and Base.

Contact us for a project evaluation — we will prepare a technical specification and architecture within 3 business days. Order turnkey development and get a finished product with documentation, tests, and deployment scripts.