Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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 why it has no browse page of its own yet.
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 word for word on 1 other registered channel. 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 (1 of the pairs behind the counts below)
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 12 comparable posts for this entry, running 16 September 2024 to 9 June 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).
Across the whole group of 2, the earliest publisher we hold is @CryptominesAnnouncements — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_mutual, last confirmed 7 August 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.
Also posting the same content
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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.
4 measurements spanning 4 days, net -16. 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 7,616–7,636 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
10 Aug 2026, 22:13
7,618
-13
7 Aug 2026, 16:51
7,631
-3
7 Aug 2026, 01:15
7,634
no change
7 Aug 2026, 01:07
7,634
first reading
Engagement
20 posts held, back to 16 September 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 11 pagesof 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 9 June 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Photos
103
Videos
21
Links
237
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Video runtime
3m 25s
Average length
21s
Measured directly from 10 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.
Reaction mix
250 reactions across 14 posts, in 9 distinct kinds. The most used accounts for 52.4% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
131
52.4%
❤
63
25.2%
🤯
28
11.2%
👀
13
5.20%
👍
6
2.40%
🎉
3
1.20%
👏
2
0.8%
🤩
2
0.8%
🥰
2
0.8%
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 14 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 250reactions 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 16 September 2024 to 9 June 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.
Battlefleets have arrived ⚔️
One board. Two Commanders. Only one takes EVERYTHING
Every mission until now was you against the sector. You knew the rules, you knew what to expect. But this is a completely different game.
This time, the danger isn't the environment. It's someone like you. Another real Commander, with a real fleet, reading your moves from the other side of the grid. Your strategy against theirs.
You…
🛠 UPDATE 05/05 — More Control
Commanders.
A new operation has been added, alongside a new feature. Both come directly from your feedback, and both are built around the same idea.
More control, fewer nodes, more runs.
🚀 Quick Expeditions — Same Frontier, no waiting
A lot of you wanted to run more, faster, without the node-by-node flow slowing things down between attempts.
Quick Expeditions are exactly that, sam…
🛠 UPDATE 24/04 — Pancho's Blessing
Commanders.
We spent the last weeks watching every expedition. Reading every message. Running the numbers on thousands of runs. You've been clear: the Frontier should feel fair. It should feel like it wants to reward the risk you take, not punish you for taking it.
So we tuned it.
Every change in this patch tips the scales in your favor, more cargo coming out, less friction goin…
THANK YOU, COMMANDERS! 🚀
CryptoMines Relive - News
Day one was a success and the response was clear: the Relive universe is more alive than ever. The gates are open, but those who know Pancho know this is just the beginning.
Tonight, the silence of space breaks with the first Midnight Bell 🔔
⚡️ The Boost: 1.5x rewards
⏳ The Window: Only 30 minutes (00:00 UTC)
💰 The Loot: 50,000 Cargo ($5,000 USDC) up for grabs…
WE'RE HERE! 🚀
We didn't come to watch, we came to conquer the network.
Do you have what it takes to dominate the next sector? Every extraction is a decision that's yours alone.
🌐 Play Now: https://cryptomines.app
New here? Don't go in blind, check the Core Loop:
👉 https://docs.cryptomines.app/gameplay/core-loop/
Stay close, Commander. Glory doesn't wait 🖖
The wait is over. Wednesday, April 15. 🚀
CryptoMines: Relive goes live. Log in, build your fleet and deploy.
Every extraction is a decision. Push forward or retreat. Come back loaded or come back with nothing. That’s Risk to Earn.
🌐 Network: BASE (USDC deposits only, multi-chain coming soon)
For the veterans who kept the faith through the dark sectors, it's time to secure your position.
Legacy, Reborn and Valiant…
When everything went dark, Pancho didn't shut down.
He built the Relive Protocol.
CryptoMines: Relive launches in the upcoming days. The grids are waking up. The hypergates are unlocking.
Push forward or risk it all. Every expedition, the same question.
That's Risk to Earn.
Know the protocol before launch 👉 docs.cryptomines.app
Stay close, Commanders 🖖
🚀 CryptoMines: Relive is about to launch.
In the upcoming days we will reveal: Trailer, documentation and much more! 🔥
Don’t miss any updates. Join the official Vortrius community to stay tuned for upcoming launch dates and news.
All announcements will be posted first on:
📢 Telegram Announcements: https://t.me/Vortrius
👾 Discord: https://discord.gg/Vortrius
🌍 We're all over the world. Find your people:
🌐 English…
❤14🔥5🤯4
Showing the 12 most recent of 20 posts we hold for @CryptominesAnnouncements. 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 — 41,727 of 1,151,006entries 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
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.
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 10 August 2026 — this
entry's latest reading, not the date you are reading this.
“CryptoMines - Announcements” (@CryptominesAnnouncements), 7,618 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/CryptominesAnnouncements.
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.
