Channel
@thornode_ann
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Citations · Cite this entry
270subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001242988667 |
|---|---|
| Type | Channel |
| Username | @thornode_ann |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 3 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 3 times, most recently 3 September 2026 |
| On Telegram | t.me/thornode_ann |
Crypto & trading — 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 89% 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.
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.
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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @thorchain/99218 May 2026, 21:03 UTC | @thornode_ann/680 · this entry18 May 2026, 21:07 UTC | 1.00 | 4 minutes |
| @thorchain/9974 Jun 2026, 23:41 UTC | @thornode_ann/685 · this entry4 Jun 2026, 23:50 UTC | 1.00 | 9 minutes |
| @thornode_ann/689 · this entry21 Jun 2026, 10:28 UTC | @thorchain/100121 Jun 2026, 10:36 UTC | 1.00 | 8 minutes |
| @thornode_ann/690 · this entry21 Jun 2026, 10:45 UTC | @thorchain/100221 Jun 2026, 10:50 UTC | 1.00 | 5 minutes |
| @thornode_ann/693 · this entry23 Jun 2026, 19:42 UTC | @thorchain/100523 Jun 2026, 19:49 UTC | 1.00 | 7 minutes |
| @thornode_ann/694 · this entry25 Jun 2026, 01:40 UTC | @thorchain/100625 Jun 2026, 01:47 UTC | 1.00 | 7 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @thorchain | 19 (8/8 hand-verifiable sample passed) | 1.00 | 7 minutes | this entry (11–8) |
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 8 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 May 2026 to 27 July 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.
Across the whole group of 2, the earliest publisher we hold is @thorchain. 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.
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 |
|---|---|---|
| 21 Aug 2026, 15:58 | 270 | -1 |
| 13 Aug 2026, 16:08 | 271 | +1 |
| 7 Aug 2026, 00:17 | 270 | no change |
| 6 Aug 2026, 17:56 | 270 | first reading |
20 posts held, back to 18 May 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 27 July 2026. An engagement rate over an empty window would be a number about nothing.
New Discord Announcement from THORChain Devs #🚨thornode-mainnet 🗳️ Node Vote Reminder: ADR-029 Reminder to vote on ADR-029, we currently have 48% of the notes voting and need another 20ish votes to pass rev-share. ``` make mimir Key: ADR029 Values: * 1 = Vote For * 0 = Vote Against ```
New Discord Announcement from THORChain Devs #🚨thornode-mainnet ## Mimir Vote Request: `STREAMINGLIMITSWAPMAXAGE = 5256000` Requesting **3 node operators** to cast an operational Mimir vote. | Field | Value | |---|---| | **Key** | `STREAMINGLIMITSWAPMAXAGE` | | **New value** | `5256000` (~1 year) | | **Current default** | `43200` (~3 days) | | **Votes needed** | 3 (`OperationalVotesMin`) | ### What it does Raise…
New Discord Announcement from THORChain Devs #🚨thornode-mainnet # 📢 Dynamic Fee Experiment Update & Expansion I know we've had several announcements like this recently. We don't want to create churn for the community or node operators, but there has been a lot happening lately—which is both exciting and, at times, operationally challenging. I wanted to provide a quick update on the Symbiosis experiment and announc…
New Discord Announcement from THORChain Devs #🚨thornode-mainnet # THORNODE ❗ MAINNET ❗ BASE daemon — v1.1.1 (fork) **NETWORK:** MAINNET **TYPE:** Non-coordinated **URGENCY:** ASAP base-daemon is updated to **v1.1.1**. If you self-host a BASE daemon, pull node-launcher and redeploy: ``` make pull make install ``` Base hardforked at L2 block **47806543** (~16:00 UTC today). Daemons not on v1.1.1 stall at that bloc…
New Discord Announcement from THORChain Devs #🚨thornode-mainnet ## MIMIR VOTE — UNHALT TCY CLAIMING **NETWORK:** MAINNET **TYPE:** Coordinated (mimir vote) **URGENCY:** ASAP TCY claiming has been halted (`TCYCLAIMINGHALT=1`) since the claiming fix landed; that patch has been live on mainnet since v3.18.0 (current mainnet 3.19.1), so claiming can safely resume. Vote to clear the halt: ``` make mimir ``` key: `TCYC…
New Discord Announcement from THORChain Devs #🚨thornode-mainnet ## DISABLE BIFROST KEYVERIFY **NETWORK:** MAINNET **TYPE:** Non-coordinated **URGENCY:** ASAP ECDSA migration is complete — bifrost keyverify is no longer needed, and leaving it on only makes nodes periodically drop availability (~every 10 min) and risk extra slashing. Node-launcher now disables it by default; please pull the latest and redeploy to pi…
New Discord Announcement from THORChain Devs #🚨thornode-mainnet # THORNODE ❗ MAINNET ❗ MIMIR VOTE — UN-HALT GLOBAL TRADING **NETWORK:** MAINNET **TYPE:** Coordinated (mimir vote) **URGENCY:** ASAP Next recovery step — re-opening global trading. All per-chain trading halts are already 0, and secured + trade assets are enabled; the only remaining gate is the global HALTTRADING. Vote it to 0 to reopen swaps. ``` mak…
New Discord Announcement from THORChain Devs #🚨thornode-mainnet # THORNODE ❗ MAINNET ❗ MIMIR VOTE — UN-HALT SECURED + ENABLE TRADE ASSETS **NETWORK:** MAINNET **TYPE:** Coordinated (operational mimir vote) **URGENCY:** ASAP Recovery step — re-opening secured-asset and trade-asset trading. ``` make mimir ``` key: `HALTSECUREDGLOBAL` value: `0` key: `TRADEACCOUNTSENABLED` value: `1` Both are operational mimirs —…
New Discord Announcement from THORChain Devs #🚨thornode-mainnet # THORNODE ❗ MAINNET ❗ MIMIR VOTE — UNHALT SIGNING (GLOBAL) **NETWORK:** MAINNET **TYPE:** Coordinated **URGENCY:** ASAP The churn has rotated and the retiring vaults need to migrate funds into the new ones — that needs signing back on. Please vote to un-halt global signing. Operational mimir, so only the small quorum (3 nodes) is needed. ``` make mi…
New Discord Announcement from THORChain Devs #🚨thornode-mainnet # THORNODE ❗ MAINNET ❗ SUCESSFUL CHURN - NEED 1 MORE VOTE — HALT CHURNING We're at 2 of 3 operational votes to halt churning for the migration — need one more node to vote: > This is to avoid any clashing while we migrate and test the new TSS changes that have been made ``` make mimir ``` key `HALTCHURNING` value `1` @everyone
New Discord Announcement from THORChain Devs #🚨thornode-mainnet <:alert:1143254456893456485> **THORNode Halted at 3.19.0 Upgrade Height — Action Required (Affected Validators)** **NETWORK:** MAINNET **TYPE:** Per-validator action (non-coordinated) **URGENCY:** ASAP for affected nodes These nodes are dead weight on consensus (network at ~89% signed) and block the recovery plan — keyverify (step 5) and the upcoming…
New Discord Announcement from THORChain Devs #🚨thornode-mainnet # Mimir Vote for Compromised Vault — Active Validators Only Following step three from https://discord.com/channels/838986635756044328/839001804812451873/1512583315339739257 we now need to vote to disable the compromised vault. ``` ❯ make mimir => Enter THORNode Mimir key: ``` Enter the value ``` CompromisedVault-thorpub1addwnpepqvpnhwzqkd2zqkxsj272fa…
Showing the 12 most recent of 20 posts we hold for @thornode_ann. 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.
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 21 August 2026 — this entry's latest reading, not the date you are reading this.
“THORNode Announcements” (@thornode_ann), 270 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/thornode_ann.
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.