31 Dec 2024, 18:46 UTC370 viewsread 9 August 2026
📣 Important news. ⚡️ Everscale devnet had been restarted with Global network Id -42. SignatureWithId capability was enabled
Channel
Evernode update info
@evernode
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
83subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001740956258 |
|---|---|
| Type | Channel |
| Username | @evernode |
| Created | Between 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/evernode |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 17:32 | 83 | no change |
| 6 Aug 2026, 16:36 | 83 | first reading |
Engagement
20 posts held, back to 16 April 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 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 31 December 2024. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Links
- 35
Lifetime counters from Telegram’s own channel header, read 9 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.
Reaction mix
30 reactions across 10 posts, in 5 distinct kinds. The most used accounts for 56.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 17 | 56.7% | |
| 🔥 | 10 | 33.3% | |
| ❤ | 1 | 3.33% | |
| 👎 | 1 | 3.33% | |
| 👏 | 1 | 3.33% |
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 11 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 30reactions 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 April 2024 to 31 December 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Recent posts
21 Nov 2024, 11:44 UTC639 views1 reactionsread 9 August 2026
#evernode_update #evernode_changelog Commit ID: 27c40673b15fadabe755aa0c040848f6e346ba28 Node Version: 0.60.11 Block version: 60 📌 Update Instructions 1. Build node. 2. Restart the node 🛠Changelog node from 0.60.7 to 0.60.11 🔹 PR270 (https://github.com/everx-labs/ever-node/pull/270/) SMFT: improvements, fixes, arbitrage ever_abi from 2.7.11 to 2.8.1 🔹 Uint256 type is returned in radix 10 🔹 Address can be set as nu…
❤1
4 Nov 2024, 04:54 UTC583 views0 reactionsread 9 August 2026
📣 Dear validators, update your nodes config! ❗️Important❗️ Disable smft in your node config: set 'smft_disabled' to 'true' like ... "smft_disabled": true, "smft_max_mc_delivery_timeout_ms": null ... Restart your nodes.
24 Oct 2024, 12:08 UTC≈2,640 viewsread 9 August 2026
IMPORTANT! Some nodes in mainnet may have wrong SMFT settings. It is needed to ensure that SMFT settings in your node config (config.json) file look like below: { ... "smft_disabled": false, "smft_max_mc_delivery_timeout_ms": null ... } If your config settings are different, please respond here with your config settings, and then change your settings to the above mentioned one.
11 Oct 2024, 07:48 UTC423 views2 reactionsread 9 August 2026
#evernode_update #evernode_changelog Commit ID: 1953439415d81c6e5035a0e85c72f3ee5b36eb99 Node Version: 0.60.0 Block version: 59 📌 Update Instructions 1. Build node. 2. Restart the node ‼️ IMPORTANT. This release will optimize the database structure, so node update will take significant time (up to several hours). Please update your nodes one by one. Do not update the next node until the previous one has worked succ…
👍2
10 Sept 2024, 04:34 UTC187 views3 reactionsread 9 August 2026
#evernode_update #evernode_changelog Commit ID: 37d828baf2251bb0297f2324f3bec9edafe50fa5 Node Version: 0.59.22 Block version: 58 📌 Update Instructions 1. Build node. 2. Restart the node 🛠Changelog node from 0.59.11 to 0.59.22 🔹 PR262 (https://github.com/everx-labs/ever-node/pull/261/) SMFT stability updates 🔹 PR263 (https://github.com/everx-labs/ever-node/pull/263/) Configure additional SMFT parameters 🔹 PR264 (htt…
👍3
1 Aug 2024, 19:28 UTC519 viewsread 9 August 2026
#evernode_update #evernode_changelog Commit ID: 41b21ba0c44a97b17d4230b107e0192292e0f413 Node Version: 0.59.11 Block version: 57 📌 Update Instructions 1. Build node. 2. Restart the node 🛠Changelog node from 0.59.10 to 0.59.11 🔹 PR260 (https://github.com/everx-labs/ever-node/pull/260/) Fix not found shard while merging
30 Jul 2024, 15:36 UTC166 viewsread 9 August 2026
📣 Important news. ⚡️ Activation of minor changes in the mainnet network. CapDuePaymentFix disabled: Third party services need time to support CapDuePaymentFix.
27 Jul 2024, 07:14 UTC261 viewsread 9 August 2026
📣 Important news. ⚡️ Activation of minor changes in the mainnet network. CapUndeletableAccounts enabled: 🔹 don't delete frozen accounts issue210 ⚠️ No additional actions are required from validators. Your nodes already contain the actual code.
23 Jul 2024, 13:43 UTC268 views1 reactionsread 9 August 2026
📣 Important news. ⚡️ Activation of minor changes in the mainnet network. CapDuePaymentFix enabled: 🔹 disabled due payments on credit phase issue235 🔹 tx.storageFee include due payment value ⚠️ No additional actions are required from validators. Your nodes already contain the actual code.
👏1
23 Jul 2024, 09:55 UTC388 views2 reactionsread 9 August 2026
#evernode_update #evernode_changelog Commit ID: eb074537d868d9feb5acffb3dbb60f55dd2c7982 Node Version: 0.59.10 Block version: 56 📌 Update Instructions 1. Build node. 2. Restart the node 🛠Changelog node from 0.59.7 to 0.59.10 🔹 PR255 (https://github.com/everx-labs/ever-node/pull/255/) Exclude validation of duplicated or non-actual block candidates 🔹 PR258 (https://github.com/everx-labs/ever-node/pull/258/) Support c…
👍1🔥1
10 Jul 2024, 12:45 UTC296 views2 reactionsread 9 August 2026
#evernode_update #evernode_changelog Commit ID: ae08a7c9287b516954e7e67c611345e20bf98f01 Node Version: 0.59.7 Block version: 55 📌 Update Instructions 1. Build node. 2. Restart the node 🛠Changelog node from 0.59.1 to 0.59.7 🔹 PR256 (https://github.com/everx-labs/ever-node/pull/256/) Fixes agains high CPU load with SMFT 🔹 PR257 (https://github.com/everx-labs/ever-node/pull/257/) Fixes agains high CPU load with SMFT, …
👍1🔥1
Showing the 12 most recent of 20 posts we hold for @evernode. 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 — 627,823 of 1,345,403entries 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.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“Evernode update info” (@evernode), 83 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/evernode.
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.