Кабинет

Посты канала TAC Announcement Channel

сначала новые

#43Фото
Просмотры2190%к среднему
Пересылки2
Реакции7
Комментарии—
#42Текст
Просмотры588+168%к среднему
Пересылки2
Реакции21
Комментарии—
#41Фото
Просмотры1 171+435%к среднему
Пересылки13
Реакции6
Комментарии—
#39Фото
Просмотры1 119+411%к среднему
Пересылки11
Реакции29
Комментарии—
#38Фото
Просмотры2 985×14к среднему
Пересылки58
Реакции25
Комментарии—
#36Превью ссылки
Просмотры883+303%к среднему
Пересылки18
Реакции25
Комментарии—
#35Текст
Просмотры1 131+416%к среднему
Пересылки12
Реакции28
Комментарии—
#34Превью ссылки
Просмотры1 296+492%к среднему
Пересылки17
Реакции26
Комментарии—
#33Превью ссылки
Просмотры1 285+487%к среднему
Пересылки17
Реакции7
Комментарии—
#32Текст
Просмотры2 593×12к среднему
Пересылки23
Реакции64
Комментарии—
#31Фото
Просмотры2 494×11к среднему
Пересылки7
Реакции19
Комментарии—
#30Текст

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.

Открыть в Telegram
Просмотры258 688×1,18 тыс.к среднему
Пересылки43
Реакции42
Комментарии—
#29Фото
Просмотры2 476×11к среднему
Пересылки9
Реакции45
Комментарии—
#28Текст
Просмотры2 434×11к среднему
Пересылки8
Реакции47
Комментарии—
#27Превью ссылкиизменён

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 community and the broader TON and EVM ecosystems for their support. Read the full post-mortem: https://tac.build/blog/post-mortem-report-tac-bridge

Открыть в Telegram
Просмотры179 404×819к среднему
Пересылки69
Реакции80
Комментарии—
#26Превью ссылки
Просмотры3 292×15к среднему
Пересылки15
Реакции41
Комментарии—
#25Текст
Просмотры3 030×14к среднему
Пересылки13
Реакции30
Комментарии—
#24Текст
Просмотры3 088×14к среднему
Пересылки11
Реакции55
Комментарии—