Celestia Labs acquires Sovereign Labs. This acquisition establishes Celestia Labs as a full-stack custom blockchain development partner for companies building onchain, marking a new chapter for our go-to-market strategy and ambitions https://x.com/celestia/status/2077408410522591242

Channel
Celestia Announcements
@CelestiaOrg
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
1,520subscribers
-6 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001321769569 |
|---|---|
| Type | Channel |
| Username | @CelestiaOrg |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/CelestiaOrg |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 07:44 | 1,520 | -3 |
| 11 Aug 2026, 00:42 | 1,523 | -3 |
| 7 Aug 2026, 15:56 | 1,526 | no change |
| 6 Aug 2026, 20:01 | 1,526 | first reading |
Engagement
20 posts held, back to 15 May 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 2 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 36.8%
- avg views ÷ 1,520 subscribers
- Avg views / post
- 559
- 1 post measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 1
- of 20 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 15 July 2026 |
|---|---|
| Posts held | 20 (15 May 2025 – 15 July 2026) |
| Views total | 559 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 18:10 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
- Video runtime
- 1m 34s
- Average length
- 47s
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.
Recent posts
The forum will be undergoing scheduled maintenance starting at around 13:00 CET today. There may be some temporary downtime during this period. Thank you for your patience.
Celestia's engineering roadmap is compressing V8 (including Hibiscus) is live on Mocha, with Mainnet following next, bringing single-signature cross-chain transfers and ZK-verified messaging to networks built on Celestia. The following protocol upgrade after V8 will bring 3-second block times and 32 MiB blocks, expanding blockspace capacity in a single step upgrade that will clear the path for Fibre — the highest-t…
Introducing Celestia Private Blockspace Confidential onchain finance — built for high-performance markets. Positions, balances, and execution logic can remain private, while data availability and protocol commitments are designed to remain publicly verifiable. Until now, these markets faced a forced tradeoff: either make data fully public and expose strategies, positions, an counterparties OR hide data offchain and …
Celestia Vision 2.0: every market onchain 0. TL;DR ● Mission: Build blockspace products that let high-volume markets come onchain. ● Vision: Every market in the world trades on open infrastructure, with permissionless read and write access to every orderbook. ● Principle: Social consensus is the final layer. Celestia provides infrastructure for markets that are fast enough for machines, but governable enough for h…
Channel photo updated
Introducing Fibre: 1Tb/s of blockspace Celestia Fibre pushes the industry into the post-throughput era. ➡️ 10KB/s enabled AMMs. ➡️ 10MB/s enabled CLOBs. ➡️ 1Tb/s is the leap that will enable every market - roughly 1 transaction per second for every human on earth. At the core of Fibre is a new ultra-fast data availability (DA) encoding protocol, based on ZODA. The encoding protocol provides an alternative to KZG c…
𝗧𝗵𝗲 𝗠𝗮𝘁𝗰𝗵𝗮 𝘂𝗽𝗴𝗿𝗮𝗱𝗲 𝗶𝘀 𝗻𝗼𝘄 𝗹𝗶𝘃𝗲 𝗼𝗻 𝗠𝗮𝗶𝗻𝗻𝗲𝘁 - halving inflation, allowing assets from anywhere to be bridged to Celestia, and enabling up to 128MB blocks https://x.com/celestia/status/1992975440898621475?t=Ax3aaRLedCYm1COXMsBGWw&s=19
Matcha 🍵 is now live on Mocha testnet. Matcha ships performance and economic upgrades. - Unlocks scaling to 128MB blocks ⬆️ - 50% less inflation ✅ - Bridge ⏩ any asset Everything about Matcha, explained here: https://blog.celestia.org/matcha/
Celestia’s v6 upgrade, Matcha 🍵 Now live on Arabica testnet! Matcha, the biggest upgrade yet, enables scaling to 128MB blocks and cuts inflation by 50%. Read more about the Matcha upgrade👇 https://x.com/celestia/status/1965445905106305089
New Celestia Instagram account just dropped 👀 Follow ➡️ instagram.com/celestiaorg
Celestia core devs have patched two network issues: the inability to claim rewards after moving stake, and broken ICA functionality (often used by liquid staking protocols). The patches will be tested and included as part of the upcoming v6 Mainnet upgrade. Wallet providers have been informed of a workaround for the rewards claim issue in the interim. https://x.com/celestia/status/1955696105762734346?t=HlHhJPHIKBXCs…
Showing the 12 most recent of 20 posts we hold for @CelestiaOrg. 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 — 203,103 of 1,189,255entries 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 6 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.
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.
“Celestia Announcements” (@CelestiaOrg), 1,520 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/CelestiaOrg.
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.