Telegram RegisterThe public register of Telegram

Channel

iToken - Ethereum

@iTokenEthereum

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry

16,511subscribers

-97 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001696523760
TypeChannel
Username@iTokenEthereum
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/iTokenEthereum

Topic

Other / unclassifiable — 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 10 August 2026 and assigned it the closest of 31 fixed categories, at 91% 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 (4 of the pairs behind the counts below)
Posted firstThenOverlapGap
@iTokenVerifiedEthereum/12083622 Jun 2025, 21:59 UTC@iTokenEthereum/1345807 · this entry22 Jun 2025, 21:59 UTC1.00under a minute
@iTokenVerifiedEthereum/12083722 Jun 2025, 21:59 UTC@iTokenEthereum/1345808 · this entry22 Jun 2025, 21:59 UTC1.00under a minute
@iTokenVerifiedEthereum/12083822 Jun 2025, 22:02 UTC@iTokenEthereum/1345812 · this entry22 Jun 2025, 22:02 UTC1.00under a minute
@iTokenVerifiedEthereum/12083922 Jun 2025, 22:06 UTC@iTokenEthereum/1345818 · this entry22 Jun 2025, 22:06 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@iTokenVerifiedEthereum5 (5/5 hand-verifiable sample passed)1.00under a minutethis entry (50)

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 18 comparable posts for this entry, running 22 June 2025 to 22 June 2025. 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 @iTokenEthereum — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 8 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.

Growth

16,51116,60816,559.57 August 2026 — 16,608 subscribers7 August 2026 — 16,595 subscribers8 August 2026 — 16,573 subscribers9 August 2026 — 16,563 subscribers10 August 2026 — 16,549 subscribers11 August 2026 — 16,530 subscribers12 August 2026 — 16,511 subscribers7 August 202612 August 2026
7 measurements spanning 6 days, net -97. 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 16,496–16,623 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 21:2816,511-19
11 Aug 2026, 20:2216,530-19
10 Aug 2026, 19:4116,549-14
9 Aug 2026, 18:4316,563-10
8 Aug 2026, 19:5116,573-22
7 Aug 2026, 17:3716,595-13
7 Aug 2026, 02:4616,608first reading

Engagement

20 posts held, back to 22 June 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 16 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 3 June 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

22 Jun 2025, 22:51 UTC≈11,800 viewsread 12 August 2026
Forwarded from @IndyReviewsPhoto

With regret, iToken has now been shut down until further notice. An updated version is in development, but due to other priorities I cannot be sure when/if it'll be released. Will post here and via iToken channels if anything changes. Over time the system has accurately detected thousands of mid to high severity scams, preventing traders from falling into often devious technical traps. It's also helped traders iden

22 Jun 2025, 22:09 UTC≈8,860 viewsread 12 August 2026
Photo

