🚨 TAC does not just «treat» the consequences of the hack. They actually replace $TAC with BNB Chain.
After the August 22 attack, the attacker had 1.662 billion TAC left. Now the team has decided to replace the old BEP20 contract with a new one—so these tokens will no longer be involved in the new distribution.
And the most important thing: the snapshot has already been taken.
As of block 119,573,620, the team recorded who owned $TAC . Those balances will be the basis for the migration. Addresses associated with the attack will be excluded. So buying the old $TAC after the snapshot and then trying to calculate/get the new tokens—won’t work.
For Binance Alpha, the swap of the new token is scheduled for September 4. The new PancakeSwap pool and the bridge are also planned to be restored by Friday.
And separately: there will be no claim site. If someone asks you to connect a wallet «for TAC migration»—then this isn’t a migration anymore, but a very familiar crypto scam scenario.
I love it when, after an exploit, a team moves from beautiful statements to a specific mechanism. Here the mechanism exists—now let’s see how it works in practice. These are the details worth watching—follow @MoonMan567
After the August 22 attack, the attacker had 1.662 billion TAC left. Now the team has decided to replace the old BEP20 contract with a new one—so these tokens will no longer be involved in the new distribution.
And the most important thing: the snapshot has already been taken.
As of block 119,573,620, the team recorded who owned $TAC . Those balances will be the basis for the migration. Addresses associated with the attack will be excluded. So buying the old $TAC after the snapshot and then trying to calculate/get the new tokens—won’t work.
For Binance Alpha, the swap of the new token is scheduled for September 4. The new PancakeSwap pool and the bridge are also planned to be restored by Friday.
And separately: there will be no claim site. If someone asks you to connect a wallet «for TAC migration»—then this isn’t a migration anymore, but a very familiar crypto scam scenario.
I love it when, after an exploit, a team moves from beautiful statements to a specific mechanism. Here the mechanism exists—now let’s see how it works in practice. These are the details worth watching—follow @MoonMan567
