Telegram RegisterThe public register of Telegram
Telegram profile photo for Zilliqa Announcement

Channel

Zilliqa Announcement

@zilliqa

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

5,905subscribers

-228 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001231634137
TypeChannel
Username@zilliqa
Created15 November 2017 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live11 November 2026
Measurements held26
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/zilliqa

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 12 September 2026 and assigned it the closest of 31 fixed categories, at 52% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Growth

5,9056,1336,0196 August 2026 — 6,133 subscribers6 August 2026 — 6,133 subscribers6 August 2026 — 6,129 subscribers9 August 2026 — 6,130 subscribers12 August 2026 — 6,122 subscribers16 August 2026 — 6,100 subscribers19 August 2026 — 6,098 subscribers23 August 2026 — 6,093 subscribers26 August 2026 — 6,086 subscribers29 August 2026 — 6,081 subscribers1 September 2026 — 6,079 subscribers6 September 2026 — 6,060 subscribers11 September 2026 — 6,045 subscribers15 September 2026 — 6,035 subscribers28 September 2026 — 6,021 subscribers5 October 2026 — 5,994 subscribers12 October 2026 — 5,984 subscribers15 October 2026 — 5,975 subscribers18 October 2026 — 5,965 subscribers21 October 2026 — 5,960 subscribers26 October 2026 — 5,955 subscribers29 October 2026 — 5,939 subscribers1 November 2026 — 5,937 subscribers4 November 2026 — 5,934 subscribers7 November 2026 — 5,917 subscribers11 November 2026 — 5,905 subscribers6 August 202611 November 2026
26 measurements spanning 97 days, net -228. 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 5,871–6,167 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 26
Measured (UTC)SubscribersChange
11 Nov 2026, 07:555,905-12
7 Nov 2026, 22:565,917-17
4 Nov 2026, 21:265,934-3
1 Nov 2026, 13:595,937-2
29 Oct 2026, 22:575,939-16
26 Oct 2026, 22:595,955-5
21 Oct 2026, 06:265,960-5
18 Oct 2026, 08:565,965-10
15 Oct 2026, 13:315,975-9
12 Oct 2026, 10:005,984-10
5 Oct 2026, 18:015,994-27
28 Sept 2026, 10:216,021-14
15 Sept 2026, 10:406,035-10
11 Sept 2026, 09:016,045-15
6 Sept 2026, 17:006,060-19
1 Sept 2026, 22:276,079-2
29 Aug 2026, 21:376,081-5
26 Aug 2026, 12:526,086-7
23 Aug 2026, 08:586,093-5
19 Aug 2026, 11:166,098first reading

Engagement

33 posts held, back to 26 January 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 11 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
13.1%
avg views ÷ 5,905 subscribers
Avg views / post
776
2 posts measured
Reaction rate
1.16%
reactions ÷ views · ER floor
Posts in window
2
of 33 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 29 October 2026
Posts held33 (26 January 2026 – 29 October 2026)
Views total1,552
Reactions total18
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken5 Nov 2026, 01:23 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
5s
Average length
5s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

715 reactions across 33 posts, in 16 distinct kinds. The most used accounts for 40.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤28940.4%
🔥17524.5%
👍9613.4%
👏466.43%
🎉324.48%
🍾273.78%
❤‍🔥162.24%
👌141.96%
🏆81.12%
🥰30.42%
🫡30.42%
🐳20.28%
👀10.14%
🕊10.14%
🙏10.14%
🤩10.14%

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 33 of the 33 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 715 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 33 most recent posts we hold, published 26 January 2026 to 29 October 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

Telegram’s own ‘edited’ marker: 0 of 2 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

29 Oct 2026, 16:57 UTC695 views7 reactionsread 5 November 2026

The Fourth exchange migration hard fork is scheduled for block height 39,242,023 expected on 30 October 2026 at ~07:00 UTC. This upgrade will: - Migrate XT exchange’s ZIL balances from legacy Schnorr addresses to verified Zilliqa EVM addresses. - Enable validator reward distribution every epoch instead of every block. - Activate Pectra support, updating Zilliqa’s EVM compatibility. - Enable the migration of legacy …

❤7

Signed Rahul

27 Oct 2026, 16:55 UTC857 views11 reactionsread 5 November 2026

Update on the recent security incidents Our investigation with an external cybersecurity firm is ongoing. Here’s what we can share today. Affected services and tokens X-Bridge and ZRC2 proxy contracts used by some liquidity pools, including PlunderSwap, have been affected. The affected tokens are zUSDT, SEED, kUSD and Zoge. Native ZIL and the Zilliqa EVM network are not affected. X-Bridge remains suspended. Plea…

👍7❤3👀1

Signed Rahul

16 Oct 2026, 10:26 UTC≈1,440 views16 reactionsread 5 November 2026

Following the security incident involving the Zilliqa Ledger app, we worked with major exchanges to coordinate the migration of ZIL to Zilliqa EVM. This included South Korea’s five major exchanges: Upbit, Bithumb, Coinone, Gopax and Korbit. Throughout this process, we responded to the questionnaire and subsequent follow-up questions from the Digital Asset eXchange Alliance (DAXA), the self-regulatory organisation rep…

👍12❤4

Signed Rahul

6 Oct 2026, 07:04 UTC≈1,830 views3 reactionsread 5 November 2026

