Telegram RegisterThe public register of Telegram

Channel

ZKsync ∎

@zksync

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

28,223subscribers

-101 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001408717617
TypeChannel
Username@zksync
DescriptionOfficial channel for announcements from ZKsync team. Join our Discord community: https://join.zksync.dev/ Have an issue? Report it to the support team: https://t.me/zksync_support
CreatedBetween 1 April 2019 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/zksync

Growth

28,22328,32428,273.56 August 2026 — 28,324 subscribers6 August 2026 — 28,324 subscribers7 August 2026 — 28,311 subscribers8 August 2026 — 28,290 subscribers9 August 2026 — 28,277 subscribers10 August 2026 — 28,270 subscribers11 August 2026 — 28,245 subscribers12 August 2026 — 28,223 subscribers6 August 202612 August 2026
8 measurements spanning 6 days, net -101. 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 28,208–28,339 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 07:3428,223-22
11 Aug 2026, 05:1128,245-25
10 Aug 2026, 03:5828,270-7
9 Aug 2026, 05:0328,277-13
8 Aug 2026, 01:4128,290-21
7 Aug 2026, 00:3528,311-13
6 Aug 2026, 02:0128,324no change
6 Aug 2026, 01:1428,324first reading

Engagement

20 posts held, back to 1 June 2023the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 17 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 11 June 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
5
Links
168

Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

11 Jun 2024, 07:08 UTC≈95,600 viewsread 12 August 2026

Introducing the ZK Token It’s time to put the ZK token into the hands of the community. It’s your turn to govern ZKsync’s future. Read more: https://blog.zknation.io/zk-token/

10 Jun 2024, 09:14 UTC≈93,900 viewsread 12 August 2026

Introducing the ZK Nation To bring Ethereum to the masses, ZKsync must maintain strong social and technical decentralization guarantees. To remain resilient in the journey ahead, ZKsync depends on ZK Nation, a vibrant community empowered to drive meaningful change through protocol governance. The ZKsync protocol token will empower ZK Nation with the ability to propose protocol upgrades, deliberate, and vote on thei

18 Apr 2024, 20:14 UTC≈84,300 viewsread 12 August 2026

Native $USDC is live on zkSync Era Until now, all USDC on zkSync has been bridged, either through the native zkSync bridge or third-party bridges. Native USDC is different. It’s backed by Circle with additional benefits. In the coming days, you'll be able to migrate bridged USDC.e to native USDC on your preferred DEX. Source: https://twitter.com/zksync/status/1777704832297513437

18 Apr 2024, 20:14 UTC≈62,200 viewsread 12 August 2026

Withdrawal Process Change pt. 2 zkSync Era is designed to have the best possible user experience — low fees, high throughput, and native account abstraction. That’s why, for the past year, Matter Labs voluntarily paid transaction fees to withdraw funds bridged from zkSync to Ethereum Mainnet. As zkSync continues to decentralize, the network cannot rely on central intermediaries to operate key protocol mechanisms. S

17 Jan 2024, 19:43 UTC≈80,400 viewsread 12 August 2026

Withdrawal Process Change We would like to inform you of a recent change in the withdrawal process. Effective January 16, 2024, withdrawals below 0.01 ETH will need to be manually claimed. What This Means If you initiated a withdrawal of less than 0.01 ETH from zkSync Era to Ethereum using native bridges such as txFusion or L2Scan since January 16, please take the below action. These funds are safe but will requi

8 Jan 2024, 17:37 UTC≈71,400 viewsread 12 August 2026

Etherscan for zkSync Era zkSync transactions are now available on Etherscan, the gold standard block explorer for searching and browsing verified Ethereum blocks and transactions. Dive in: http://era.zksync.network/ Source: https://x.com/zksync/status/1744343399417737266?s=20

22 Nov 2023, 21:26 UTC≈72,600 viewsread 12 August 2026

Catch up on zkSync with Alex G In case you missed it a new episode was released of the Zero Knowledge podcast, featuring Alex Gluchowski, co-founder of Matter Labs the team behind zkSync. Dive deep into the evolution and future of zkSync, as Alex shares insights on zkSync Lite, zkSync Era, zkEVM, Boojum, zkPorter, ZK Stack, hyperchains, and more. https://www.youtube.com/watch?v=OLFbG0yvBak This episode is packed

8 Nov 2023, 18:35 UTC≈56,400 viewsread 12 August 2026

🗓 Devconnect 2023 Events Calendar Check out the 30+ opportunities to meet up with the zkSync community the week of Devconnect — from zkSync Connect, to the ZK Bazaar and zkCafe, to technical talks, workshops, happy hours, and headline sessions! https://matterlabs.notion.site/matterlabs/Devconnect-2023-Events-Calendar-b4e40d3063f24bca87790fc5491d36ab

12 Oct 2023, 13:55 UTC≈58,300 viewsread 12 August 2026

Portal and Block Explorer Changes The zkSync Era Portal (Bridge) will now be run by TX Fusion which is now providing a user-friendly interface for the Portal, enabling seamless token bridging and transaction viewing. https://portal.txsync.io/ The Block Explorer, crucial for exploring transactions, blocks, and contracts, is fully open-source, welcoming local community-run versions. These steps, part of a broader mov

19 Sept 2023, 21:55 UTC≈55,600 viewsread 12 August 2026

Meet zkSync's new ecosystem portal 👋 You can now explore the universe of dapps on zkSync with the new ecosystem portal managed by DappRadar, which features dapps’ key metrics, rankings, and more. Visit: https://ecosystem.zksync.io/ or https://zksync.dappradar.com/ Learn more: https://zksync.mirror.xyz/TKWRSWULp-UNmx4I8A1bp81vQgWXZlQzUCelO8kQpS4

Showing the 12 most recent of 20 posts we hold for @zksync. 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 — 29,311 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.

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 28 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

Names

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

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

“ZKsync ∎” (@zksync), 28,223 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/zksync.

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.