Telegram RegisterThe public register of Telegram
Telegram profile photo for Cere Network Announcement Channel

Channel

Cere Network Announcement Channel

@cerenetwork

On this record: Growth · Engagement · Reactions · Posts · Polls · Citations · Telegram's recommendations · Cite this entry

8,662subscribers

-134 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-1001361600093
TypeChannel
Username@cerenetwork
Created2 June 2019measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live4 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 4 September 2026
On Telegramt.me/cerenetwork

Growth

8,6628,7968,7296 August 2026 — 8,796 subscribers6 August 2026 — 8,796 subscribers6 August 2026 — 8,792 subscribers9 August 2026 — 8,781 subscribers12 August 2026 — 8,770 subscribers16 August 2026 — 8,747 subscribers19 August 2026 — 8,730 subscribers22 August 2026 — 8,719 subscribers26 August 2026 — 8,695 subscribers28 August 2026 — 8,683 subscribers31 August 2026 — 8,669 subscribers4 September 2026 — 8,662 subscribers6 August 20264 September 2026
12 measurements spanning 29 days, net -134. 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 8,642–8,816 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Sept 2026, 02:168,662-7
31 Aug 2026, 18:488,669-14
28 Aug 2026, 19:038,683-12
26 Aug 2026, 02:068,695-24
22 Aug 2026, 15:288,719-11
19 Aug 2026, 11:488,730-17
16 Aug 2026, 18:268,747-23
12 Aug 2026, 23:048,770-11
9 Aug 2026, 16:218,781-11
6 Aug 2026, 22:028,792-4
6 Aug 2026, 10:178,796no change
6 Aug 2026, 09:418,796first reading

Engagement

20 posts held, back to 6 August 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 28 pages 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 15 April 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

224 reactions across 20 posts, in 3 distinct kinds. The most used accounts for 58.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥13258.9%
8738.8%
🎉52.23%

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 20 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 224 reactions 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 6 August 2025 to 15 April 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

15 Apr 2026, 13:21 UTC≈2,900 views11 reactionsread 28 August 2026

📢Update on the recent Hyperbridge incident We want to reassure our community that Cere Network's operations remain unaffected. Due to our secure lock & release integration and minimal exposure, the impact on Cere is negligible. A small batch (valued at $4,500) of $CERE tokens was affected and they have already been absorbed by the market. There is no further impact. Hyperbridge is actively working on fixes and out

🔥74

4 Mar 2026, 10:58 UTC≈3,040 views4 reactionsread 28 August 2026
Poll

What AI agent/automation tools are you actually using day-to-day?

  1. OpenClaw42%
  2. Sim.ai2%
  3. n8n18%
  4. Zapier12%
  5. CrewAI7%
  6. LangChain9%
  7. Make5%
  8. Other42%

The shares total 137%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

4

24 Feb 2026, 09:44 UTC≈3,210 views5 reactionsread 28 August 2026

🚀 New Runtime Upgrade Referendum is Live! We've just proposed Release-v7.3.14, a runtime dependency upgrade from polkadot-stable2506 → polkadot-stable2512, keeping Cere aligned with the latest audited Polkadot/Substrate runtime and unblocking future upgrades. 🗳️ Referenda is live now: vote before execution on Wednesday at 2 PM CET! What this upgrade brings ✅ Latest security patches, consensus & runtime bug fixes f

🔥41

2 Dec 2025, 11:18 UTC≈4,210 views15 reactionsread 28 August 2026

🚀 New Runtime Upgrade Referendum is Live! We’ve just proposed an upgrade to run the Cere chain on Polkadot-stable2506 (from 2503). This keeps Cere aligned with the latest audited Polkadot/Substrate runtime and unblocks future upgrades (2509, 2512, etc.). What this upgrade brings - ✅ Latest security patches, bug fixes & protocol improvements from upstream - ✅ A clean upgrade path for the next Polkadot-stable releases

🔥105

7 Nov 2025, 12:15 UTC≈3,920 views3 reactionsread 28 August 2026

