Channel
@CortensorNetwork
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
1,377subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002201101566 |
|---|---|
| Type | Channel |
| Username | @CortensorNetwork |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 10 August 2026 |
| On Telegram | t.me/CortensorNetwork |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 17:55 | 1,377 | -2 |
| 7 Aug 2026, 22:18 | 1,379 | no change |
| 7 Aug 2026, 15:29 | 1,379 | first reading |
20 posts held, back to 14 August 2025 — 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 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 20 posts for this entry, the most recent from 4 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 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.
153 reactions across 18 posts, in 5 distinct kinds. The most used accounts for 42.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 65 | 42.5% | |
| 🔥 | 49 | 32.0% | |
| 👍 | 33 | 21.6% | |
| 👏 | 4 | 2.61% | |
| 🥰 | 2 | 1.31% |
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 18 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 153reactions 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 14 August 2025 to 4 July 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.
🧪 Testnet Phase #4 – Wrap-Up Recap Testnet Phase #4 is wrapping up over the next 48 hours. Phase #4 focused on tightening the full Cortensor stack under more realistic conditions - network execution, Portal, router pools, observability, L3 recovery, and Mainnet Lite readiness. Core Infra: 🔹 Mainnet Lite baseline validation - Mainnet Lite moved from rough setup into real E2E baseline checks under actual mainnet con…
❤7
🧪 Testnet Phase #4 Starts Now Testnet Phase #4 is now live. Phase #4 is less about adding isolated features and more about tightening the full pipeline under realistic conditions — data → quality → routing, reliability under load, and Mainnet Lite readiness. 🔹 E2E scope lock (Phase #3 → Phase #4) Finalize the end-to-end test plan + order + pass/fail metrics (throughput/latency, recovery, drift, data integrity/offc…
❤5👍3👏1
🧪 Testnet Phase #3 – Wrap-Up Recap Testnet Phase #3 has been running for a few weeks, and we’re now wrapping up the current Phase #3 stretch. We moved from setup → real testing loops → product/data-layer alignment, with v3 agent surfaces + MVP data management + inference-quality signals exercised together. Core Infra: 🔹 v3 /delegate + /validate (testing + iteration) - Rollout + session prep complete; now iterating …
👍6❤2👏2
🧪 Testnet Phase #3 – Progress Recap So Far (1–2 Weeks Before Wrap-Up) Testnet Phase #3 has been running for a few weeks now. So far, Phase #3 has moved from initial setup → real testing loops → early product/data-layer alignment. We now have v3 agent surfaces, MVP data management, and inference-quality signals all actively exercised together. 🔹 v3 /delegate + /validate (prep → testing phase) - Initial rollout + se…
❤5🔥3👍2
🧪 Testnet Phase #3 Starts Now Testnet Phase #3 is now live. Phase #3 pushes Cortensor from “trust-layer hardening” into economic + agentic hardening - payments/staking become production-shaped, rewards become more repeatable, and router surfaces move closer to agent primitives. 🔹 Privacy feature v0.5 Router key distribution (ACL/signature checks) + dashboard privacy module + dedicated sessions marked private/publi…
❤3👍3🔥3
🧪 Testnet Phase #2 — Wrap-Up Recap (Rewards Complete) Testnet Phase #2 is now officially wrapped - and reward/prize distribution is complete. Phase #2 delivered what we wanted: a stable baseline, meaningful self-managed L3 progress, and a stronger trust + routing foundation to support the more agentic direction of Phase #3. ✅ What We Completed in Phase #2 🔹 Stable baseline achieved - Network/background tasks held…
❤5👍2🔥1
🧪 Testnet Phase #2 - Recap Phase #2 delivered a stable baseline, real traction on the self-managed L3 track, and measurable progress on the trust layer (PoI/PoUW) + observability - plus the groundwork for more agent-ready router surfaces going into Phase #3. ✅ What We Completed in Phase #2 🔹 Network stability held as a usable baseline - Background/network tasks stayed stable enough that Phase #2 stats became real …
🔥6❤1👍1
🧪 Testnet Phase #2 Starts Now Phase #2 is live - this round is about validation refinement + infrastructure hardening, so Cortensor’s trust layer becomes more deterministic, more redundant, and cheaper to run. All environments are now active and wired for Phase #2 testing: - Testnet-0 — #Arbitrum #Sepolia (L2) - Testnet-1 — $COR #L3 via RaaS - Testnet-1a — Self-managed $COR #L3 (comparison target) - Testnet-1b — Se…
🔥7❤3🥰2
🧪 Testnet Phase #2 – Preview Recap (Starts This Weekend – Jan 17) We're wrapping prep for Testnet Phase #2, which kicks off this weekend (Jan 17). Most docs + infra are now in semi-final shape, and all environments are wired for the next round of testing: - Testnet-0 — Arbitrum Sepolia (L2) - Testnet-1 — COR L3 via RaaS - Testnet-1a — Self-managed COR L3 (comparison target) - Testnet-1b — Self-managed COR L3 (intern…
❤4👍1🔥1
🗓️ 2025 Year-End Wrap - Cortensor 2025 was the year we proved a simple thesis: decentralized inference can be practical if you treat it like infrastructure - not a science project. We focused on one thing: build the execution loop, validate it under load, and set the foundation for an agent-ready and developer-ready trust layer - so builders can ship reliable AI apps without a high cost barrier. Minimal E2E MVP i…
🔥4👍2❤1
🧪 Testnet Phase #1 Recap – Integration, Load, and Engine Expansion Phase #1 was the first structured Testnet week where we focused on one thing: break the pipeline, harden the pipeline, and prove the system scales under real usage across both Testnet-0 (Arbitrum Sepolia) and Testnet-1 (COR #L3). 🔹 Incentivized Manual Testing (E2E + Payments) - Daily manual testing by community testers across different models and ta…
❤2👍1👏1
🧪 Testnet Phase #1 Starts Now The first of four structured Testnet phases is now live. We're entering a 1-week grace period: node stats and session data have been reset on Testnet-0 (Arbitrum Sepolia) and Testnet-1 ($COR Rollup L3), and this week serves as onboarding + warm-up before full regression. 🔹 Focus – System Integration & Regression - Validate all node roles and coordination flows end-to-end across apps, …
❤6👍4🔥2
Showing the 12 most recent of 20 posts we hold for @CortensorNetwork. 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 — 857,020 of 1,160,990entries 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.
Named by 3 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.
@CortensorNetwork named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“Cortensor Announcements” (@CortensorNetwork), 1,377 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/CortensorNetwork.
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.