Web appOpen in Telegram
LLiquid
Liquid
@liquid · channel · Crypto · indexed since 2026-07-04 Statistics

Statistics of the channel “Liquid”

Active channel: 6 posts in the index in 30 days, reach ≈237% of the audience, growing 4% a week, cited by 4 venues in 30 days.
546subscribers±0 in a day · +21 in a week
6posts in 30 days
1,292average post reach
237%ER — reach to subscribers
46post forwards in 30 days
4venues cited it in 30 days11 all time
91posts in the index102 total in Telegram
2020-09-02first post
#333 501catalog rank#11 424 in topic · #26 216 in language

Subscribers 546

history since 2026-09-29
2026-09-292026-10-08

Audience checkhow we check

Not enough data to checkFewer than 1,000 subscribers — too small to judge

Posts per day

max 2
2026-07-112026-10-08

Average post reach by day

max 1,926
2026-07-112026-10-08

When it posts (UTC, 90 days)

036912151821MoTuWeThFrSaSu

What it posts (90 days)

text56%
links44%

Top posts in 30 days

LIQUID NETWORK UPDATE: INCIDENT REPORT Status as of September 8, 2026, 19:10 UTC What Happened? On September 6, 2026 at 15:53:10 UTC (Liquid block 4,050,336), a vulnerability in the open-source Elements software relate1,846 views · 18 forwards · 2026-09-08 19:22 UTCLIQUID NETWORK UPDATE: OPERATIONS RESUMED, RECOVERY ONGOING Status as of September 10, 2026, 10:00 UTC Recovery Status The Liquid Network has entered the next phase of its controlled resumption. As a precautionary meas1,587 views · 5 forwards · 2026-09-10 15:25 UTCLIQUID NETWORK UPDATE: ECOSYSTEM ACTIVITY Status as of September 17, 2026, 21:05 UTC Network and Ecosystem Status Since resuming on September 10, block production and network transactions, including LBTC transfers, hav1,563 views · 13 forwards · 2026-09-17 21:25 UTCLIQUID NETWORK UPDATE: TRANSACTIONS RESUMED, PEG-OUTS DISABLED Status as of September 10, 2026, 19:55 UTC Recovery Status The Liquid Network has entered into its next recovery phase. Block production has resumed, and f1,065 views · 3 forwards · 2026-09-10 20:08 UTCLIQUID NETWORK UPDATE: NEW RELEASE Status as of September 9, 2026, 13:10 UTC Update to Elements v23.3.4 The emergency Elements v23.3.4 release is now available. Functionary nodes are being updated immediately and we re1,041 views · 6 forwards · 2026-09-09 14:39 UTCBlockstream’s technical security assessment of the September 6 Liquid incident is now published on the Liquid blog. It covers the exploit’s root cause and mechanics, the incident timeline, and the engineering and securit651 views · 1 forwards · 2026-09-25 02:42 UTC

Most forwarded posts in 30 days

The channel's posts other venues forwarded most; the text comes from the forwarded copies.
LIQUID NETWORK UPDATE: ECOSYSTEM ACTIVITY Status as of September 17, 2026, 21:05 UTC Network and Ecosystem Status Since resuming on September 10, block production and network transactions, including LBTC transfers, havforwarded by 4 venues · 2026-09-17 22:11 UTCLIQUID NETWORK UPDATE: OPERATIONS RESUMED, RECOVERY ONGOING Status as of September 10, 2026, 10:00 UTC Recovery Status The Liquid Network has entered the next phase of its controlled resumption. As a precautionary measforwarded by 3 venues · 2026-09-10 15:26 UTCLIQUID NETWORK UPDATE: INCIDENT REPORT Status as of September 8, 2026, 19:10 UTC What Happened? On September 6, 2026 at 15:53:10 UTC (Liquid block 4,050,336), a vulnerability in the open-source Elements software relateforwarded by 3 venues · 2026-09-08 20:05 UTCLIQUID NETWORK UPDATE: NEW RELEASE Status as of September 9, 2026, 13:10 UTC Update to Elements v23.3.4 The emergency Elements v23.3.4 release is now available. Functionary nodes are being updated immediately and we reforwarded by 2 venues · 2026-09-09 14:40 UTCLIQUID NETWORK UPDATE: TRANSACTIONS RESUMED, PEG-OUTS DISABLED Status as of September 10, 2026, 19:55 UTC Recovery Status The Liquid Network has entered into its next recovery phase. Block production has resumed, and fforwarded by 2 venues · 2026-09-10 20:08 UTCBlockstream’s technical security assessment of the September 6 Liquid incident is now published on the Liquid blog. It covers the exploit’s root cause and mechanics, the incident timeline, and the engineering and securitforwarded by 2 venues · 2026-09-25 02:42 UTC

Badge for your website

An image with the venue's fresh numbers linking to its statistics — paste the code into your site or README.

ChatCrawler

Similar venues

catalog data as of 08.10.2026 08:49 UTC · Updated: 2026-10-08 09:30 UTC · How we count →

Whole catalog

An open public feed from the search index ChatCrawler — “Google for public Telegram”; refreshed as the venue is crawled. Times are UTC.

Public content only, official Telegram API. About · FAQ · What we do not do · Remove a page · Catalog · Search · How we count