ContentsBrowse sections
This page records a withdrawal. Its former argument treated TON as a demonstrated instance of regulatory form substitution after the 2020 Telegram proceeding. The assembled legal, institutional, code, chain, and market record does not sustain that conclusion. Several observations remain valuable, yet the bridges between them remain unproved.
The decisive correction comes from the legal record itself. The March 2020 opinion did not confine Howey to an isolated token. It considered Telegram's agreements, expectations, undertakings, and planned distribution as a complete contract, transaction, or scheme. Any future account must begin there.
Basis of analysis
This note rests on a legal, institutional, code, chain, and market record. The March 24, 2020 opinion and the June 26, 2020 consent judgment supply the judicial layer. Zefix records the registration of The Open Network Stiftung under UID CHE-418.000.792. Telegram's Bot Platform Developer Terms and Blockchain Guidelines state the platform obligations, whose stated scope is Mini Apps and their bots. A TON Foundation-authored January 2025 release gives the Foundation's public account of the arrangement rather than a measurement of exposure, adoption, token demand, or institutional control. The canonical TON repository at the audited July 15, 2026 commit yields copyright provenance and the Elector and Config sources, and TON documentation describes a temporary emergency key assigned in 2021 and retired at block 34312810. An April 2026 account snapshot and a defined Binance window around Pavel Durov's August 2024 detention hold the chain and market observations. Each of those layers stops where its source stops. The audit did not prove the hash of deployed contracts, reconstruct historical key custody, or establish when any capability was exercised. Public labels and balances do not identify beneficial owners, and one venue and one event window establish an association without estimating causality or proving institutional continuity. Repository licences permit redistribution and modification, so the retained copyright lines establish provenance and attribution rather than continuing ownership or control. TON's own account of the canonical chain is a party history needing independent corroboration, and the captured 2018 Form D request failed at the SEC access layer.
An artefact can persist while an institution changes. A copyright notice can survive a transfer of agency, a governance function can exist without evidence of its custodian or use, and a platform rule can channel developers without establishing a securities-law relationship. The former draft collapsed those distinctions; this note restores them.
Decision
The original public thesis is withdrawn. The temporal sequence is insufficient to establish substitution, evasion, common control, economic continuity, or a recreated investment contract. Publishing that thesis would give conjectural bridges the cadence of findings.
This note’s purpose is methodological: preserve the corrections, identify the surviving record, and specify what a reconstructed inquiry would need before it could support a new finding.
Legal Correction
On March 24, 2020, the Southern District of New York granted a preliminary injunction after concluding that the SEC had shown a substantial likelihood of success on its Section 5 claim. The opinion framed the alleged security as the full Gram purchase and distribution scheme. It expressly rejected an analysis that severed the Gram from surrounding agreements and undertakings. That ruling, preliminary and directed to Telegram’s 2018 sales and planned distribution, did not adjudicate the later Toncoin network, Swiss foundation, or 2025 platform relationship.
The June 2020 final judgment was a consent judgment. Telegram entered it without admitting or denying the complaint’s allegations, apart from jurisdiction. The judgment imposed a Section 5 injunction, disgorgement of $1.224 billion subject to specified repayment and loan credits, an $18.5 million civil penalty, and a three-year notice obligation for participation in digital-asset issuances.
One sentence in the former draft also misstated Howey. The first prong asks whether there was an investment of money. A change from a corporate issuer to a Swiss foundation does not, by itself, dissolve that inquiry. Entity form enters the analysis as a fact rather than as the doctrinal answer.
What the Record Establishes
The institutional chronology can be stated with precision.
-
The Open Network Stiftung is an existing Swiss foundation registered in Zug under UID
CHE-418.000.792. Zefix records an instrument date of April 11, 2023 and first publication in the Swiss Official Gazette of Commerce on May 8, 2023. -
Telegram’s Bot Platform Developer Terms require Mini Apps that implement cryptocurrency functionality to use TON. The associated blockchain guidelines require TON Connect for covered wallet interfaces and describe transition dates and bridging exceptions. Their stated scope is Mini Apps and their bots; regular bots without a Mini App component are exempt.
-
A TON Foundation-authored January 2025 release described TON as the exclusive blockchain infrastructure for Telegram’s Mini App platform. That release establishes the Foundation’s public account of the arrangement. It does not independently measure exposure, adoption, token demand, or institutional control.
-
The canonical TON repository descends from Telegram-era source. At the audited July 15, 2026 commit, 950 tracked non-third-party files retained the exact Telegram Systems LLP copyright line. The repository’s licences permit redistribution and modification, so the notices establish provenance and attribution rather than continuing ownership or control.
-
The current Elector source accepts validator applications, checks signatures and stake conditions, applies configured validator limits, and selects by effective stake. The Config source contains validator voting paths and a master-key authorization path. These are source-level capabilities. The audit did not prove the hash of deployed contracts, reconstruct historical key custody, or establish when any capability was exercised.
-
TON documentation describes a temporary emergency key assigned to the TON Foundation in 2021 and retired at block 34312810 on November 22, 2023. The statement is material to a capability history. It leaves custody, instruction, use, and organizational control as separate questions.
The chain and market observations are narrower still. An April 2026 account snapshot shows high raw-address concentration, including protocol and lockup accounts. Public labels and balances do not identify beneficial owners. A defined Binance window around Pavel Durov’s August 2024 detention shows a sharp TON price decline relative to BTC and ETH. One venue and one event window establish an association; they do not estimate causality or prove institutional continuity.
The former Hamster Kombat section compared more than 300 million cumulative joiners with a later monthly-active-user estimate. Those units cannot support a retention rate. The token’s decline also varies materially with the selected price baseline. Claims about attention decay, user exodus, or comparative retention require cohort data, a common metric, and a specified counterfactual.
What the Record Leaves Open
The present record does not identify a common decision-maker across Telegram, the TON Foundation, validators, developers, and investors. It does not show that the Swiss foundation was selected to alter a Howey outcome, it does not establish that source-code ancestry carried organizational agency forward, and it does not support an inference of intent from chronology. That same record does not convert a platform rule into proof of token demand or investment reliance, does not establish beneficial ownership from account labels, and does not establish a permissioned validator allowlist.
Canonical-chain history also requires care. TON Labs launched Free TON, a separate network. TON’s own historical account attributes continuation of Telegram’s testnet2 code and network to NewTON and other open-source participants, followed by a community decision to promote the network to mainnet. That account is a party history and needs independent corroboration. It nevertheless defeats the former draft’s categorical attribution of the canonical launch to TON Labs.
Investor-name recurrence offers another weak bridge. A firm name appearing in separate fundraising narratives would not establish the same fund, beneficial owners, decision rights, coordination, or control. The captured 2018 Form D request failed at the SEC access layer, and the available filed record does not supply the investor-level bridge the thesis requires.
Reconstruction Candidate
A narrower paper could ask: From scheme to stack, what counts as continuity in the Telegram and TON record?
That inquiry would compare evidence classes rather than announce a finding of recoding. Judicial records can establish what transaction a court evaluated, registry records can establish legal identity and formal officeholders, and platform terms can establish developer obligations. Repositories can establish ancestry and source capability, while deployed bytecode and chain replay can establish live capability and exercise. Custody and decision-right evidence can connect capability to an institution, and beneficial-ownership work can connect balances to actors. Event studies can estimate market response within declared assumptions.
The contribution would lie in the bridge rules. Continuity of code is one proposition, and continuity of agency is another. Platform dependence is one proposition, and reliance for securities-law purposes is another. Economic association is one proposition, and causal mechanism is another. A rigorous paper would make each transition visible and would leave unsupported transitions unmade.
Gates for a Renewed Thesis
A renewed thesis requires all of the following:
-
A securities-law review that starts from the opinion’s scheme-wide analysis and addresses later facts without predicting liability.
-
An independently corroborated chronology distinguishing Telegram Open Network, testnet2, NewTON, Free TON, TON Foundation, and the later Telegram platform arrangement.
-
A deployed-code map that matches source to live contracts at defined blocks and reconstructs upgrades.
-
Evidence of key custody, exercised authority, and decision rights before any institutional-control claim.
-
Beneficial-ownership analysis before any supply-control claim.
-
Validator-set and participation data before any permissioning or decentralization claim.
-
A preregistered market-event design with comparison assets, confounds, venue coverage, and uncertainty.
-
Cohort-consistent user measurements before any retention or attention claim.
-
A literature review that distinguishes the proposed evidence protocol from Pistor’s legal coding, platform envelopment, regulatory arbitrage, and ordinary process tracing.
-
Independent legal, methods, code, and adversarial review, followed by route and visibility tests.
Until those gates close, this work remains a reconstruction record.
Scope of Inference
This note decides the status of a manuscript, not the legal status of TON, Telegram, the Foundation, any token, or any person. It does not allege evasion, liability, coordination, or concealed control. It records where the available materials support a bounded proposition and where an additional evidentiary bridge is required.
The population in view is the Telegram and TON record as the July 15, 2026 audit assembled it, and every observation reported here is bounded to that assembly. Dated anchors run from Telegram’s 2018 sales and planned distribution, through the 2020 Southern District proceeding and its June consent judgment, the April 11, 2023 instrument date and May 8, 2023 gazette publication of The Open Network Stiftung, the 2021 assignment and November 22, 2023 retirement that TON documentation gives for the emergency key, an August 2024 detention window, and a January 2025 Foundation release, to an April 2026 account snapshot and the audited repository commit. No observation later than that audit is reported, and no claim here depends on one.
Each layer holds what its source can carry and no more. Repository files show what source can do, so the Elector and Config observations stop at source-level capability and reach neither deployed bytecode, nor key custody, nor the time of any exercise. Registry records fix legal identity and formal officeholders without reaching control. Platform terms bind Mini Apps and their bots, and regular bots without a Mini App component fall outside them. Public labels and balances describe accounts without identifying beneficial owners. One venue and one event window support an association without an estimate of causality. The Hamster Kombat comparison of cumulative joiners with a later monthly-active-user estimate supports no retention rate on those units.
The complete claim disposition, source captures, repository pins, hashes, code anchors, calculations, and replay checks are preserved in the July 15, 2026 audit dossier.
Falsification
The affirmative claim here is evidentiary: the assembled record carries continuity of artefacts across the Telegram and TON sequence without carrying continuity of institutions, and the March 2020 opinion evaluated the full Gram purchase and distribution scheme rather than an isolated token. Five observations would defeat that position. Two reach that claim itself; three others defeat a particular finding this note reports and leave the withdrawal standing.
-
A passage in the March 24, 2020 opinion treating the Gram apart from the surrounding agreements, expectations, undertakings, and planned distribution would defeat the reading in Legal Correction, and with it the correction on which the withdrawal rests. That opinion is the CourtListener Opinion and Order cited below, so the condition resolves against a text already pinned here.
-
Evidence matching the current Elector and Config sources to deployed contracts at named blocks, together with a custody record for the master-key authorization path and a trace of when that path was used, would carry source-level capability through to exercised authority and defeat the restriction stated in What the Record Establishes. That condition reaches the affirmative claim itself, because authority traced to a custodian and to an occasion of use would carry continuity of institutions beyond continuity of artefacts. The assembled record does not contain that evidence. The audit did not prove the hash of deployed contracts, reconstruct historical key custody, or establish when any capability was exercised, and gates 3 and 4 name the work that would produce it.
-
A recount over the audited repository tree returning a figure materially different from the 950 tracked non-third-party files reported to retain the exact Telegram Systems LLP copyright line would defeat the provenance observation in What the Record Establishes. The reviewed revision is pinned in the code record below, so the count resolves against a fixed tree.
-
Independently corroborated records attributing continuation of Telegram’s testnet2 code and network to TON Labs rather than to NewTON and the other open-source participants would restore the former draft’s attribution of the canonical launch and defeat the correction in What the Record Leaves Open. This note carries TON’s own account, which it treats as a party history. Corroborating records are not in the assembled set.
-
A recomputation over the same Binance venue and the same defined window around Pavel Durov’s August 2024 detention returning no sharp TON price decline relative to BTC and ETH would defeat the market observation in What the Record Establishes. The venue is named here; the window and the calculation are fixed in the July 15, 2026 dossier.
Two of the five resolve against material this note already pins: a court document and a repository commit. A third resolves against the market window the July 15, 2026 dossier fixes. The remaining two turn on material the assembled record does not hold, and gates 2, 3, and 4 specify the work that would have to precede either check: a deployed-code map at defined blocks, custody and exercise evidence, and an independently corroborated chronology. No condition here asks for a forecast, which keeps the refutation test separate from the reconstruction programme.
References
U.S. District Court for the Southern District of New York. 2020. SEC v. Telegram Group Inc., Opinion and Order, March 24, 2020. CourtListener RECAP document 227.
U.S. District Court for the Southern District of New York. 2020. SEC v. Telegram Group Inc., Final Judgment as to Defendants, June 26, 2020. CourtListener RECAP document 242.
Telegram. n.d. Bot Platform Developer Terms of Service, section 7. Telegram.
Telegram. n.d. Blockchain Guidelines. Telegram.
Swiss Federal Office of Justice. n.d. The Open Network Stiftung, UID CHE-418.000.792. Zefix.
TON Core. n.d. The Open Network source repository, audited at commit bbc3bc6d52abbe3a7f852b22050708166fdaafbc. GitHub.
TON Docs. n.d. System smart contracts. TON Docs.
Code Records
TON Core. 2026. Audited repository tree; ton-blockchain/ton@bbc3bc6; tracked non-third-party files at that revision; reviewed commit bbc3bc6d52abbe3a7f852b22050708166fdaafbc. Source.