Fragment tests USDT payments via the TRON network

Fragment is preparing to accept USDT payments via the TRON network. On November 2, styles for a 'USDT in TRON' payment tab and a dedicated code branch for the invoice QR code appeared in Fragment's code on five Telegram test stands. Later that evening, one stand reverted to its previous code. On November 3, the same code, now with a TRON fee hint, landed on the production fragment.com server, but the site's pages do not load it yet and the payment form has no TRON tab: there, Stars and Premium are paid for in TON, as well as in USDT and USDC on the TON, Ethereum, Polygon, and Base networks. This affects users who hold USDT on TRON and currently transfer it to another network before paying Fragment.

What Appeared on the Test Stands

The static assets for Telegram's web services, including Fragment's script and styles, are served by several test stands. Each operates with its own code version, and changes are deployed to them sequentially. The TRON-related change propagated across five stands within two hours (archive snapshot times, UTC):

Before November 2, the word tron was not present in any version of these files. The archive of test stands has been maintained since February 2026, and for all five stands, since March. As of the evening of November 2, the change remains on four out of five stands. The stands are more like parallel branches than sequential steps, so a rollback on one stand does not necessarily mean TRON has been abandoned.

What changed on November 3

At 10:54 UTC, a fee hint block appeared in the styles on stand y-: it is shown only when usdt_tron is selected as the payment method in the form. The hint's text is in neither the script nor the styles — the server inserts it into the page, and it can be read once the tab goes live. At 11:21, stand a- reverted to code without TRON, so the tron branch remains on three of the five stands: y-, b- and l-.

The same day, the code from stand y- reached the production fragment.com server: auction.js there was modified at 10:19 UTC and auction.css at 11:14 UTC, and both match stand y- byte for byte. The site's pages, however, still load the previous versions (auction.js?112 and auction.css?111) served from the Cloudflare cache, and the list of payment methods is assembled by the server itself, with no usdt_tron in it yet.

How Fragment Currently Accepts Stablecoins

Until the end of May, Fragment accepted TON and USDT on the TON network. On May 29, tabs for USDT and USDC on Ethereum-compatible networks (EVM networks) appeared on the live site. Currently, the payment form on the Stars purchase page and the Premium gift page offers:

These same networks appeared on the test stands on May 28, approximately 24 hours before the live site.

An invoice on an EVM network works as follows: Fragment provides an address, an amount, and an expiry time, while a countdown runs on the page. The address, judging by a test invoice, is single-use: nothing arrived at or left the Polygon test invoice address from June 4 to mid-October, except for that single payment. The invoice QR code is structured according to the Ethereum payment link standard (EIP-681): it includes the token contract, network ID, recipient address, and amount. Therefore, a wallet that understands EIP-681 will open a pre-filled transfer for the correct token on the correct network after scanning. The second method is to connect a wallet via WalletConnect (Reown AppKit library), and the site will prompt you to sign the transfer. Arbitrum is hardcoded into the list of networks for connection, but there is no Arbitrum payment tab on the site.

How a TRON Invoice Differs from Others

In the test code for TRON, the QR code contains only the address—without the token, amount, or network. After scanning, a wallet will open a transfer to this address, but you will have to manually select and enter the token and amount. The reason is probably due to standards: the ethereum: link format is defined for Ethereum networks and does not work with TRON, and there is no universally accepted token payment link format that all TRON wallets would understand. A bare address can be read by any wallet.

A second change in the same set concerns the timer. The countdown digits previously came from the expiry time sent by the server, but the progress bar beneath them was scaled for 600 seconds: for invoices longer than ten minutes, it would remain full until less than 600 seconds remained. Now, the progress bar's scale is also sent by the server, with 600 seconds remaining as a fallback value—meaning invoices of different durations are expected, according to the code. Whether this change is related to TRON cannot be determined from the code; presumably, an invoice that requires manual input needs more time.

The list of networks for wallet connection in the test code has not changed: it still includes Ethereum, Base, Polygon, and Arbitrum. Payments in TRON, according to the code, will likely only be possible via QR code or copied address.

What to Do

• Currently. You cannot pay for Stars or Premium from TRON on fragment.com. USDT on TON, Ethereum, and Polygon networks, and USDC on Ethereum, Base, and Polygon are accepted.
• The network is selected on the tab. An invoice is issued for a single network. The QR code itself specifies the network, while for payments via a copied address, you select it manually. EVM networks share a common address, so a wallet will send a token to the same address on a different network without objection, but this will not pay the invoice, and such a transfer can only be recovered through support.
• If TRON is released, the QR code will not contain the amount: you will need to enter it manually down to the cent and complete the transaction before the timer expires.

How It Was Verified

• Archive of test stands testserverchangesall: full history of auction.js and auction.css files since February 2026, for all five stands since March, with a search for the string tron across all versions.
• Archive of the live site prodserverchangesall: EVM network tabs in styles on May 29, invoice code with WalletConnect network list in the next snapshot.
• Live fragment.com on November 2: the script auction.js?112 does not contain the string tron, and the Stars purchase and Premium gift pages show six stablecoin and TON tabs.
• Live fragment.com on November 3: auction.js and auction.css fetched past the Cloudflare cache (with a different version number) are files modified at 10:19 and 11:14 UTC, with the tron branch and the fee hint, and their checksums match stand y-; the Stars purchase and Premium gift pages still load ?112 and ?111 and offer the same seven payment options.