TAC (🫰,✨️)

We're happy to share that cross-chain transactions between TON and TAC are now available again. The patched sequencer software has been independently reviewed by our auditor and TON ecosystem partners and we can resume operations with complete confidence. TAC CCL is now safer than ever. All missing funds in USDT, BLUM, and tsTON have been restored. Users can use TAC-powered products (DeFi Wallet vaults, Acid ID staking feature, and others) as before. Affected users expecting transactions on TON in BLUM or USDT will receive their funds automatically - no action is required from their side. ❗️Important Notice: As part of the relaunch, a necessary step resulted in some users receiving more tokens than expected. More details to follow in a post later today. Thank you for your support, patience and trust.

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.

@Bancor 👀🔥

Get exclusive access to DeFi's most advanced limit orders: → adjustable price, budget, and strategy type ✨ without starting all over again → no expiry → pause trading → no third-party dependencies → set a single execution price, or a custom range. → full and partial fills → any standard ERC-20 pair → 100% price certainty → zero maker fees on filled orders → sandwich attack immunity → a built-in solver system helping fill orders with liquidity from major DEXs chainwide → the ability to link with another order to automate a recurring buy low, sell high trading strategy @CarbonDeFixyz 🗿 Live on @ethereum, @SeiNetwork, @Celo, @COTInetwork, @TacBuild, and @base through 🦾's licensed deployment.

@meooowwwwwwwn Yes, we have bug bounty program. There's a dedicated space for bug bounty reports in our docs: docs.tac.build/bug-bounty/ove… Please, follow the flow and we'll definitely investigate your report with the team!

@TacBuild I found a vulnerability in your code that issues new tokens indefinitely. Which email address should I use to report this? Do you have a bug bounty program?

❗️Important notice for node operators: TAC mainnet upgrade v1.6.0 is scheduled for June 30, ~12:00 UTC (block ~21,776,800). If you run a TAC node, action is required before the upgrade height: upgrade to the v1.6.0 binary and set evm-chain-id = 239 in app.toml. We also recommend Cosmovisor to automate it.

Full details of the upgrade: github.com/TacBuild/tacch… Cosmovisor guide to handle the upgrade automatically: github.com/TacBuild/tacch…

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.

For any questions: t.me/TACbuild

We're happy to share that cross-chain transactions between TON and TAC are now available again. The patched sequencer software has been independently reviewed by our auditor and TON ecosystem partners and we can resume operations with complete confidence. TAC CCL is now safer than ever. All missing funds in USDT, BLUM, and tsTON have been restored. Users can use TAC-powered products (DeFi Wallet vaults, Acid ID staking feature, and others) as before. Affected users expecting transactions on TON in BLUM or USDT will receive their funds automatically - no action is required from their side. ❗️Important Notice: As part of the relaunch, a necessary step resulted in some users receiving more tokens than expected. More details to follow in a post later today. Thank you for your support, patience and trust.

For any questions, please reach us in our Telegram community: t.me/TACbuild

Update on the TAC CCL re-enablement. The final patches at the sequencer level are being independently reviewed by our auditor and TON ecosystem partners. This work is in its final stage. Restoration of the missing funds in USDT, BLUM, and tsTON is underway. Yesterday we completed three steps: 1) The assets recovered from the attacker were consolidated into USDT 2) USDT was moved to TON 3) BLUM held on the TAC side was burned as planned. At this point, we need to settle the outstanding gap in BLUM and USDT, which we are currently working on. We expect the TAC CCL to re-open very soon. The full announcement will follow once everything is in place. In the meantime, please rely only on this account and our official Telegram for updates. Any unsolicited "support" or "recovery" DMs should be treated as scams. Thank you for your support, patience, and trust throughout this process.

Read the full post-mortem: tac.build/blog/post-mort…

On May, 11th a security incident affected TON-TAC asset bridge. Over the past few days, TAC team has been engaged in post incident efforts, which, four days after, have resulted in the return of approximately 80% of the affected assets. Today, we are publishing the official post-mortem report detailing everything that happened behind the scenes of the incident. The root reason traced to a single missing validation in our sequencer software: the responsible party deployed a counterfeit jetton wallet on TON, and the sequencer accepted the counterfeit tokens because it did not verify the sender wallet's code hash. The total loss was approximately $2.86M across USDT, BLUM, and tsTON. Following a public appeal and subsequent recovery efforts, the assets under the responsible party's control were successfully secured, with approximately 90% returned to TAC-controlled multisigs on May 14th and the remaining 10% retained by the responsible party. The bridge remains paused while the patched sequencer software is independently reviewed by our auditor and TON partners. We understand the urgency - affected users and integrated projects want the bridge back, and so do we. At the same time, security comes before speed. Cross-chain operations will only resume once the fixed software has been fully verified and the imbalance has been closed using the recovered assets and the TAC Foundation's token reserve. Both steps take time due to coordination with multiple entities, and we are unable to provide precise timelines at this stage due to external dependencies. When operations resume, the change will be transparent to users with no action required from their side. The remaining gap will be covered by the TAC Foundation treasury, ensuring zero financial impact on users or the protocol. Official updates are only posted through this account and our Telegram; any unsolicited "recovery" or «support» DMs are scams. Thank you to the @ton_blockchain community and the broader TON and EVM ecosystems for their support.

