Tomorrow, September 9, at 10:00 UTC we start the $TAC contract swap on BNB Chain. Every address that held the old BEP20 $TAC at block 119,573,620 gets the new token 1:1. That is 465.4M new $TAC to around 3,700 addresses, sent in several batches over the following hours. This covers regular wallets, EIP-7702 wallets, Safe multisigs, LP positions in the main TAC pools on PancakeSwap and Uniswap, and bridge transfers that were in flight at the halt. You do not need to do anything. The new tokens come from our distribution wallet 0xaF7834D0cBf8542d169b380f768d889c3Fb06d86. New $TAC contract: 0xb305E6954e4e0Cd021c06Ec355681abc8A00dbD7. If it does not show up in your wallet, add it manually with this address. There is no claim site. We will never ask you to connect your wallet anywhere. Be careful with anyone who does. LP amounts reflect the $TAC in your position at the snapshot. The whole swap is visible on-chain from the wallet above.

If your address is a smart contract (vesting, protocol contract or any other) and it is not in this batch, get in touch and we will process the swap for it. Requests are open until October 8: forms.gle/vqD5AHX7xFnvuwFx7

Update on exchanges. $TAC deposits and withdrawals have also resumed on @kucoincom and @bitget.

Binance Alpha has completed the $TAC contract swap on BNB Chain at 1:1. Deposits, withdrawals and trading for the new token are open. If you held $TAC on Binance Alpha, the swap was done for you. Nothing to do.

$TAC on BNB Chain is migrating to a new contract. The snapshot has already been taken. We are replacing the BEP20 $TAC on BNB Chain, where 1,662,322,353 $TAC is linked to the August 22 exploit. The migration cuts the attacker off from the stolen supply he still controls. New $TAC contract on BNB Chain: 0xb305E6954e4e0Cd021c06Ec355681abc8A00dbD7 Any other address is fake. Snapshot block: 119,573,620 (September 2, 17:16 UTC). It was taken before this announcement so the attacker could not use his supply to interfere with the distribution. Snapshot only records who held $TAC at that block. What happens now: > Held $TAC in your own wallet or in an LP position at the snapshot block: you receive the new token automatically. Attacker-linked addresses are excluded. > Held on Binance Alpha: the token swap and trading of the new token go live there on Friday, September 4, 08:00 UTC. > Proposed airdrop list will be published shortly, with three business days to dispute it. > New PancakeSwap pool and TAC<>BNB Chain bridging will be back by Friday. > There is no claim site. Never connect your wallet anywhere to "claim". Do not buy or trade the old token: purchases via trading/OTC/transfers after the snapshot block will not be credited. $TAC on Ethereum and TON is not part of this migration.

⚠️ $TAC on BNB Chain: STOP all activity. Do not trade, swap or transfer it, on any exchange or pool, until further notice.

In coordination with the @cosmoslabs_io team, we are holding off on publishing our post-mortem and recovery plan. Since the vulnerability involves the shared Cosmos EVM module, Cosmos Labs asked us to give them a bit more time to ensure all affected Cosmos-based networks are patched safely. We're fully aligned with prioritizing the security of the wider ecosystem. Both documents will be published in full very soon.

On August 22 an attacker exploited a vulnerability in the Cosmos EVM precompile layer and drained a single account on TAC. We halted the chain at block 24,671,475 to stop it. The defect is not in TAC-specific code. It sits in the shared Cosmos EVM module, and several other chains running that module were hit by the same class of attack within a day. This was a drain, not a mint. No tokens were created and total supply is unchanged: 2,985,651,403 TAC was moved from one account to another. Only $TAC was affected, and all other assets on TAC are intact. We are finalising the technical post-mortem and the relaunch plan, and expect to publish both tomorrow. The plan is built to normalize $TAC balances and include all the necessary Cosmos fixes to safely restore the network. We are working with SEAL 911 and with exchanges on the funds that moved. Updates come only from @TacBuild and our official Telegram channel.

The TAC team is currently investigating an exploited vulnerability on the Cosmos-based EVM side of TAC, affecting only $TAC supply. We are working, together with the TAC validators on a temporary chain-halt that will happen over the next few minutes. We will keep you posted on the next findings and next steps for chain resume. please only follow official channels for updates.

Over the past 24 hours TAC experienced a sharp price decline. We know many of you are holding losses today. We take that seriously, and you deserve a direct explanation. 1. No exploit. TAC was not hacked in any form. The protocol operates exactly as designed. All on-chain assets are safe. 2. No insider selling. Neither the team nor early backers contributed to the selling pressure. Team and investor tokens remain fully locked and vested. Unlocks have not begun and are technically impossible at this stage. 3. What happened. We completed an internal review of trading activity, both on-chain and using data available to us from centralized venues. There was no minting of tokens and no malicious activity. The decline was a liquidation cascade triggered initially by a large perpetual futures sell order exceeding the relatively thin liquidity on the market. That in turn resulted in a cascade of liquidations on the perp market as well as sell pressure on spot venues. We continue to monitor trading activity closely. 4. What’s next. The team is fully committed to building. We are finalizing a set of measures focused on strengthening market structure, deepening liquidity, and rebuilding confidence with our community, partners, and investors. We will share the concrete details later this month. Price moved. Fundamentals did not. We build for the long term.

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.