Telegram RegisterThe public register of Telegram

Channel

CIPHER38

@cipher38ai

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

716subscribers

-12 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003579604523
TypeChannel
Username@cipher38ai
Created26 March 2026measured — dated from the channel’s first post
First recorded6 August 2026
Last confirmed live7 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 7 August 2026
On Telegramt.me/cipher38ai

Growth

7167287226 Aug 2026, 11:04 — 728 subscribers6 Aug 2026, 16:13 — 728 subscribers7 Aug 2026, 10:04 — 716 subscribers6 Aug 2026, 11:047 Aug 2026, 10:04
3 measurements taken within a single day, net -12. 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 714–730 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 10:04716-12
6 Aug 2026, 16:13728no change
6 Aug 2026, 11:04728first reading

Engagement

10 posts held, back to 26 March 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 10 posts for this entry, the most recent from 8 May 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

12 reactions across 5 posts, in 3 distinct kinds. The most used accounts for 58.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
758.3%
👍433.3%
🔥18.33%

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

Measured over the 10 most recent posts we hold, published 26 March 2026 to 8 May 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

8 May 2026, 17:00 UTC258 views3 reactionsread 6 August 2026

Cipher38 Documentation is live The docs cover the signal engine, index structure, clusters, information sources, weights, classifications and scoring, how the system actually works under the hood. Feedback on what to add or change is welcome, drop it in the comments cipher38.org/docs |c38.info

👍21

7 May 2026, 00:14 UTC248 viewsread 6 August 2026

Cipher38 Project Update Hey everyone, GUI v1.1 and updated scoring system are live on c38.info. The next interface update is planned alongside the functional update in 2.5 weeks The day after tomorrow we're publishing the full documentation and roadmap. The docs cover the signal engine, index structure, clusters, information sources, weights, classifications and scoring, how it all works. The roadmap covers every

25 Apr 2026, 11:00 UTC228 views3 reactionsread 6 August 2026
Photo

The update is just about to roll out ! It will include a redesigned UI for better user understanding, …along with a range of additional improvements. Keep an eye on our social media! #bsc #fourmeme #ai

👍2🔥1

21 Apr 2026, 23:22 UTC292 views2 reactionsread 6 August 2026
Photo

The system is live. The dashboard is open. c38.info Public — free now Admitted — 10,000 C38 Inner Circle — 38,000 C38 Access to the next layer is now open. cipher38.org | c38.info

2

14 Apr 2026, 22:26 UTC396 viewsread 6 August 2026

The token has been trading for approximately six hours. We are currently finalizing updates to the official website, which should be live within the next few hours. Token: http://four.meme/en/token/0x46F425d87B92da4aaea9D44F0842aD494A1D4444 Website: http://cipher38.org (live), http://c38.info (live)

3 Apr 2026, 15:45 UTC≈6,030 views3 reactionsread 6 August 2026

🧠 February 2026 crypto VC report (Wu Blockchain): • 62 deals disclosed — down 50% YoY • $866M total funding — down 71% YoY • DeFi: 29% of projects • AI: 11.3% of projects Less capital. More selective. Exactly the market where fundamentals start to matter again. The noise is clearing. What's left standing is infrastructure, real usage, and actual agent activity on-chain. BSC fits all three.

3

2 Apr 2026, 12:06 UTC≈5,990 viewsread 6 August 2026

🏦 Holding tokens for access vs holding tokens for speculation. Most people think about token ownership in terms of price appreciation. There’s a second model: tokens as access keys. Hold enough → gate unlocks → you get something you couldn’t get otherwise. This changes the holding calculus entirely. You’re not just betting on price — you’re paying for a service in a form that can also appreciate. In that model, the f

2 Apr 2026, 04:39 UTC≈5,970 viewsread 6 August 2026

⛓️ Why BSC is the right infrastructure layer for on-chain access control. Speed: 0.45s block times means verification is near-instant Cost: gas fees low enough that wallet verification doesn't cost more than it's worth Volume: $1.7B+ daily DEX volume means the tokens used for verification have real liquid markets Ecosystem: Binance Wallet, PancakeSwap, four.meme — all native to the same stack On-chain gating only wor

1 Apr 2026, 05:28 UTC≈6,590 views1 reactionsread 6 August 2026

🤖 BSC just became the #1 blockchain for AI agents. Numbers as of March 2026: • 34,278 registered ERC-8004 agents on BSC • 523,000 agent transactions in a single day (March 10) • $18.1M in agent-driven DEX volume on March 11 • Total agents across all chains grew from 337 → 130,000+ since Jan 2026 (+39,000%) Ethereum built for humans. BSC is being rebuilt by machines. The infrastructure is already here. The question

1

Showing the 10 most recent of 10 posts we hold for @cipher38ai. 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 — 399,992 of 1,183,361entries 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.

Mentions

Named by 1 registered channel — 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.

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

“CIPHER38” (@cipher38ai), 716 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/cipher38ai.

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.