Channel
@liquid
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
495subscribers
+12 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001238056703 |
|---|---|
| Type | Channel |
| Username | @liquid |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 20 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 20 August 2026 |
| On Telegram | t.me/liquid |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 20 Aug 2026, 21:25 | 495 | +5 |
| 14 Aug 2026, 21:37 | 490 | +6 |
| 7 Aug 2026, 19:01 | 484 | +1 |
| 7 Aug 2026, 00:03 | 483 | no change |
| 6 Aug 2026, 23:48 | 483 | first reading |
20 posts held, back to 20 March 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 25 July 2026. An engagement rate over an empty window would be a number about nothing.
141 reactions across 20 posts, in 13 distinct kinds. The most used accounts for 39.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 56 | 39.7% | |
| 👍 | 34 | 24.1% | |
| ❤ | 32 | 22.7% | |
| 👏 | 3 | 2.13% | |
| 🤮 | 3 | 2.13% | |
| 👎 | 2 | 1.42% | |
| 💩 | 2 | 1.42% | |
| 😁 | 2 | 1.42% | |
| 🤪 | 2 | 1.42% | |
| 🥴 | 2 | 1.42% | |
| 😍 | 1 | 0.709% | |
| 🤝 | 1 | 0.709% | |
| 🥰 | 1 | 0.709% |
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 20 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 141reactions 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 20 March 2025 to 25 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.
Dear Liquid community, On Monday, Liquid functionaries plan to activate a Dynamic Federations (DynaFed) transition as part of ongoing HSM upgrade work. Following the transition, Liquid’s new proof-of-reserves address will be: bc1qdlld6antmv4xug242ed83q7k4rqw50cwfns38szx4qu2f4jwaxxsuhwxxr The team maintaining liquid.network (Mempool) has also been notified so that its proof-of-reserves display can be updated accord…
❤2👍2
New zero-confirmation (0-conf) infrastructure is now available, giving enterprises near-instant, privacy-preserving acceptance flows on Liquid. It’s part of Liquid’s 2026 roadmap, alongside a quantum-ready testnet and BitVM whitepaper by year-end. https://blog.liquid.net/0-conf-for-elements-and-liquid-a-technical-explainer/
❤7
Simplicity, Liquid’s high-assurance smart contracting language, has a newly redesigned documentation site with more example apps and tutorials, including a testable lending contract that lets users borrow against assets such as LBTC and USDT. Explore yourself! https://simplicity-lang.org/simplicity-apps
🔥8
Activation complete. ✅ ELIP 203 is now live on Liquid, removing the issuance cap for non-LBTC assets and unlocking better UX for large-scale tokenization. Mainnet proof. 👇 https://blockstream.info/liquid/tx/6c3be5b2dff1ab1a65586bc572a48daa00e6c3acba415cfbb4df5e0c17c4dae2?expand First major upgrade shipped. Next up: 0-conf by end of June. ⏱️ Full 2026-2027 roadmap details below. 🌊 👀 https://blog.liquid.net/blocks…
👍5👎1
Attention Liquid community! A reminder before Monday's scheduled network upgrade to update your nodes to at least 23.3.1 to avoid any disruptions. Releases: https://github.com/ElementsProject/elements/releases Any questions, please don't hesitate to comment. Enjoy the weekend!
👎1
Attention node runners! This is a reminder to update your Elements nodes to at least v23.3.1 ahead of the scheduled activation of ELIP 203 on Monday, June 1, 2026. Releases: https://github.com/ElementsProject/elements/releases As outlined in the recent Liquid roadmap update, ELIP 203 removes the inherited 21M issuance cap for non-LBTC assets, an important UX upgrade for tokenization on Liquid. ELIP 203 details: h…
🔥3
ICYMI: Blockstream shares an update on Liquid’s development roadmap. - Major Elements updates, including 0-conf, UPP and cont. Bitcoin Core parity - PQ readiness and a planned quantum-ready testnet by EOY - BitVM-style 1-of-n bridge research and whitepaper - Simplicity-based oracle, DEX and other DeFi infrastructure - Extending Lightning support for the Liquid Wallet Kit (LWK) - Institutional custody and improved to…
🔥1
All-time high transaction volume. $5 billion in RWA TVL. 87 Federation members. Get the quick download on the latest Liquid ecosystem updates in the new quarterly report. https://blog.liquid.net/liquid-federation-quarterly-update-q1-2026/
❤2👏2
Blockstream has just released Simplex, a Rust-based developer framework for Simplicity smart contracts, aimed at providing a rich suite of tools for implementing, testing and deploying contracts on Liquid. * CLI for managing Simplicity-based projects. * SDK with essential Simplicity utilities. * Liquid regtest for local integration testing. * Extensive framework configuration. Start building with expressive, high-a…
❤6👍1
Dear Liquid community, a reminder to update your nodes to the latest Elements release, 23.3.2. This update ensures the smoothest experience when building with Simplicity smart contracts and includes several upstream patches from Bitcoin Core. Onward! https://github.com/ElementsProject/elements/releases
👍6
The Liquid Federation is excited to welcome seven new member companies: Cowbolt, Eulen, illuminodes, Mooze, OrderMoon, Sorted Wallet, and SOUSTA, bringing total Federation membership to 87. Together, they represent a meaningful expansion in both where Liquid is being deployed and how it is being used. The new members broaden Liquid’s usage across three distinct sectors: everyday payments, decentralized protocols and…
🔥12👍1🤝1🥰1😍1
The Liquid Developer Bootcamp world tour expands. 🌎 Next stop: Mexico City (Oct 29-30), followed by São Paulo (Nov 3-4), including a Simplicity hackathon with $6k in BTC for winning teams! Free to attend! Sign up at http://liquid.net/bootcamp now!
❤1
Showing the 12 most recent of 20 posts we hold for @liquid. 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 — 1,126,193 of 1,603,893entries 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 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.
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.
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 20 August 2026 — this entry's latest reading, not the date you are reading this.
“Liquid” (@liquid), 495 subscribers as measured 20 August 2026. Telegram Register, tgregister.com/channel/liquid.
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.