Telegram RegisterThe public register of Telegram
Telegram profile photo for LiquidLaunch Alerts

Channel

LiquidLaunch Alerts

@liquidlaunchalerts

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Posts · Citations · Cite this entry

1,006subscribers

-33 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002338343645
TypeChannel
Username@liquidlaunchalerts
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live8 November 2026
Measurements held23
Confirmed unchanged2 times, most recently 8 November 2026
On Telegramt.me/liquidlaunchalerts

Topic

Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 19 September 2026 and assigned it the closest of 31 fixed categories, at 96% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@liquidlaunchalerts/3394 · this entry25 Jun 2026, 18:32 UTC@launchallerts/48525 Jun 2026, 18:48 UTC1.0016 minutes
@liquidlaunchalerts/3397 · this entry29 Jun 2026, 11:08 UTC@launchallerts/48829 Jun 2026, 11:23 UTC1.0015 minutes
@liquidlaunchalerts/3398 · this entry30 Jun 2026, 03:58 UTC@launchallerts/48930 Jun 2026, 03:58 UTC1.00under a minute
@liquidlaunchalerts/3400 · this entry30 Jun 2026, 14:52 UTC@launchallerts/49130 Jun 2026, 14:58 UTC1.005 minutes
@liquidlaunchalerts/3406 · this entry10 Jul 2026, 15:02 UTC@launchallerts/49710 Jul 2026, 15:19 UTC1.0017 minutes
@liquidlaunchalerts/3407 · this entry14 Jul 2026, 01:29 UTC@launchallerts/49814 Jul 2026, 01:32 UTC1.003 minutes
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@launchallerts19 (8/8 hand-verifiable sample passed)1.0013 minutesthis entry (19–0)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 20 comparable posts for this entry, running 18 June 2026 to 4 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 2 channels, the one whose matching posts we hold earliest is @liquidlaunchalerts — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

1,0061,0391,022.57 August 2026 — 1,039 subscribers7 August 2026 — 1,038 subscribers14 August 2026 — 1,036 subscribers17 August 2026 — 1,034 subscribers20 August 2026 — 1,035 subscribers24 August 2026 — 1,033 subscribers26 August 2026 — 1,032 subscribers30 August 2026 — 1,030 subscribers1 September 2026 — 1,028 subscribers6 September 2026 — 1,025 subscribers11 September 2026 — 1,021 subscribers14 September 2026 — 1,020 subscribers19 September 2026 — 1,018 subscribers28 September 2026 — 1,017 subscribers5 October 2026 — 1,010 subscribers12 October 2026 — 1,007 subscribers15 October 2026 — 1,008 subscribers19 October 2026 — 1,007 subscribers22 October 2026 — 1,008 subscribers24 October 2026 — 1,007 subscribers28 October 2026 — 1,008 subscribers2 November 2026 — 1,007 subscribers5 November 2026 — 1,006 subscribers7 August 20265 November 2026
23 measurements spanning 90 days, net -33. 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 1,001–1,044 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 23
Measured (UTC)SubscribersChange
5 Nov 2026, 10:491,006-1
2 Nov 2026, 16:091,007-1
28 Oct 2026, 01:591,008+1
24 Oct 2026, 19:581,007-1
22 Oct 2026, 02:281,008+1
19 Oct 2026, 05:081,007-1
15 Oct 2026, 23:271,008+1
12 Oct 2026, 17:591,007-3
5 Oct 2026, 21:371,010-7
28 Sept 2026, 09:351,017-1
19 Sept 2026, 00:001,018-2
14 Sept 2026, 10:361,020-1
11 Sept 2026, 06:591,021-4
6 Sept 2026, 00:571,025-3
1 Sept 2026, 18:241,028-2
30 Aug 2026, 04:041,030-2
26 Aug 2026, 17:161,032-1
24 Aug 2026, 02:051,033-2
20 Aug 2026, 18:141,035+1
17 Aug 2026, 19:531,034first reading

Engagement

20 posts held, back to 18 June 2026 — 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 page of 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 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

4 Aug 2026, 05:42 UTC42 viewsread 7 August 2026
Photo

$MORPHO 🧩 Deployer supply 🧩 ┝ 💰 Amount: 0.00 (0.00%) ┕ 💸 Worth: 0.00 HYPE 🦄 Token 🦄 ┝ Morphoe ┕ Mor(pho)e to do on the HyperEVM. 📍 Addresses 📍 ┝ 😎 Deployer: 0x8f71119a38e218A5aBff2E435aD159243a21E9df ┕ 🌈 Token: 0x9F35734d30bcD3982cf7622468547ef879EF61A5

27 Jul 2026, 15:38 UTC61 viewsread 7 August 2026

$SLH 🧩 Deployer supply 🧩 ┝ 💰 Amount: 0.00 (0.00%) ┕ 💸 Worth: 0.00 HYPE 🦄 Token 🦄 ┕ Slush 📍 Addresses 📍 ┝ 😎 Deployer: 0x9bbCb5167bFfd0Dd3F6712a5bC51A8036AA31836 ┕ 🌈 Token: 0xd8121De527fCB01AA1a481f88132b9a94a55562D

22 Jul 2026, 19:30 UTC79 viewsread 7 August 2026

$GNZ 🧩 Deployer supply 🧩 ┝ 💰 Amount: 0.00 (0.00%) ┕ 💸 Worth: 0.00 HYPE 🦄 Token 🦄 ┝ GAINZ ┕ GAINZ 📍 Addresses 📍 ┝ 😎 Deployer: 0xF9b8946f8D8970451cdB9d6A1d08B0a7B2f11F4A ┕ 🌈 Token: 0x922Ee16e6B56F305aCFb0c4e3B83Fa03d57B7E01

