Channel
@ZilliqaDevsAnnouncements
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Cite this entry
75subscribers
-2 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001378996551 |
|---|---|
| Type | Channel |
| Username | @ZilliqaDevsAnnouncements |
| Created | Between 1 March 2018 and 14 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 8 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 3 times, most recently 8 October 2026 |
| On Telegram | t.me/ZilliqaDevsAnnouncements |
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 28 September 2026 and assigned it the closest of 31 fixed categories, at 91% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Sept 2026, 11:01 | 75 | -1 |
| 15 Aug 2026, 17:08 | 76 | -1 |
| 9 Aug 2026, 20:16 | 77 | no change |
| 8 Aug 2026, 00:24 | 77 | first reading |
20 posts held, back to 14 July 2021 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of 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 4 February 2022. An engagement rate over an empty window would be a number about nothing.
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.
Dear Zilliqa community, We are making a small update to the Zilliqa ZRC-6 NFT standard. We will be adding “token_owner” to the events emitted in the following transitions - SetSpender - AddOperator - RemoveOperator https://github.com/Zilliqa/ZRC/blob/master/zrcs/zrc-6.md This update will provide more verbose information for events emitted. It will useful for use cases like NFT indexer and frontend interacting with…
Dear community, We have released zilliqa-js version v3.3.4 We have introduced improvements such as - A fix for next.js compatibility issue with crypto module - A fix for transaction version issue with account module The release note can be found at https://github.com/zilliqa/zilliqa-js/releases/tag/v3.3.4 Regards, Zilliqa team
Dear ecosystem developers, We have released a new utility scilla-json-utils. scilla-json-utils simplifies and helps with the construction of Scilla JSON data. https://www.npmjs.com/package/@zilliqa-js/scilla-json-utils
Zilliqa's Creator Economy is Evolving! Introducing the ZRC-6 NFT token standard With key features like royalty payments and batch operations, the ZRC-6 token standard will further us in our push to be the Layer-1 of choice for creators 🔥 Read more on our blog: https://blog.zilliqa.com/introducing-zrc-6-the-new-and-improved-nft-standard-to-fuel-the-creator-economy-c3661dae3287
Dear community, We have released ZilliqaJS version v3.3.3 We have introduced improvements such as - A fix for ESM issue that caused by require syntax for elliptic signature The release note can be found at https://github.com/Zilliqa/Zilliqa-JavaScript-Library/releases/tag/v3.3.3 Regards, Zilliqa team
Dear community, We have released ZilliqaJS version v3.3.2 We have introduced improvements such as - A fix for .d.ts file type checking error in subscriptions package The release note can be found at https://github.com/Zilliqa/Zilliqa-JavaScript-Library/releases/tag/v3.3.2 Regards, Zilliqa team
Dear community, We have released ZilliqaJS version v3.3.1 We have introduced improvements such as - A fix for .d.ts file type checking error when skipLibCheck is false - Code refactoring The release note can be found at https://github.com/Zilliqa/Zilliqa-JavaScript-Library/releases/tag/v3.3.1 Regards, Zilliqa team
Dear community, We have released ZilliqaJS version v3.3.0 We have introduced numerous improvements such as - Support API such as getTransactionsForTxBlockEx and getTxnBodiesForTxBlockEx - Add tslib as dependency and remove the need for user to manual install it - Code refactoring The release note can be found at https://github.com/Zilliqa/Zilliqa-JavaScript-Library/releases/tag/v3.3.0 Regards, Zilliqa team
Dear community, We have released ZilliqaJS version v3.2.0 We have introduced numerous improvements such as - Support NodeJS 16 - Update GetSmartContracts API - Fix tx block header type - Code refactoring - Documentation update The release note can be found at https://github.com/Zilliqa/Zilliqa-JavaScript-Library/releases/tag/v3.2.0 Regards, Zilliqa team
Dear community, We have released ZilliqaJS version v3.1.0. Version V3.1.0 supports the new API “GetStateProof” which was introduced in Zilliqa v8.1.0. In addition, we have introduced numerous improvements such as - Build optimization and improvement - Code refactoring - Documentation update The ZilliqaJS example code is now moved to https://github.com/Zilliqa/Zilliqa-JavaScript-Library-Examples The release note …
Dear everyone, The mainnet recovery of v8.1.0 has been completed (31 Aug 2021, 11:30 UTC). Please download and use the new configuration for v8.1.0. This recovery addresses an issue observed with the most recent network upgrade. For more information, please refer to the following blog post: https://blog.zilliqa.com/post-mortem-report-for-mainnet-upgrade-v8-1-0-94d00ce23ff2 If you are an exchange provider, then do …
Dear exchanges and ecosystem, We noticed an issue with the recent upgrade. We are pausing the processing of the transactions while we investigate the issue. We will keep you posted Regards, Zilliqa team
Showing the 12 most recent of 20 posts we hold for @ZilliqaDevsAnnouncements. 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.
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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“Zilliqa Developer Announcements” (@ZilliqaDevsAnnouncements), 75 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/ZilliqaDevsAnnouncements.
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.