Channel
@metahash
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
403subscribers
-3 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001118041740 |
|---|---|
| Type | Channel |
| Username | @metahash |
| Created | Between 1 February 2017 and 30 November 2019 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 8 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 8 October 2026 |
| On Telegram | t.me/metahash |
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 22 September 2026 and assigned it the closest of 31 fixed categories, at 87% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Oct 2026, 06:38 | 403 | -1 |
| 28 Sept 2026, 03:39 | 404 | +1 |
| 15 Sept 2026, 03:21 | 403 | +1 |
| 8 Sept 2026, 10:59 | 402 | -1 |
| 22 Aug 2026, 06:36 | 403 | -1 |
| 15 Aug 2026, 00:36 | 404 | -2 |
| 6 Aug 2026, 19:33 | 406 | no change |
| 6 Aug 2026, 02:30 | 406 | first reading |
20 posts held, back to 6 May 2022 — 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 28 December 2022. An engagement rate over an empty window would be a number about nothing.
Hi all! We invite you to join #MetaBridge testing! It becomes available with the new #MetaHashGate version. But be careful: - Service is in a test mode - Testing may be completed at any time. No compensation is provided for in this case - Do not exchange large amounts until testing is completed Instruction - https://metahash.readme.io/docs/metabridge Let's start right now!
No more words, it's a new #MetaHashGate version! Upgrade it to enjoy SMART TOKENS! Find instructions here - https://metahash.readme.io/docs/smart-tokens-on-the-tracechain-base
Please note that Torrents older than the 0.149 version no longer pass tests. This means that such nodes will not be rewarded tomorrow. Update your nodes as soon as possible - https://github.com/metahashorg/Node-Torrent/releases/tag/v6.0
Friends, some of you wonder why unupdated Torrents still receive awards. Since the deadline was pretty short, we decided to add a few-days delay. We will let you know when the changes finally take effect. In the meantime, please update your nodes —https://github.com/metahashorg/Node-Torrent/releases/tag/v6.0 Thanks!
#MHC deposit/withdrawal are restarted on KuCoin If you have any questions about depositing or withdrawing funds, don't hesitate to contact the chat admins @vinnythe and @maxwe1fox. https://www.kucoin.com/news/en-kucoin-opens-mainnet-mhc-tokens-deposit-and-withdrawal-services-20220922
Time to update your Torrent nodes! Starting next Monday (26.09) all Service Torrent nodes must be no older than version 0.149 (v6.0) to pass tests and receive rewards. In the meantime, we're working on the overall stability of the network to make the next major releases as smooth and secure as possible.
#MetaHash secures Internet 🌐 Use #MetaHashGate, share your experiences and wishes — we're building a decentralized Internet together! ⚡️Join our Community Chat! -> @metahash_eng⚡️ Follow the link attached to read more -> https://link.medium.com/R1jmKMsrfsb
Project progress 19.07.2022 📲 ⚡️Join our Community Chat! -> @metahash_eng⚡️ Follow the link attached to read more -> https://link.medium.com/mHKBY0gWMrb
Waiting for cryptomorning. Hype cycles ♻️ ⚡️Join our Community Chat! -> @metahash_eng⚡️ Follow the link attached to read more -> https://link.medium.com/CeZvCuv2urb
Project progress 01.07.2022 🪁 ⚡️Join our Community Chat! -> @metahash_eng⚡️ Follow the link attached to read more -> https://link.medium.com/oLTRLujojrb
Cryptocheese in a cryptotrap 🧀 ⚡️Join our Community Chat! -> @metahash_eng⚡️ Follow the link attached to read more -> https://link.medium.com/X8RUVnas7qb
Hi! We're doing maintenance work today, so there may be some network interruptions. Please don't worry and thank you for understanding!
Showing the 12 most recent of 20 posts we hold for @metahash. 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.
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.
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.
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 8 October 2026 — this entry's latest reading, not the date you are reading this.
“#MetaHash News” (@metahash), 403 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/metahash.
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.