Telegram RegisterThe public register of Telegram
Telegram profile photo for Context Layer

Channel

Context Layer

@ContextLayer

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

73subscribers

-1 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002654450500
TypeChannel
Username@ContextLayer
Created17 May 2025measured — dated from the channel’s first post
First recorded9 August 2026
Last confirmed live22 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/ContextLayer

Growth

737473.57 August 2026 — 74 subscribers9 August 2026 — 74 subscribers22 August 2026 — 73 subscribers7 August 202622 August 2026
3 measurements spanning 15 days, net -1. 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 73–74 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 13:4773-1
9 Aug 2026, 21:4774no change
7 Aug 2026, 16:3374first reading

Engagement

10 posts held, back to 17 May 2025the 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 28 June 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
1m 43s
Average length
34s

Measured directly from 3 videos 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.

Reaction mix

16 reactions across 7 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
16100.0%

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 7 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 16reactions 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 17 May 2025 to 28 June 2025, 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

28 Jun 2025, 01:35 UTC≈1,140 views5 reactionsread 9 August 2026
Video

👋 Welcome to Context Layer We’re building autonomous AI agents that interact directly with Ethereum, fully onchain, voice-enabled, and 100% decentralized. No centralized backend. No scripts. Just real AI acting in real time. 🧠 What You Can Do Right Now: 🎙️ Use voice or text to talk to the AI agent 🔁 Execute ERC-20 token swaps via smart contracts 💸 Perform secure token transfers with no wallet UI 🌐 Access everythin

5

28 Jun 2025, 00:10 UTC701 views3 reactionsread 9 August 2026
Photo

🎉 ContextLayer AI Chat Contest, $500 in prizes! https://x.com/Contextlayereth/status/1938283296699650202 🧠 Try the first fully onchain AI agent 🎙️ Talk via voice or text 🔁 Swap tokens 💸 Transfer funds 🌐 100% decentralized frontend (Fleek/IPFS) 📸 How to Join: 1️⃣ Use the AI agent 2️⃣ Post a screenshot or video 3️⃣ Tag us and use these hashtags: $CXLYR #contextlayer #fleek #chatai #decentralizedai 🏆 Prizes 🥇 1st –

3

26 Jun 2025, 17:31 UTC≈1,060 views1 reactionsread 9 August 2026
Video

📽️ ContextLayer Chat AI — Real Onchain Intelligence We’re not just building another chatbot. This is a fully autonomous, voice-enabled AI agent — deployed 100% onchain. 🎙️ Talk to your agent 💱 Swap tokens 💸 Transfer crypto 🛠️ Deploy AI modules Watch the full showcase and see it in action. contextlayer.on-fleek.app

1

27 May 2025, 03:17 UTC≈2,420 views2 reactionsread 9 August 2026
Video

👋 Welcome to Context Layer We’re building autonomous AI agents that interact directly with Ethereum, fully onchain, voice-enabled, and 100% decentralized. No centralized backend. No scripts. Just real AI acting in real time. 🧠 What You Can Do Right Now: 🎙️ Use voice or text to talk to the AI agent 🔁 Execute ERC-20 token swaps via smart contracts 💸 Perform secure token transfers with no wallet UI 🌐 Access everythin

2

20 May 2025, 07:48 UTC746 views1 reactionsread 9 August 2026
Photo

🤖 How AI Agents Take Action with Blockchain via the Context Layer Imagine an AI agent that doesn't just give answers—but takes action. The AI Agent detects your intent: “Stake my tokens,” or “Show my last DeFi yield.” The Context Layer steps in: It understands the request, fills in missing context (like wallet address, token, network), and prepares the task. The Blockchain executes: Smart contracts are triggered. Tra

1

19 May 2025, 12:09 UTC385 views1 reactionsread 9 August 2026
Photo

🌐 Context Layer Protocol is revolutionizing the way AI interacts with blockchain! Imagine AI models that do not just work in isolation but are fully aware of live blockchain data and smart contract states, enabling secure, real-time, context-aware automation like never before. With Context Layer Protocol, you can: 🔗 Seamlessly connect AI workflows directly to on-chain state and smart contract logic ⚡ Automate proce

1

17 May 2025, 17:13 UTC407 views3 reactionsread 9 August 2026
Photo

🔍 The Role of the Context Layer in Connecting #AI Agents to #Blockchain 🤖 AI Agent: Issues contextual requests ⚙️ Context Layer: Manages task execution, processes contextual data, interfaces via API Gateway 🔗 Blockchain: Executes smart contracts, manages on-chain storage, facilitates on-chain operations ✨ This synergy enables seamless, decentralized AI-driven interactions with blockchain technology, unlocking new lev

3

Showing the 10 most recent of 10 posts we hold for @ContextLayer. 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.

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

“Context Layer” (@ContextLayer), 73 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/ContextLayer.

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.