🚀 Referendum 44 is live: unblock nomination pool users 🗳️ This proposal re-enables users to access the funds that were previously stuck in the Subwallet and Talisman nomination pools — a follow-up to the successful fix in Proposal 43. 🗳️ Cast your vote here: https://cere.polkassembly.io/referenda/44

🔥3

29 Oct 2025, 14:42 UTC≈3,990 views5 reactionsread 28 August 2026

🗳️ Referendum 43: Fix for Withdrawals From Nomination Pools TL;DR: Some delegators couldn’t withdraw their unbonded funds due to a delegatedStaking.notEnoughFunds error. This referendum ships a runtime fix that correctly links Staking and DelegatedStaking, so unbonded tokens properly propagate and become withdrawable. What’s changing - Ensures proper linkage between the staking and DelegatedStaking modules. - Once y

3🔥2

22 Oct 2025, 14:30 UTC≈2,950 views16 reactionsread 28 August 2026
Photo

🔈Cere × UofT AI Agents Club Hackathon 🔈 We’re excited to collaborate with the University of Toronto AI Agents Club on a 3-day AI agents hackathon (Oct 27–30). The program is designed for UofT students to explore Cere’s AI Stack, building and deploying live agents on real Telegram data. What this partnership highlights - Event-driven data processing with Streams & Rafts - Modular agent deployment and real-time obser

16

22 Oct 2025, 12:33 UTC≈2,490 views9 reactionsread 28 August 2026

🗳 Referendum #41 — Temporarily chill underperforming validators TL;DR: This proposal temporarily chills a set of consistently underperforming/unstable validators on Cere mainnet so the network can finalize blocks reliably, protect nominators from unnecessary slashing, and unblock the pending runtime upgrade. Please review and vote below. Nominators: Unstake / re-delegate away from the underperforming validators now

🔥54

9 Oct 2025, 15:59 UTC≈2,260 views4 reactionsread 28 August 2026

Going live in 2 minutes with the community AMA on Discord: https://discord.gg/f8Jqxk5M?event=1425602957537312848 🫡

🔥4

8 Oct 2025, 22:11 UTC≈2,460 views8 reactionsread 28 August 2026
Photo

Tomorrow at 4PM UTC Bren will be holding a community AMA on Discord: https://discord.gg/f8Jqxk5M?event=1425602957537312848

🔥8

25 Sept 2025, 10:35 UTC≈2,770 views17 reactionsread 28 August 2026
Photo

🔥 Cere AI Stack Alpha test 🔥 We need your help to stress test our new system. 👉 How to join: 1️⃣ Jump into @thisiscere 2️⃣ Type /fun 3️⃣ Send the bot a selfie 🤳 💰 Bonus: The funniest/coolest selfie wins $50 USDC 💡 Why this matters This bot isn’t just a toy, it’s a fun way way to test our the underlying Cere AI Stack end-to-end. - Custom/open source models are hosted on Cere’s DDC (in this test we use SAM2 Hiera L

🔥125

22 Sept 2025, 12:37 UTC≈2,110 views13 reactionsread 28 August 2026
Photo

We are currently the #1 farm on Quickswap BASE 🔥 Give this post some love: https://x.com/quickswapdex/status/1970087754651643993

7🔥6

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

4 Mar 2026, 10:58 UTCAnonymous Poll57 voters

What AI agent/automation tools are you actually using day-to-day?

  1. OpenClaw42%
  2. Sim.ai2%
  3. n8n18%
  4. Zapier12%
  5. CrewAI7%
  6. LangChain9%
  7. Make5%
  8. Other42%

The shares total 137%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 20 most recent posts we hold, published 6 August 2025 to 15 April 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

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

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.

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.

Casper Official Announcements
@casperofficialann · 36,197
Telegram ranks this channel #5 of 81 here — alongside 80 others — read 1 September 2026
Portal to Bitcoin Announcements
@portaltobitcoin_announcements · 88,298
Telegram ranks this channel #59 of 88 here — alongside 87 others — read 1 September 2026

This channel appears in 2 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 4 September 2026 — this entry's latest reading, not the date you are reading this.

“Cere Network Announcement Channel” (@cerenetwork), 8,662 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/cerenetwork.

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.