Telegram RegisterThe public register of Telegram

Channel

TAC Announcement Channel

@TACbuild1

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

1,543subscribers

-4 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002398984487
TypeChannel
Username@TACbuild1
CreatedBetween 1 September 2024 and 13 February 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live11 August 2026
Measurements held3
Confirmed unchanged2 times, most recently 11 August 2026
On Telegramt.me/TACbuild1

Growth

1,5431,5471,5456 August 2026 — 1,547 subscribers6 August 2026 — 1,547 subscribers8 August 2026 — 1,543 subscribers6 August 20268 August 2026
3 measurements spanning 3 days, net -4. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,542–1,548 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 16:561,543-4
6 Aug 2026, 07:341,547no change
6 Aug 2026, 00:431,547first reading

Engagement

20 posts held, back to 13 February 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 8 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

828 reactions across 19 posts, in 22 distinct kinds. The most used accounts for 33.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤27933.7%
🔥19924.0%
👍9811.8%
👏495.92%
🎉455.43%
🙏313.74%
🤔202.42%
😁141.69%
🥰141.69%
🕊131.57%
😱111.33%
💩91.09%
🍾70.845%
👀70.845%
🤣60.725%
💯50.604%
😍50.604%
🏆40.483%
💊40.483%
🤝30.362%
2 further kinds50.604%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 19 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 828reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 13 February 2025 to 8 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

8 Jul 2026, 21:55 UTC≈1,380 views53 reactionsread 7 August 2026

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 f…

🙏17👍11❤10🤣6💩5🦄2😁2

29 Jun 2026, 15:06 UTC≈1,640 views14 reactionsread 7 August 2026
Photo

❗️ Important notice for TAC node operators The TAC mainnet upgrade v1.6.0 is scheduled for June 30, 2026, ~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 • Set evm-chain-id = 239 in app.toml We also recommend running Cosmovisor to apply the upgrade automatically at the scheduled height, no manual intervention needed at block time.…

👍7❤4🤝3

10 Jun 2026, 17:35 UTC≈226,000 views34 reactionsread 7 August 2026

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 fund…

🙏11❤9🕊7🔥5💊2

10 Jun 2026, 14:58 UTC≈1,930 views37 reactionsread 7 August 2026
Photo

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 sta…

❤18🔥8👏6🤔3💊2

3 Jun 2026, 14:49 UTC≈1,980 views39 reactionsread 7 August 2026

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…

❤18👏10👍5🔥4🤔2

20 May 2026, 19:40 UTC≈155,000 views70 reactionsread 7 August 2026

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 …

👍22👏20❤12😁8🤔3🙏3💩2

15 May 2026, 15:10 UTC≈2,870 views36 reactionsread 7 August 2026

Hello everyone! 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 da…

❤21👍4👏4🤔4🔥3

13 May 2026, 17:54 UTC≈2,690 views27 reactionsread 7 August 2026

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 a…

👍10👏5🔥5🤔3❤2💩2

12 May 2026, 18:17 UTC≈2,790 views52 reactionsread 7 August 2026

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…

👍19😱11❤7🤔5👏4🤨3😁2🥰1

27 Feb 2026, 11:14 UTC≈2,920 views26 reactionsread 7 August 2026

gTAC 🫰 Been a while since the last announcement, we have been building in the background. TAC is advancing DeFi on TON by bringing blue-chip assets and institutional-grade yield directly into Telegram. We recently announced the launch of cbBTC (Coinbase Wrapped BTC) on TON, enabling Bitcoin to be used natively on Telegram using TON-native wallets. https://x.com/TacBuild/status/2025962907713097857 Fully backed 1:…

🔥12👍5❤4🥰3😁2

6 Jun 2025, 16:16 UTC≈2,780 views33 reactionsread 7 August 2026

Tune in to our space with Cosmos: https://x.com/i/spaces/1lDxLzXreZqGm

❤25🍾7🕊1

6 Jun 2025, 15:01 UTC≈2,810 views23 reactionsread 7 August 2026

GTAC The TAC TEAM is live on Discord for the community AMA, tune in: https://discord.com/channels/1313636846852640870/1345287656610992158

❤18🔥5

Showing the 12 most recent of 20 posts we hold for @TACbuild1. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Citation-graph rank

Citation-graph rank — 15,831 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Wallet DeFi News
@tonwallet_news_en · 638,4041 post

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 4 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

Новости Wallet DeFi
@tonwallet_news_cis · 433,15610 postsWallet DeFi News
@tonwallet_news_en · 638,4049 postshamster blok
@hblok · 2381 post-_-
@kivi_loading · 1731 post

Names

Channels on the register whose handles appear in this channel's posts.

TAC Build Portal
@TACbuild · 6,0272 postsWallet DeFi News
@tonwallet_news_en · 638,4041 post

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 8 August 2026 — this entry's latest reading, not the date you are reading this.

“TAC Announcement Channel” (@TACbuild1), 1,543 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/TACbuild1.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.