Multisigs under TAC control with received funds: ETH/BSC/TAC → #tokentxns" target="_blank" rel="nofollow noopener">etherscan.io/address/0xa05C… TON → tonviewer.com/EQAkTfPo4zo72Z… ZEC → blockchair.com/zcash/address/…

We're happy to announce that ~90% of the funds from the May 12th security incident have been recovered. The attacker decided to return the funds that were sitting across Ethereum, TON, TAC, BSC and Zcash, and retained the 10% as a bounty. We are happy to confirm that the unbalance on the cross-chain layer will be completely fixed. A detailed update and full post-mortem will follow in the coming days. Big thanks to @SEAL_911, our security partners, the @ton_blockchain community and to every partner team that stood with us.

We, the TAC team, based on coordinated discussions with our security partners and law enforcement, formally assert that upon successful return of the funds to the TAC team multisig at 0xa05CBfF7b395DeA456539Db279AbC6EE5a8150f9 and EQAkTfPo4zo72Zyr5dk1QrWvCWlgA0gRd3njyg5hqmwdrVcN and t1dXd2EUAe34BYEtNUtNfrBFQTTs8LhoTUH: 1. Legal action will not be taken against the operator of the address(es) eth/bsc:0x46FB375EAc7a44C231b2b7aB762040ee74908CDc, zec:t1h6NcBAciYGdaVb4Ej1AELTx1D9UF9WUDr and ton:EQBPHhXyG_vbsAEnB6YccNhhaVc6I3ixOCc7vriaOzo4AFA8. The entity controlling the above address(es) carried out the incident affecting the TAC cross-chain layer in multiple transactions, resulting in the movement of approximately $2.8M in USDT, BLUM, and tsTON. Any further investigations or legal matters against the entity, in relation to this incident, will end. 2. We view this occurrence as a white-hat rescue, and as a result: eth:0x46FB375EAc7a44C231b2b7aB762040ee74908CDc and zec:t1h6NcBAciYGdaVb4Ej1AELTx1D9UF9WUDr will be rewarded with 10% of the recovered fund as a white-hat bounty from the TAC team, which translates to approximately 13 ETH + 300ZEC. 3. The remaining balance, will be directed to the TAC team multisigs mentioned above.

Following the security incident, we identified an exploit on the TON side of the TAC crosschain layer that was carried out by an external attacker. The incident resulted in a loss of approximately $2.8M across USDT, BLUM, and tsTON. The TAC token, TON and all ERC-20 tokens bridged from Ethereum are NOT affected. The bridge remains paused while forensic analysis and remediation work are ongoing. A post-mortem with additional disclosure will be published in the next 48 hours. We are actively working with law enforcement, SEAL 911, and our security partners to trace and block the stolen funds. Our focus is on making users whole and fully restoring bridge liquidity through a legally structured sale of Foundation’s TAC token treasury reserves. We will continue to share updates through our official channels. Thank you for your patience and trust.

We are currently investigating a security incident affecting the TAC bridge with TON. The bridge has been paused as soon as we received reports from our security partners. The issue appears isolated to native TON Jettons bridged from TON (excluding $TON). $TON and every other Ethereum native asset are not affected. TON cross-chain transactions remain paused while the investigation is ongoing. Protecting our users is our top priority. Should any users be affected as a result of this incident, we are committed to doing everything we can to make them whole. We will be sharing regular updates through our official channels.

@LucidlyFi @RealAcidLabs @ton_blockchain 🤝🤝

@TacBuild @RealAcidLabs @ton_blockchain 🫡

A great dive from @LucidlyFi on how we’re working with @RealAcidLabs to test and implement a completely new monetisation tool for Telegram Mini Apps, powered by institutional-grade DeFi strategies right on @ton_blockchain

@Boy1Sniper @LucidlyFi @RealAcidLabs @ton_blockchain got you some study for this weekend sniper 🤓

@TacBuild @LucidlyFi @RealAcidLabs @ton_blockchain I think it high time to study tacman 👀