Mining 🌟 Starts In… 3 days. YES, you read that right. No, it’s not a hallucination. It’s a timer. THE timer. 🎉 When Acki Nacki sees the world — and the world truly sees Acki Nacki. How will you celebrate? 🥂
🔥3😢2❤1

Channel
@tvm_validators
On this record: Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
848subscribers
-1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001246936843 |
|---|---|
| Type | Channel |
| Username | @tvm_validators |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/tvm_validators |
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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 19:54 | 848 | -1 |
| 6 Aug 2026, 16:35 | 849 | no change |
| 6 Aug 2026, 16:23 | 849 | first reading |
20 posts held, back to 23 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 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 20 September 2025. An engagement rate over an empty window would be a number about nothing.
67 reactions across 17 posts, in 5 distinct kinds. The most used accounts for 70.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 47 | 70.1% | |
| 🔥 | 14 | 20.9% | |
| ❤ | 3 | 4.48% | |
| 😢 | 2 | 2.99% | |
| 👎 | 1 | 1.49% |
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 18 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 67reactions 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 23 May 2022 to 20 September 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Mining 🌟 Starts In… 3 days. YES, you read that right. No, it’s not a hallucination. It’s a timer. THE timer. 🎉 When Acki Nacki sees the world — and the world truly sees Acki Nacki. How will you celebrate? 🥂
🔥3😢2❤1
🏆 To the attention of the Rust Cup winners! ⚠️ Dear winners of the Rust Cup who have not yet received prize lock stakes! Please, replenish balances of the proxy contracts of your DePools by 3 EVER to avoid potential problems at the start of your DePools after a long waiting without validation due to accumulated storage fees in the masterchain.
👍11❤2🔥1
🏆 To the attention of the Rust Cup winners! Please, find below information about the Rust Cup Donor: Address: 0:eabd38806e244f941f0611aef85d8ab06dd9289cb2495153e9561153c08dc4d5 DeName: rustcupdonor.ever
👍5
Public link to instructions: https://docs.google.com/document/d/1IEhVKrd8LtnRS2Np2nNvbxHwZnSYEkQJQHfd749h-fw/edit?usp=sharing
👍2
TVM Validators pinned a photo
🏆 To the attention of the Rust Cup winners! The payout team process all your confirmations required by the instructions in the Rust Cup Payout Registry where you can track your status. Please take into account that processing of a large number of messages takes some time. If you don't see a change in status after 24 hours of sending the message, repeat the message.
👍1👎1
‼️ Attention! A new proposal for RUSTCUP has been developed ‼️ Read carefully and express your opinions and wishes! https://docs.google.com/document/d/1Et5cvPxKN_BPR2uCqkpYWG4Oun_23nsQlIugCPm4cyk/edit#
🔥2
#evernode_update #evernode_changelog Commit ID: a67e970ae133bbffe1b42db23efb45b5b964bda9 Node Version: 0.51.34 Tools version: 0.1.300 Block version: 35 1. Build node. 2. Restart the node 🛠Changelog node from 0.51.25 to 0.51.34 🔹 add optional feature "signature_with_id" 🔹 few updates for slashing (feature is off now) 🔹 fix bug: CapStcontNewFormat, CapFastStorageStatBugfix, CapResolveMerkleCell can't enabled 🔹 maste…
‼️ ATTENTION ‼️ ‼️ Up to 30% of nodes in the network have not been updated yet ‼️ Because of this, the shard in the network periodically stops Anyone who hasn't updated nodes yet should update them!! Update process: - update the node from the master, and make sure it matches TON Node, version 0.51.25 Rust: rustc 1.65.0 (897e37553 2022-11-02) TON NODE git commit: e6820018e1170f6f7baec66931229ebb4a55eba8 ADNL git co…
👍6
#evernode_update #evernode_changelog Commit ID: b621e417bea9661cdc638a56106795d0f2994502 Node Version: 0.51.14 Tools version: 0.1.297 Block version: 33 1. Build node. 2. Restart the node 🛠Changelog node from 0.51.1to 0.51.14 🔹 sha2 package Updated to 0.10 🔹 statsd package Updated to 0.15 🔹 recomended rust up to 1.65.0 🔹 clean unapplied blocks every 15 seconds 🔹 remove unapplied files from storage 🔹 publish script …
👍2
Bindings support voting Ever-sdk bindings are important components of Everscale dev ecosystem. Please, support this voting to help us continue the maintaining the bindings. The voting will take place until the end of sunday 27.11.2022. Follow the link to read and vote for the proposal -> https://everdao.net/governance/proposals/98
🔥2
🪙Token API in available in Evercloud! 🪙 ft root type is API that provides data about fungible tokens, transfers, holders. Try it now! query{ ft{ holder(address:"0:3666ef0af863317eafcea173b9a9fdd6d1e4aa6dd080a1f472b2ad217215e5c9"){ address wallets(first:2){ edges{ node{ address balance token{ symbol } percenta…
👍7
Showing the 12 most recent of 20 posts we hold for @tvm_validators. 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 — 998,645 of 1,340,412entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“TVM Validators” (@tvm_validators), 848 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/tvm_validators.
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.