TON
A sharded network, Telegram distribution, and a complicated naming history.
The Open Network combines smart contracts and asynchronous messaging with unusually close access to Telegram's application ecosystem. Its technical design, original Telegram fundraising, present network and 2026 currency rename need to be understood separately.
The network, the currency and the names
TON is The Open Network: infrastructure for accounts, smart contracts and messages whose state is agreed by validators. Telegram is a messaging platform through which people may encounter those applications. A wallet is another component, responsible for presenting balances and authorizing transactions. Keeping those identities separate makes it easier to understand which organization or piece of software is responsible when a payment, application or login behaves unexpectedly.
Names require special care in this archive. Current TON documentation calls the native currency Gram, with ticker GRAM. Blockchain.com's July 2026 support notice describes Toncoin's rename and says existing balances, addresses and transaction history stay unchanged, without a user swap or migration. Historical articles and market-provider records may still say TON or Toncoin. Those labels describe continuity of the native asset; a separately issued token with a matching logo or ticker does not establish that identity.
TON Connect provides a communication interface between applications and compatible wallets. A connection request and a transfer request serve different purposes. An educational interface should explain the particular permission or transaction being requested, rather than treating connection to a familiar messaging app as a guarantee about everything an application might subsequently ask the wallet to do.
Telegram's original offering and the later network
The original Telegram project had a specific legal history. The SEC's June 2020 settlement announcement describes the 2019 enforcement action, the March 2020 preliminary injunction and a resolution requiring more than $1.2 billion to be returned to investors alongside an $18.5 million penalty. Telegram and TON Issuer settled without admitting or denying the complaint's allegations. Those proceedings concerned the original offering and distribution scheme; they are not a blanket classification of every later asset or application using the TON name.
A June 2021 open letter from the independent developer community describes maintaining and updating Telegram's original testnet2 after the company's withdrawal, and requests stewardship of the project's repository and domain. It is a contemporary account by participants, while the SEC record documents the enforcement outcome. Today's Telegram Mini App rules establish a later integration relationship. Read these artifacts together without collapsing the original issuer, subsequent developers, current network validators and today's app operators into one interchangeable entity.
A shared technical lineage does not make their contracts, responsibilities or business arrangements identical.
Shards and asynchronous execution
TON organizes work across workchains and shardchains. The masterchain carries network-level configuration, while the basechain hosts ordinary accounts and applications. The sharding design divides account ranges and permits changing how work is distributed as load changes. An individual account still has its own state and transactions. The architectural goal is to distribute processing rather than require every application's entire workload to fit through one permanently fixed execution partition.
A user-visible operation may involve several contracts exchanging messages. An explorer's trace follows the causal chain between those messages and transactions. Imagine a wallet initiating an exchange: seeing the wallet's first transaction is not, by itself, the same observation as seeing the recipient receive the desired output. Following the whole trace reveals where processing continued, failed or generated another message. That distinction matters to support teams and developers interpreting what a completed operation means.
The word infinite in the sharding vocabulary describes the design's expandable partitioning scheme. The documentation also explains finite block capacity and queues between shards. A network's transaction benchmark therefore needs its workload, hardware and completion criteria; a capacity slogan alone cannot establish that every complex application will have the same latency under all conditions.
Jettons, native transfers and the cost of execution
Jettons are fungible tokens implemented by contracts on TON. Their architecture includes a master contract and separate wallet contracts for holders. Payment integration must establish that an incoming notification comes from the expected wallet associated with the expected master. Looking only at a token's displayed name, a reported balance or a message saying transfer is insufficient: another contract can imitate those superficial details. This is why a native currency and a similarly named Jetton must remain distinguishable in a wallet or encyclopedia.
Fees have multiple components. Storage charges relate to keeping account data, computation charges pay for execution, and message-related charges cover forwarding and actions. Network configuration determines the parameters. For an application performing several steps, the practical question is whether the operation funds all required processing, rather than whether the first screen quotes a small average transaction fee. Reviewing the trace and fee breakdown can explain why a contract interaction costs more than a basic transfer or why a failure still consumed resources.
Telegram integration brings reach and platform dependence
Telegram's blockchain guidelines require qualifying Mini Apps to use TON for issuing or distributing blockchain assets and TON Connect for wallet interactions. The document distinguishes Mini Apps from ordinary bots without a Mini App component, and it provides specific exceptions and examples for bridging and multichain wallets. This is a concrete distribution policy, not merely an informal endorsement. Developers need to read the actual scope before assuming that every bot or every cross-chain interaction is governed identically.
Telegram Stars are also distinct from the native blockchain currency. Telegram's developer terms prescribe Stars for digital goods and services in the relevant platform flow. A diagram that labels every in-app payment as an on-chain TON transaction would therefore be misleading. Separately, Telegram reserves control over platform access and service changes. An application's smart contracts may remain accessible on a blockchain while its main discovery or user-interface channel changes.
Assessing the ecosystem means examining both blockchain execution and the platform through which users arrive.
The adoption story and how to investigate it
TON's official channel describes wallets, in-chat services and blockchain games as ways to introduce Telegram users to blockchain applications. Its ambition of bringing 30 percent of Telegram's users to TON by 2028 is a target in that ecosystem narrative, not an achieved adoption measurement. Familiar interfaces help explain why the story resonates: the first interaction can be social or playful before a newcomer learns blockchain terminology.
Our research approach asks what remains after the introductory incentive ends. Useful follow-up evidence would include returning users, repeat transactions with a stated purpose, support outcomes and independently reproducible activity measurements. Registrations, addresses, game participants and people are different units. Likewise, several messages in one trace can represent one user operation. Record the unit, time window and method alongside any growth chart so a change in counting conventions is not mistaken for growth in actual use.
This chapter documents a substantial distribution opportunity alongside its dependencies. It makes no inference from audience size to a guaranteed token price. A persuasive future update would connect application demand to observable network activity and explain how platform rules, user retention and operational costs affected that result.
How we got here.
- 2019-10-11
SEC files its Telegram complaint
The SEC challenges the original Gram offering and proposed distribution, according to its later settlement record.
- 2020-03-24
Preliminary injunction
The U.S. district court preliminarily bars delivery of the original Grams; the SEC settlement announcement describes this procedural step.
- 2020-06-26
Settlement announced
Telegram and TON Issuer agree to investor repayments and an $18.5 million civil penalty, without admitting or denying the complaint's allegations.
- 2025-01-21
Mini App asset policy takes effect for new issuance
Telegram's guidelines apply TON requirements to newly issued or distributed assets, with later transition deadlines for existing Mini Apps.
- 2026-07-15
Wallet provider documents the GRAM rename
Blockchain.com's updated notice explains continuity of existing balances and warns about imitation Jettons. This is the notice's date, not an asserted network activation date.
Beliefs, ambitions & unanswered questions.
These are attributed narratives, not endorsements. Open each evidence file to see the supporting record and the limits of what it establishes.
Future possibilityTelegram's audience becomes a blockchain audience
Open evidence file
An established messaging audience and games can become a durable base of blockchain users.
Where the story comes from
An official TON channel post connects wallets, in-chat services and games to a 2028 conversion target.
What the record supports
- Telegram's Mini App rules create a concrete distribution advantage for TON applications.
- The ecosystem publicly explains the acquisition strategy rather than leaving the adoption thesis implicit.
What it does not prove
- Access to an audience does not measure retained users or economic activity.
- Platform policy remains controlled by Telegram and can change.
What to watch
- Retention after rewards expire, with a published counting method.
- Repeat use across applications and clear separation of Stars purchases from on-chain transactions.
Not establishedA rename requires a new token swap
Open evidence file
Users must send their existing native balance elsewhere or exchange it for a newly received GRAM token to complete the rename.
Where the story comes from
Blockchain.com's rename notice specifically warns about imitation GRAM Jettons and upgrade or verification demands.
What the record supports
- The provider states that the rename leaves addresses and balances intact and requires no user swap.
- TON's token documentation explains why matching names do not establish the identity of a Jetton.
What it does not prove
- An exchange may update its display label on its own schedule.
- A separate token displaying the same name is not evidence that it is the native currency.
What to watch
- Native-transfer records versus Jetton records in a trusted explorer.
- Requests to approve transactions or send funds merely to rename a balance.
Not establishedInfinite sharding means no congestion
Open evidence file
Expandable shard architecture guarantees unlimited real-world throughput for every application.
Where the story comes from
A literal reading of the Infinite Sharding Paradigm label in TON's architecture discussion.
What the record supports
- The design supports partitioning work and describing account ranges across shards.
- The same documentation explicitly discusses finite blocks and delayed cross-shard message processing.
What it does not prove
- Architectural address space is not an observed throughput measurement.
- A multi-message operation has a different completion path from a simple transfer.
What to watch
- Reproducible benchmarks with transaction type, hardware and latency distribution.
- Explorer traces showing when the final application result actually arrives.
The source library.
Primary documents explain mechanics and decisions. Community records show what participants believed. Dates below indicate when these links were reviewed; external pages may change.
- TON documentation: network overview and native Gram ↗TON documentation · primary · Reviewed 2026-09-22
- Telegram settlement and investor repayments ↗U.S. Securities and Exchange Commission · legal · Published 2020-06-26 · Reviewed 2026-09-22
- Toncoin (TON) renamed to GRAM ↗Blockchain.com · primary · Published 2026-07-15 · Reviewed 2026-09-22
- Blockchain sharding and cross-shard congestion ↗TON documentation · primary · Reviewed 2026-09-22
- Transaction traces ↗TON documentation · primary · Reviewed 2026-09-22
- Transaction fee components ↗TON documentation · primary · Reviewed 2026-09-22
- Jetton payment processing and identity validation ↗TON documentation · primary · Reviewed 2026-09-22
- Blockchain guidelines for Mini Apps ↗Telegram · primary · Reviewed 2026-09-22
- Bot Platform developer terms ↗Telegram · legal · Reviewed 2026-09-22
- TON channel: Telegram adoption strategy and 2028 target ↗TON official channel · community · Reviewed 2026-09-22
- Open-source community's request to Telegram ↗TON developer community · primary · Published 2021-06-23 · Reviewed 2026-09-22
- TON Connect overview ↗TON documentation · primary · Reviewed 2026-09-22