14 Jul 2026, 01:29 UTC93 viewsread 7 August 2026
Photo

$BUDDY 🧩 Deployer supply 🧩 ┝ 💰 Amount: 92.39K (0.01%) ┕ 💸 Worth: 0.03 HYPE ($1.74) 🦄 Token 🦄 ┝ ProjectXBuddy ┕ The mascot token of the Project X ecosystem on HyperEVM 📍 Addresses 📍 ┝ 😎 Deployer: 0x3032C9A6De0C87aEc1a272911Ba1f5897609882B ┕ 🌈 Token: 0xE8d89D2B3028ed224b5908eADBc36E9D272037Ea

10 Jul 2026, 15:02 UTC76 viewsread 7 August 2026

$FRA 🧩 Deployer supply 🧩 ┝ 💰 Amount: 0.00 (0.00%) ┕ 💸 Worth: 0.00 HYPE 🦄 Token 🦄 ┝ France ┕ Mbape 📍 Addresses 📍 ┝ 😎 Deployer: 0x247f2f8C53460D9d168Acd1aFFf3B437396bf454 ┕ 🌈 Token: 0x724DF2e35C70B4749A1a83179c1a5254288C0917

7 Jul 2026, 19:19 UTC67 viewsread 7 August 2026
Photo

$SENPI 🧩 Deployer supply 🧩 ┝ 💰 Amount: 8.64M (0.86%) ┕ 💸 Worth: 2.59 HYPE ($180.78) 🦄 Token 🦄 ┝ Senpi ┕ AI that runs your Hyperliquid strategy while you sleep. Powered by Senpi Samurai, the Hyperliquid AI. 📍 Addresses 📍 ┝ 😎 Deployer: 0xFC6D950c2B3441e5b2Adb08b00cb03cEd9f136BD ┕ 🌈 Token: 0xc6d6233a4271f32b338D7772B18b0ebd5960785B

5 Jul 2026, 08:40 UTC67 viewsread 7 August 2026

$Jeff 🧩 Deployer supply 🧩 ┝ 💰 Amount: 0.00 (0.00%) ┕ 💸 Worth: 0.00 HYPE 🦄 Token 🦄 ┕ The HYPE Bull 📍 Addresses 📍 ┝ 😎 Deployer: 0x9A04f5eDF3e9574c59e368c39926cC25605151F3 ┕ 🌈 Token: 0x1669b737f7Ab13AA98c4d72Dbb4c646b8dBf499f

5 Jul 2026, 06:03 UTC57 viewsread 7 August 2026
Photo

$EASY 🧩 Deployer supply 🧩 ┝ 💰 Amount: 9.48M (0.95%) ┕ 💸 Worth: 2.84 HYPE ($194.24) 🦄 Token 🦄 ┝ HyperEasy ┕ The missing UX layer for the Hyperliquid ecosystem. 📍 Addresses 📍 ┝ 😎 Deployer: 0x4Ad8163a515D34876E343bbd610F8F3f81473AF7 ┕ 🌈 Token: 0x1040fE6489d13af0139C15b026158E9f0b0D0EDe

3 Jul 2026, 11:50 UTC43 viewsread 7 August 2026

$WCP 🧩 Deployer supply 🧩 ┝ 💰 Amount: 0.00 (0.00%) ┕ 💸 Worth: 0.00 HYPE 🦄 Token 🦄 ┝ World Cup ┕ World cup 📍 Addresses 📍 ┝ 😎 Deployer: 0x0ec19CC29389D029C7C7D77b6b23bf966eF97619 ┕ 🌈 Token: 0xfdA2D77FF2fb1c2D75d38c9caa53A9f2eb044670

2 Jul 2026, 18:40 UTC47 viewsread 7 August 2026

$MBAP 🧩 Deployer supply 🧩 ┝ 💰 Amount: 0.00 (0.00%) ┕ 💸 Worth: 0.00 HYPE 🦄 Token 🦄 ┕ Mbappe 📍 Addresses 📍 ┝ 😎 Deployer: 0xdBCa5C5A784Bc93b508126fac5FC6eC5133D2e0e ┕ 🌈 Token: 0xe8751Ad32A75ba8D7A3cFB1Aae6FB71dD9C7a1f6

30 Jun 2026, 14:52 UTC45 viewsread 7 August 2026
Photo

$HPAD 🧩 Deployer supply 🧩 ┝ 💰 Amount: 857.26K (0.09%) ┕ 💸 Worth: 0.25 HYPE ($16.55) 🦄 Token 🦄 ┝ Hyperpad ┕ A Hybrid Launchpad on @HyperLiquidX 📍 Addresses 📍 ┝ 😎 Deployer: 0xEFEc02c4b9353764F8bFBD801EA957293f0aB5Fd ┕ 🌈 Token: 0xe902c1202308cc92c0e9Cdf19f8dD6B7A428d94B

30 Jun 2026, 10:23 UTC40 viewsread 7 August 2026
Photo

$HYDE 🧩 Deployer supply 🧩 ┝ 💰 Amount: 956.09K (0.10%) ┕ 💸 Worth: 0.28 HYPE ($18.57) 🦄 Token 🦄 ┝ hyde ┕ A social layer on top of Hyperliquid Copy Traders. Predict Outcomes. Launch Coins. 📍 Addresses 📍 ┝ 😎 Deployer: 0x54872297D66318e00cE9FB15400037121Eb67B06 ┕ 🌈 Token: 0x1FABE6438265a9EEb8AB64714f7Db11F32Fc8256

Showing the 12 most recent of 20 posts we hold for @liquidlaunchalerts. 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.

Mentions

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.

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

“LiquidLaunch Alerts” (@liquidlaunchalerts), 1,006 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/liquidlaunchalerts.

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.