• The Third hard fork went live successfully. ZIL balances for Bithumb, Uphold and Bybit were migrated from Legacy Schnorr addresses to verified Zilliqa EVM addresses. • Paribu and CEX.IO have also resumed ZIL deposits and withdrawals on Zilliqa EVM, alongside Binance, Bitvavo, HTX, MEXC, LBank and Bitkub. • The Zilliqa Ledger app is now available. Ledger users can use it alongside the ZKP Migration App to migrate …

❤3

Signed Rahul

2 Oct 2026, 14:05 UTC≈1,970 views13 reactionsread 5 November 2026

A quick follow-up on migration progress: • The ZKP Migration App installation guide is now available for macOS, alongside the Linux and Windows guides https://blog.zilliqa.com/migrate-zil-from-a-legacy-account-to-zilliqa-evm/. • Binance, Bitvavo, HTX, MEXC, LBank and Bitkub have resumed ZIL deposits and withdrawals on Zilliqa EVM. • Third hard fork is scheduled for 5 October 2026 at 10:00 UTC, at block height 37,4…

❤13

Signed Rahul

24 Sept 2026, 16:36 UTC≈1,950 views14 reactionsread 5 November 2026

The ZKP Migration App is available for retail holders moving ZIL from a Legacy (Zil1...) account to a Zilliqa EVM (0x...) account. We’ve published a step-by-step guide covering installation on Windows and Linux, what to expect inside the app, and how to submit your claim after generating a proof. Full guide: https://blog.zilliqa.com/migrate-zil-from-a-legacy-account-to-zilliqa-evm/

🔥9❤3🎉1👏1

Signed Rahul

23 Sept 2026, 10:56 UTC≈1,550 views21 reactionsread 5 November 2026

A quick ZIL migration update: - Binance has announced support for the ZIL token migration https://www.binance.com/en/support/announcement/detail/343ad3d991c64b27842482f1fb1fe11c. - Bitvavo and MEXC have resumed ZIL deposits and withdrawals on Zilliqa EVM. - The ZKP migration tool is in its final stages of preparation. It will be released soon. - The second exchange migration hard fork was successfully activated o…

🔥8❤6🎉3👍2❤‍🔥1👌1

Signed Rahul

17 Sept 2026, 10:38 UTC≈1,720 views17 reactionsread 5 November 2026

The Second hard fork for the migration of centralised exchange balances is scheduled for block height 36,383,378, with an estimated activation time of 22 September 2026 at approximately 07:21 UTC. It will migrate participating exchange's ZIL balances from legacy Schnorr-based wallets to the verified Zilliqa EVM wallet addresses provided by each exchange. The following exchanges are included in the second hard fork:…

❤17

Signed Rahul

7 Sept 2026, 16:21 UTC≈1,720 views28 reactionsread 5 November 2026

MEXC has successfully completed the migration of ZIL to Zilliqa EVM. ZIL deposits and withdrawals will reopen on 8 September 2026 at 10:00 UTC. Users should ensure they select the Zilliqa EVM network when depositing, as legacy ZIL deposits will no longer be supported. Read the full MEXC announcement.

🔥13❤5👍5👏3🍾1🎉1

Signed Rahul

2 Sept 2026, 16:18 UTC≈2,040 views28 reactionsread 5 November 2026
Photo

Six weeks after legacy transactions were paused, we’ve published a full update on where things stand and what comes next. Key developments: - The first exchange migration hard fork completed today. - A second exchange migration is planned for mid-September. - The self-guided, zero-knowledge migration tool for legacy wallet holders is in its final stages and remains on track for mid-September. - A community proposal…

❤17👏5🎉4🔥1🙏1

Signed Rahul

24 Aug 2026, 15:40 UTC≈2,080 views18 reactionsread 5 November 2026

Exchange migration hard fork scheduled: The first hard fork for the migration of Centralised exchange balances is scheduled for block height 34,844,968, with an estimated activation time of 2 September 2026 at approximately 12:58 UTC. It will migrate the ZIL balances held in participating exchanges’ legacy Schnorr-based wallets to the new Zilliqa EVM wallet addresses provided and verified by each exchange. The fol…

👍13❤5

Signed Rahul

21 Aug 2026, 08:50 UTC≈1,540 views11 reactionsread 5 November 2026

A full post-mortem into the legacy Zilliqa Ledger application incident has been published. The report provides a transparent account of: • The technical root cause • How the vulnerability could be exploited • The timeline of the incident and response • The confirmed impact • The actions taken to prevent further exploitation • The migration and recovery work now under way The investigation established that a flaw in…

❤6👌4🎉1

Signed Rahul

Showing the 12 most recent of 33 posts we hold for @zilliqa. 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.

Forward network

Republished by

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

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 8 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.

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Kadena Official Announcements
@Kadena_Announcements · 22,424
Telegram ranks this channel #26 of 85 here — alongside 84 others — read 18 September 2026
Sonic Announcements
@SonicAnnouncements · 20,276
Telegram ranks this channel #29 of 88 here — alongside 87 others — read 25 September 2026
Cardano Announcements
@CardanoAnnouncements · 34,917
Telegram ranks this channel #39 of 85 here — alongside 84 others — read 1 September 2026
Casper Official Announcements
@casperofficialann · 33,713
Telegram ranks this channel #64 of 81 here — alongside 80 others — read 1 September 2026
MultiversX - Announcements
@MultiversXAnn · 267,284
Telegram ranks this channel #66 of 87 here — alongside 86 others — read 15 August 2026

This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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 11 November 2026 — this entry's latest reading, not the date you are reading this.

“Zilliqa Announcement” (@zilliqa), 5,905 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/zilliqa.

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.