Telegram RegisterThe public register of Telegram

Supergroup

Cluster Protocol

@clusterprotocolchat

Has discussion group

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

26,296members

-101 since we began measuring on 6 August 2026

191 online right now

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

Register entry

Telegram ID-1001918521291
TypeSupergroup
Username@clusterprotocolchat
DescriptionOrchestration layer of private ai for autonomous workflows and prompt to dapp browser based IDE on Base. Backed by DAO5 and Paper Ventures X: https://twitter.com/ClusterProtocol Announcement Channel: https://t.me/clusterprotocolann
CreatedBetween 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live14 August 2026
Measurements held10
On Telegramt.me/clusterprotocolchat

Growth

26,29626,39826,3476 August 2026 — 26,397 members6 August 2026 — 26,398 members7 August 2026 — 26,395 members8 August 2026 — 26,367 members10 August 2026 — 26,360 members11 August 2026 — 26,343 members12 August 2026 — 26,328 members13 August 2026 — 26,322 members14 August 2026 — 26,296 members14 August 2026 — 26,296 members6 August 202614 August 2026
10 measurements spanning 8 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 26,281–26,413 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
14 Aug 2026, 20:1926,296no change
14 Aug 2026, 16:3426,296-26
13 Aug 2026, 03:5326,322-6
12 Aug 2026, 05:0626,328-15
11 Aug 2026, 02:5226,343-17
10 Aug 2026, 02:1126,360-7
8 Aug 2026, 23:2126,367-28
7 Aug 2026, 19:5526,395-3
6 Aug 2026, 20:2226,398+1
6 Aug 2026, 17:1626,397first reading

Engagement

No public post preview. We read this entry on 14 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

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.

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

“Cluster Protocol” (@clusterprotocolchat), 26,296 members as measured 14 August 2026. Telegram Register, tgregister.com/channel/clusterprotocolchat.

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.