Skip to main content
AVOID.NET
← avoid.net

Verify a decision

Every moderation decision on AVOID.NET is anchored to the Solana blockchain. You don't have to trust us — you can verify cryptographically that we committed to a verdict at a specific moment and have not rewritten it.

How verification works

  1. We commit. When a moderator accepts/rejects a submission, we serialize the decision into deterministic UTF-8 bytes (payload_canonical_string), hash it with SHA-256, encode the digest as base58, and write it to Solana inside an SPL Memo v2 transaction.
  2. We store the bytes. The exact bytes we hashed are stored alongside the decision in our database. Anyone can read them and recompute the hash in any language.
  3. You compare three values. Database hash, your independently-recomputed hash, and the hash inside the on-chain memo. If all three match, the decision is authentic and timestamped.
The on-chain memo format is AVOID.NET|v1|h:<b58-sha256>|d:<id>|t:<iso>

Find a signature on any investigation page's decision log, or run python -m src.verify_decision --signature <sig> for a CLI check.

Sequence
#1
Score
→
Cluster
mainnet-beta
Slot
450091068
Off-chain at
2026-09-24T17:03:51.331Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
6jEq8oRvjZ3txJtwRG3YCkn6GaqhFLEVJ6j2M9SFsbrn
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (14297 chars)
{"actor":"system:backfill","investigation_id":"a9a2357c-017c-409e-a727-76dcfa1373b6","kind":"publish","page_slug":"chainflip-tron-usdt-exploit-september-2026","published_at":"2026-09-24T17:03:51.204Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"Chainflip TRON USDT Exploit (September 2026)","sections":[{"content":"Chainflip's TRON integration reads swap parameters from transaction memos, unlike other supported chains that use dedicated smart contract functions. According to Chainflip's official incident report, an attacker discovered that a memo could be appended to a transaction that Chainflip validators had already signed. When the protocol's witnessing layer encountered the altered memo, it interpreted the instruction as a separate, distinct swap request. Because the fabricated swap appeared to fail, the system issued a refund — while the original deposit had already been processed — resulting in a duplicate payout for the same underlying deposit. The attacker executed this technique eight times over approximately 90 minutes on the morning of September 12, 2026. Six of the eight attempts produced unauthorized payouts. The attacker employed an escalating strategy, beginning with small amounts and approximately doubling the sum with each subsequent round. The exploit was isolated to the TRON USDT integration; Chainflip confirmed that other assets, chains, and vault funds were unaffected, and no compromise of the TRON blockchain or the USDT contract occurred.","heading":"Exploit Mechanism","severity":"critical","sources":[{"credibility":1,"name":"Incident report: Tron USDT exploit, what happened and what's next | Chainflip","type":"official","url":"https://chainflip.io/blog/tron-usdt-exploit-what-happened-and-what-happens-next"},{"credibility":2,"name":"Chainflip loses 736,442 USDT in TRON exploit | crypto.news","type":"news_article","url":"https://crypto.news/chainflip-loses-736442-usdt-in-tron-exploit/"},{"credibility":2,"name":"Chainflip pauses network after $736,442 USDT exploit in TRON integration | Coin-Turk","type":"news_article","url":"https://en.coin-turk.com/chainflip-pauses-network-after-736442-usdt-exploit-in-tron-integration/"}]},{"content":"The attacker extracted a confirmed total of 736,442.17 USDT through six unauthorized payouts. A seventh transaction involving 115,654.41 USDT — a legitimate in-flight user swap — remained unprocessed in the vault at the time of the halt and was described by Chainflip as recoverable upon a secure restart. Chainflip characterized the event as its first significant critical vault loss. The stolen funds were flagged with relevant parties in an effort to track movement through exchanges and other services; however, as of late September 2026 no public statement confirmed any portion of the stolen USDT had been frozen by Tether or recovered by other means.","heading":"Financial Impact","severity":"critical","sources":[{"credibility":1,"name":"Incident report: Tron USDT exploit, what happened and what's next | Chainflip","type":"official","url":"https://chainflip.io/blog/tron-usdt-exploit-what-happened-and-what-happens-next"},{"credibility":2,"name":"Chainflip Halts Network After $736K Tron USDT Exploit; Users to Be Made Whole | CryptoTimes","type":"news_article","url":"https://www.cryptotimes.io/2026/09/13/chainflip-halts-network-after-736k-tron-usdt-exploit-users-to-be-made-whole/"}]},{"content":"Chainflip halted all swaps, deposits, and withdrawals immediately upon detecting the exploit. The team identified a technical fix and released software version 2.2.13 on or around September 15, 2026. According to the GitHub release and related reporting, version 2.2.13 restricts TRON vault swaps to accept only direct transfers to the Vault address, eliminating the memo-attachment vector used in the attack. The release also closed all trxUSDT trading strategies, cancelled all trxUSDT pool orders, repaid trxUSDT loans, and returned lending supply before executing LP balance snapshots. Most network routes resumed between September 15 and 16. TRON remained excluded from the restart with no confirmed reinstatement date disclosed as of late September 2026.","heading":"Network Response and Patch","severity":"high","sources":[{"credibility":1,"name":"Release 2.2.13 | chainflip-io/chainflip-backend (GitHub)","type":"official","url":"https://github.com/chainflip-io/chainflip-backend/releases/tag/2.2.13"},{"credibility":2,"name":"Chainflip Plans to Restart With Tron Paused and Provider Balances Reset | Unchained","type":"news_article","url":"https://unchainedcrypto.com/chainflip-plans-to-restart-with-tron-paused-and-provider-balances-reset/"},{"credibility":2,"name":"Chainflip to relaunch cross-chain swaps minus Tron after $736,442 USDT exploit | Coin-Turk","type":"news_article","url":"https://en.coin-turk.com/chainflip-to-relaunch-cross-chain-swaps-minus-tron-after-736442-usdt-exploit/"}]},{"content":"As part of the network restart under version 2.2.13, Chainflip zeroed the active trxUSDT balances of all affected liquidity providers. Before executing the reset, the protocol wrote each provider's pre-migration trxUSDT balance to a separate on-chain record, creating a traceable ledger of amounts owed. Chainflip stated it is contacting affected providers directly and has committed to making them whole. However, as of the most recent publicly available reporting in mid-to-late September 2026, Chainflip has not disclosed a funding source for reimbursement, a payout schedule, or any confirmation that payments have been made. The TRON vault's reserves were depleted by the exploit, and no insurance mechanism or treasury draw has been publicly identified to cover the shortfall.","heading":"Liquidity Provider Balance Treatment","severity":"high","sources":[{"credibility":2,"name":"Chainflip to reset TRON USDT provider balances to zero following $736,000 exploit | CryptoSlate","type":"news_article","url":"https://cryptoslate.com/chainflip-to-reset-tron-usdt-provider-balances-to-zero-following-736000-exploit/"},{"credibility":2,"name":"Chainflip Restarts Tron Route After $736K USDT Exploit | Phemex News","type":"news_article","url":"https://phemex.com/news/article/chainflip-restarts-tron-route-with-new-accounting-after-736k-usdt-theft-97035"},{"credibility":2,"name":"Chainflip Plans to Restart With Tron Paused and Provider Balances Reset | Unchained","type":"news_article","url":"https://unchainedcrypto.com/chainflip-plans-to-restart-with-tron-paused-and-provider-balances-reset/"}]},{"content":"Users who had TRON USDT swaps in flight at the time of the exploit were also affected. Chainflip committed to making impacted users whole and described several options as under review, including treasury reserves, protocol revenue, and an insurance-style buffer, without specifying which mechanism would be used. No completed reimbursements or confirmed compensation amounts had been publicly announced as of late September 2026. The team stated that a detailed post-mortem and compensation specifics would follow once the restart plan was finalized, but no such follow-up disclosure had appeared in available sources at the time of this investigation.","heading":"User Swap Impact and Reimbursement Status","severity":"high","sources":[{"credibility":1,"name":"Incident report: Tron USDT exploit, what happened and what's next | Chainflip","type":"official","url":"https://chainflip.io/blog/tron-usdt-exploit-what-happened-and-what-happens-next"},{"credibility":2,"name":"Chainflip Halts Network After $736K Tron USDT Exploit; Users to Be Made Whole | CryptoTimes","type":"news_article","url":"https://www.cryptotimes.io/2026/09/13/chainflip-halts-network-after-736k-tron-usdt-exploit-users-to-be-made-whole/"}]},{"content":"The exploit exposed a structural design risk in how Chainflip handled memo-based transaction parsing on TRON. Because TRON does not use dedicated contract function calls for swap instructions — instead relying on memos attached to transfers — the protocol's witnessing layer was vulnerable to memo injection on already-signed transactions. The attack required no compromise of private keys, validators, or external infrastructure; it exploited the protocol's own interpretation logic. The vulnerability was specific to the TRON integration and did not affect other supported chains. The patch in version 2.2.13 restricts TRON vault swaps to direct-transfer-only, removing the memo-attachment surface. Whether a full third-party audit of the TRON integration had been conducted prior to the exploit has not been confirmed in available public sources.","heading":"Root Cause and Protocol Design Risk","severity":"medium","sources":[{"credibility":1,"name":"Release 2.2.13 | chainflip-io/chainflip-backend (GitHub)","type":"official","url":"https://github.com/chainflip-io/chainflip-backend/releases/tag/2.2.13"},{"credibility":3,"name":"Could one edited TRON transaction memo really drain Chainflip's entire vault this fast? | NewsBreak","type":"community_report","url":"https://www.newsbreak.com/we-play-on-chain-376611620/4891576794272-could-one-edited-tron-transaction-memo-really-drain-chainflip-s-entire-vault-this-fast"}]}],"sources_used":[{"credibility":1,"name":"Incident report: Tron USDT exploit, what happened and what's next | Chainflip","type":"official","url":"https://chainflip.io/blog/tron-usdt-exploit-what-happened-and-what-happens-next"},{"credibility":1,"name":"Release 2.2.13 | chainflip-io/chainflip-backend (GitHub)","type":"official","url":"https://github.com/chainflip-io/chainflip-backend/releases/tag/2.2.13"},{"credibility":2,"name":"Chainflip Halts Network After $736K Tron USDT Exploit; Users to Be Made Whole | CryptoTimes","type":"news_article","url":"https://www.cryptotimes.io/2026/09/13/chainflip-halts-network-after-736k-tron-usdt-exploit-users-to-be-made-whole/"},{"credibility":2,"name":"Chainflip loses 736,442 USDT in TRON exploit | crypto.news","type":"news_article","url":"https://crypto.news/chainflip-loses-736442-usdt-in-tron-exploit/"},{"credibility":2,"name":"Chainflip to reset TRON USDT provider balances to zero following $736,000 exploit | CryptoSlate","type":"news_article","url":"https://cryptoslate.com/chainflip-to-reset-tron-usdt-provider-balances-to-zero-following-736000-exploit/"},{"credibility":2,"name":"Chainflip Plans to Restart With Tron Paused and Provider Balances Reset | Unchained","type":"news_article","url":"https://unchainedcrypto.com/chainflip-plans-to-restart-with-tron-paused-and-provider-balances-reset/"},{"credibility":2,"name":"Chainflip Restarts Tron Route After $736K USDT Exploit | Phemex News","type":"news_article","url":"https://phemex.com/news/article/chainflip-restarts-tron-route-with-new-accounting-after-736k-usdt-theft-97035"},{"credibility":2,"name":"Chainflip pauses network after $736,442 USDT exploit in TRON integration | Coin-Turk","type":"news_article","url":"https://en.coin-turk.com/chainflip-pauses-network-after-736442-usdt-exploit-in-tron-integration/"},{"credibility":2,"name":"Chainflip to relaunch cross-chain swaps minus Tron after $736,442 USDT exploit | Coin-Turk","type":"news_article","url":"https://en.coin-turk.com/chainflip-to-relaunch-cross-chain-swaps-minus-tron-after-736442-usdt-exploit/"}],"summary":"On September 12, 2026, an attacker exploited a memo-parsing vulnerability in Chainflip's TRON USDT settlement layer, draining 736,442.17 USDT across six unauthorized payouts in approximately 90 minutes. Chainflip halted all network operations, patched the vulnerability via software version 2.2.13, and restarted most routes by September 15–16 with TRON excluded. As of late September 2026, liquidity provider balances on the affected route have been zeroed and claims recorded separately on-chain, but no funding source, repayment schedule, or confirmed reimbursement has been publicly disclosed.","timeline":[{"date":"2026-09-12","event":"Attacker exploited TRON memo-parsing vulnerability across eight rounds over approximately 90 minutes, producing six unauthorized payouts totaling 736,442.17 USDT from Chainflip's TRON vault.","source":"Chainflip official incident report","source_url":"https://chainflip.io/blog/tron-usdt-exploit-what-happened-and-what-happens-next"},{"date":"2026-09-12","event":"Chainflip halted all network swaps, deposits, and withdrawals after detecting the exploit. Stolen funds were flagged with relevant parties for tracking.","source":"Chainflip official incident report","source_url":"https://chainflip.io/blog/tron-usdt-exploit-what-happened-and-what-happens-next"},{"date":"2026-09-13","event":"Chainflip publicly disclosed the exploit, confirmed the 736,442.17 USDT loss, and pledged to make affected users whole. The team described the incident as its first significant critical vault loss.","source":"CryptoTimes","source_url":"https://www.cryptotimes.io/2026/09/13/chainflip-halts-network-after-736k-tron-usdt-exploit-users-to-be-made-whole/"},{"date":"2026-09-15","event":"Chainflip released software version 2.2.13, patching the TRON vault swap restriction and implementing LP balance snapshots. Network restart commenced with TRON excluded.","source":"GitHub release 2.2.13 / Unchained","source_url":"https://github.com/chainflip-io/chainflip-backend/releases/tag/2.2.13"},{"date":"2026-09-15","event":"Affected liquidity provider trxUSDT balances were reset to zero, with pre-migration amounts recorded in a separate on-chain ledger tracking claims owed.","source":"CryptoSlate","source_url":"https://cryptoslate.com/chainflip-to-reset-tron-usdt-provider-balances-to-zero-following-736000-exploit/"},{"date":"2026-09-16","event":"Most Chainflip swap routes restarted. TRON USDT route remained offline with no confirmed reinstatement date.","source":"Phemex News","source_url":"https://phemex.com/news/article/chainflip-restarts-tron-route-with-new-accounting-after-736k-usdt-theft-97035"},{"date":"2026-09-17","event":"Reporting confirmed no funding source, payment schedule, or reimbursement completions had been publicly disclosed by Chainflip for affected liquidity providers or users.","source":"Phemex News","source_url":"https://phemex.com/news/article/chainflip-restarts-tron-route-with-new-accounting-after-736k-usdt-theft-97035"}]},"v":1}