Launching: SCAI (Scia AI) Scan: ⚠️ code unavailable for auto-analysis. Pair: SCAI / WETH (Uni V2) CA: 0x2E3D340cEdf7C40526f9B68942f4C3201fa8350E Supply: 1,000,000,000 (+9 decimals) 🔗 TG 🤷‍♂️ | Web 🤷‍♂️ | Twitter 🤷‍♂️ | Code | Deployer | Holders 📊 DexT | DexV | Defined | Screener | KibaSwap 🔄 ___________________________________ ☎️ Fitz 🌙 | Vegeta 🥶 | Killer 😈 ___________________________________ 📣 Advertise (iT

22 Jun 2025, 22:08 UTC≈5,460 viewsread 12 August 2026
Photo

Deployed: SCAI (Scia AI) Scan: ⚠️ code unavailable for auto-analysis. CA: 0x2E3D340cEdf7C40526f9B68942f4C3201fa8350E Supply: 1,000,000,000 (+9 decimals) 🔗 Code | Deployer ___________________________________ ☎️ Killer 😈 | Fitz 🌙 | Noodles 🟢 ___________________________________ 📣 Channels (iToken): TG 📣 Advertise (iToken): TG Donate 🪣 | Stay safe 🙏

22 Jun 2025, 22:07 UTC≈3,810 viewsread 12 August 2026
Photo

Locked: D&D (Heroes of DEX and Degens) Scan: ⚠️ code unavailable for auto-analysis. Lock: 100% burned | Verify Pair: D&D / WETH (Uni V2) CA: 0x9032E9efecac73C0C7A77349eB0E98dcE3833a6c Supply: 1,000,000,000 (+9 decimals) 🔗 TG 🤷‍♂️ | Web 🤷‍♂️ | Twitter 🤷‍♂️ | Code | Deployer | Holders 📊 DexT | DexV | Defined | Screener | KibaSwap 🔄 ___________________________________ ☎️ Noodles 🟢 | Brently 🐶 | Joe 🌱 ___________

22 Jun 2025, 22:07 UTC≈2,590 viewsread 12 August 2026
Photo

Launching: NEXUS (Nexus) Scan: inconclusive (🧐 manual review recommended). Pair: NEXUS / WETH (Uni V2) CA: 0xbd9C5c3Bb9AE9259196758862e0e5edA7BE3d70B Supply: 31,000,000,000 (+18 decimals) 🔗 TG 🤷‍♂️ | Web 🤷‍♂️ | Twitter 🤷‍♂️ | Code | Deployer | Holders 📊 DexT | DexV | Defined | Screener | KibaSwap 🔄 ___________________________________ ☎️ Joe 🌱 | Maythous 💪 | Vegeta 🥶 ___________________________________ 📣 Chann

22 Jun 2025, 22:06 UTC≈2,010 viewsread 12 August 2026
Photo

Verified: NEXUS (Nexus) Scan: inconclusive (🧐 manual review recommended). CA: 0xbd9C5c3Bb9AE9259196758862e0e5edA7BE3d70B Supply: 31,000,000,000 (+18 decimals) 🔗 TG 🤷‍♂️ | Web 🤷‍♂️ | Twitter 🤷‍♂️ | Code | Deployer ___________________________________ ☎️ Joe 🌱 | JK 🎮 | Iron Man 🤖 ___________________________________ 📣 Advertise (iToken): TG 📣 Channels (iToken): TG Donate 🪣 | Stay safe 🙏

22 Jun 2025, 22:04 UTC≈1,480 viewsread 12 August 2026
Photo

Deployed: NEXUS (Nexus) Scan: ⚠️ code unavailable for auto-analysis. CA: 0xbd9C5c3Bb9AE9259196758862e0e5edA7BE3d70B Supply: 31,000,000,000 (+18 decimals) 🔗 Code | Deployer ___________________________________ ☎️ Vegeta 🥶 | Bag 🎒 | JK 🎮 ___________________________________ 📣 Channels (iToken): TG 📣 Advertise (iToken): TG Donate 🪣 | Stay safe 🙏

22 Jun 2025, 22:03 UTC≈1,240 viewsread 12 August 2026
Photo

Launching: D&D (Heroes of DEX and Degens) Scan: ⚠️ code unavailable for auto-analysis. Pair: D&D / WETH (Uni V2) CA: 0x9032E9efecac73C0C7A77349eB0E98dcE3833a6c Supply: 1,000,000,000 (+9 decimals) 🔗 TG 🤷‍♂️ | Web 🤷‍♂️ | Twitter 🤷‍♂️ | Code | Deployer | Holders 📊 DexT | DexV | Defined | Screener | KibaSwap 🔄 ___________________________________ ☎️ JK 🎮 | Iron Man 🤖 | Killer 😈 ___________________________________

22 Jun 2025, 22:03 UTC≈1,010 viewsread 12 August 2026
Photo

Deployed: D&D (Heroes of DEX and Degens) Scan: ⚠️ code unavailable for auto-analysis. CA: 0x9032E9efecac73C0C7A77349eB0E98dcE3833a6c Supply: 1,000,000,000 (+9 decimals) 🔗 Code | Deployer ___________________________________ ☎️ Guru ♿️ | Iron Man 🤖 | Fitz 🌙 ___________________________________ 📣 Channels (iToken): TG 📣 Advertise (iToken): TG Donate 🪣 | Stay safe 🙏

22 Jun 2025, 22:03 UTC905 viewsread 12 August 2026
Photo

Launching: D&D (Heroes of DEX and Degens) Scan: ⚠️ code unavailable for auto-analysis. Pair: D&D / WETH (Uni V2) CA: 0x2f7e008784762a5Ecaab2Aa584829261EA926b52 Supply: 1,000,000,000 (+9 decimals) 🔗 TG 🤷‍♂️ | Web 🤷‍♂️ | Twitter 🤷‍♂️ | Code | Deployer | Holders 📊 DexT | DexV | Defined | Screener | KibaSwap 🔄 ___________________________________ ☎️ Brently 🐶 | Guru ♿️ | Vegeta 🥶 ___________________________________

Showing the 12 most recent of 20 posts we hold for @iTokenEthereum. 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 — 440,146 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.

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.

Mentions

Named by 10 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

@TRENDING (ETH / SOL)
@trending · 495,832
Telegram ranks this channel #65 of 78 here — alongside 77 others — read 9 August 2026
Maestro Bot Updates
@MaestroSniperUpdates · 193,571
Telegram ranks this channel #67 of 82 here — alongside 81 others — read 12 August 2026
Maestro Hub
@MaestroBotsHub · 172,101
Telegram ranks this channel #72 of 84 here — alongside 83 others — read 12 August 2026

This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“iToken - Ethereum” (@iTokenEthereum), 16,511 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/iTokenEthereum.

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.