# THORChain resumes TRON swaps after Tether lifts USDT freeze Author: KriptoMeta Editorial Team Language: English Published: 2026-10-10T07:48:44+03:00 Updated: 2026-10-10T07:48:44+03:00 ![Conceptual technology cover showing thawing frost on a metal module with the Tether symbol](https://kriptometa.com/uploads/thorchain-de-usdt-dondurmasi-kalkti-tron-takaslari-acildi-935555eb78bb_article.webp) ## Key takeaways - Four of THORChain’s six TRON vaults were affected by the blacklist. - An October 9 update at 15:58 UTC confirmed that swaps had restarted. - No explanation for the decision to blacklist the addresses was provided. Developer Khal estimated that four vaults holding 1.45 million USDT were temporarily restricted. THORChain’s co-founder said the team received no advance communication. THORChain resumed USDT swaps on TRON on October 9 after Tether lifted restrictions on the protocol’s vault addresses. Technical co-founder Chad Barraford [reported that the addresses appeared to be unfrozen](https://x.com/CBarraford/status/2108582069958033547) at 15:35 UTC and said trading would resume shortly. LeoDex developer Khal confirmed that swaps were running again in an update at 15:58 UTC. [Khal’s October 9, 2026 update on the resumption of swaps](https://x.com/khalkaz/status/2108587916574572872) ## Four vaults held 1.45 million USDT In his [analysis of transaction records](https://x.com/khalkaz/status/2108552150238286208), Khal said four of THORChain’s six TRON vaults were added to the USDT blacklist in block 86,958,330. Those addresses held about 1.45 million USDT, or 93% of the USDT in the protocol’s TRON vaults. He reported that swaps, transaction signing and [liquidity-pool](https://kriptometa.com/en/glossary/liquidity-pool) activity on the TRON side were halted roughly 27 minutes later. Around 363,000 USDT in outbound payments was queued during the disruption. Those figures come from Khal’s published analysis; they do not mean that all THORChain assets were frozen or that the TRON blockchain stopped operating. **A frozen balance is not the same as stolen funds.** The reported amount referred to USDT held in the vaults. Khal said no funds were lost when he announced the restart; that update was not an independent loss audit. ## The reason for the freeze remains unclear While the restrictions were still in place, Barraford [wrote](https://x.com/CBarraford/status/2108557964629921938): “We don’t know why this choice was made.” He said there had been no communication with Tether beforehand and the team was trying to establish contact. His suggestion that there might have been an error or misunderstanding was not a confirmed explanation. The Tether statements reviewed for this report did not give a reason for restricting THORChain’s addresses. In a [September 28 statement](https://tether.io/news/tether-has-supported-nearly-550-million-in-iran-linked-usdt-freezes-as-u-s-expands-sanctions-campaign/), the issuer described its cooperation with law enforcement and its [policy of aligning wallet freezes](https://kriptometa.com/en/tether-iran-usdt-550-million-freezes) with the US OFAC sanctions list. That earlier statement does not establish a connection between the THORChain incident and any particular sanction or investigation. ## Vault signatures and token permissions are separate controls THORChain’s [technical documentation](https://dev.thorchain.org/bifrost/vault-behaviors.html) describes vaults as on-chain accounts managed jointly by validators. Outbound transfers use a threshold signature scheme: enough participating nodes must sign, without assembling the complete [private key](https://kriptometa.com/en/glossary/private-key) in one place. For [issuer-backed stablecoins](https://kriptometa.com/en/stablecoin-risks-checklist) such as USDT, the issuer can separately block an address from sending tokens. Having validators ready to sign a transaction does not, by itself, release blacklisted tokens. Funds left in a user’s own wallet are also separate from assets the user has submitted to a protocol vault for a swap. In a [community broadcast on October 1](https://blog.thorchain.org/can-or-should-thorchain-censor-transactions), the protocol team explained that nodes can pause a chain’s activity when there is a solvency concern, but lack a separate control for selectively blocking one swap. The recording below covers that earlier technical discussion. It predates the October 9 disruption and is not an account of that incident. [THORChain’s October 1, 2026 broadcast — relevant section at 1:14:23](https://www.youtube.com/watch?v=wHXs-4ab_P8&t=4463s)