As mentioned in reopening announcement, here is the full context behind the deliberate decision that resulted in 316 duplicate transactions reaching a few hundred users on TON.

When the bridge was drained during the May 11 incident, a number of legitimate cross-chain transactions initiated by users were left in limbo: processed on the TAC side, but never settled on TON because the TON Adapter no longer held the funds to complete them.

Ahead of the relaunch, we faced a clear choice on how to handle these pending transactions.

The first option was to hard-fork TAC: coordinating with validators and partners, re-issuing tokens to mirror a snapshot of the previous state, and a number of operations that break the immutability of the TAC blockchain. Immutability is a core property of any serious chain, and we will not compromise it to patch an operational issue, however convenient that shortcut would have been.

The second option was to let the TON Adapter process these pending transactions through its normal flow once the bridge was live. This preserved chain soundness and immutability. The trade-off: 316 transactions reprocessed on TON, delivering approximately $80,000 to users who were not meant to receive them.

We chose immutability.

If you received an unexpected transaction in any of these assets: TAC, USDT, BLUM, tsTON, Re7 USDTv2, Re7 cbBTCv2, Re7 WETHv2, mRe7YIELD, cbBTC, syUSDT - kindly return the funds back to the TAC team multisig on TON: UQAkTfPo4zo72Zyr5dk1QrWvCWlgA0gRd3njyg5hqmwdrQrI

We appreciate your cooperation.