TON Specification Dated February 8 Maps Telegram’s Blockchain Amid SEC Fight

Nikolai Durov’s 121-page specification for the Telegram Open Network carries the date February 8, 2020, adding a detailed description of TON’s proposed blockchain while Telegram remained locked in a US securities dispute over its planned Gram token distribution. The document defined block formats, state transitions, message handling, smart-contract execution and cryptographic signatures, but explicitly described the system as a preliminary test version rather than a finished production network.

That distinction made the specification consequential. Telegram had financed TON through agreements for future Grams, and the US Securities and Exchange Commission was seeking to stop their delivery. The February 8 document supplied a substantially more concrete technical record of the network behind those agreements, yet it did not resolve whether TON was ready to launch or whether the contemplated token distribution complied with securities law.

What the specification established

The document described a multi-chain architecture organized around a masterchain and shardchains. Masterchain blocks would record the latest blocks from active shardchains, making their inclusion canonical, while configurable parameters and special masterchain contracts would govern matters such as validator selection and protocol settings. TON represented persistent data through collections of cells: structures containing as many as 1,023 data bits and four references to other cells.

It also formalized consistency conditions intended to preserve balances and state across blocks. Global conditions included a guarantee that internally generated messages should reach their destination exactly once. Separate sections addressed account states, transactions, inbound and outbound message queues, smart contracts and serialization. These details offered developers a specification against which implementations and test software could be compared.

The document was not a complete operational proof. It omitted the Byzantine Fault Tolerant protocol validators would use to select blocks, saying that subject belonged in a separate TON Network document. It also omitted network protocols for propagating blocks and candidates, as well as complete source code for masterchain contracts responsible for validator elections, configuration changes and punishment of misbehavior. The paper warned that minor details could change before launch.

A contemporaneous February 5 report about a separate TON consensus paper said TON Labs developers had already been exercising the test network. That report attributed claims of testing with as many as 300 nodes and block production every four to five seconds to the project’s papers and participants. Those were project-reported test results, not an independent benchmark, and they should not be treated as demonstrated production capacity.

The regulatory collision

The SEC’s October 11, 2019 complaint alleged that Telegram raised approximately $1.7 billion by selling rights to about 2.9 billion Grams to 171 initial purchasers. According to the complaint, 39 US purchasers supplied $424.5 million for more than one billion Grams. The agency alleged that Telegram was financing TON’s development through the offering and that purchasers expected profits from Telegram’s work building the network and integrating it with Messenger.

Those were the regulator’s allegations, not findings as of February 8, 2020. The technical specification could document how TON was intended to function, but technical detail alone could not decide whether the purchase agreements, future token delivery and anticipated resales formed an unregistered securities offering. Nor could a white paper establish that the described code was secure, decentralized or ready for unrestricted deployment.

What remained uncertain

The surviving specification verifies its February 8 date and technical contents, but it does not preserve an independently authenticated first-upload time. The event-day record therefore supports saying the specification was dated February 8—not claiming an exact publication hour or that every described component was running that day.

Later context must remain separate: a federal judge granted the SEC a preliminary injunction on March 24, 2020, and a settlement received court approval in June 2020. Neither outcome was knowable on February 8. On the dated record, TON remained an ambitious test-stage protocol whose engineering disclosures were advancing while its proposed token launch faced unresolved legal constraints.