0x1dF0e765Bbf3F195bad5b12f1C0ef18479CAF25d

Channel
Xenon Protocol | $XP
@XenonProtocol
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
8subscribers
+0 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001854569777 |
|---|---|
| Type | Channel |
| Username | @XenonProtocol |
| Created | 24 July 2023 — measured — dated from the channel’s first post |
| First recorded | 13 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/XenonProtocol |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 13:07 | 8 | no change |
| 13 Aug 2026, 12:31 | 8 | first reading |
Engagement
11 posts held, back to 24 July 2023 — 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 11 posts for this entry, the most recent from 5 January 2024. An engagement rate over an empty window would be a number about nothing.
Reaction mix
4 reactions across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 4 | 100.0% |
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 1 of the 11 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 4reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 24 July 2023 to 5 January 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
https://t.me/ShenTokenSol shen-token.vercel.app
https://t.me/shenrontokensol shen-token.vercel.app
CnTQGjyrX71jPoE6wX7sUu5tP2ihMfn9w2p1YFU9fniT
6pUoTJjCTikKtpmatFDqEi9nArfNaxgDEp6xXgUDx9mg
Its easy to do & It's all right here. Just use fIuxbeam.xyz to create a token, and do whatever you need with that. 0.02 SOL to create. Once you create it, in the URL, you'll see the Mint address ( Token address ), that's gonna be your token address. You'll also see it in the UI, and in your wallet Use fIuxbeam.xyz token manager to revoke mint authority, and freeze authority. Use openbook-expIorer.xyz to create a ma…
Its easy to do & It's all right here. Just use fIuxbeam.xyz to create a token, and do whatever you need with that. 0.02 SOL to create. Once you create it, in the URL, you'll see the Mint address ( Token address ), that's gonna be your token address. You'll also see it in the UI, and in your wallet Use fIuxbeam.xyz token manager to revoke mint authority, and freeze authority. Use openbook-expIorer.xyz to create a ma…
🤖🟣 Mev AI 🟣🤖 🚀 Engage with our innovative Web3-based AI chatbot. MevGPT brings intelligent conversation to the decentralized world. 🟣 Dapp Live 🟣 ATH 6k 🟣 MEV GPT BOT Live 🟣 Long Term Project MEVAI on DappRadar! 🗯 Telegram @MevAiBSC 📌 Contract 0x351598125e882cf7104fbe4cFe7226998D1e65f4
Just listed on Dapp Radar 🔌 🤖👾 Mev Ai 👾🤖 MEVAI on DappRadar! https://dappradar.com/dapp/mevai 📌 Telegram @MevAiBSC 📌 Contract 0x351598125e882cf7104fbe4cFe7226998D1e65f4
Xenon Protocol is being protected by @SafeguardRobot Click below to verify you're human
👍4
Channel created
Showing the 11 most recent of 11 posts we hold for @XenonProtocol. 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 — 1,132,466 of 1,481,306entries 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
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 4 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@XenonProtocol named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 15 August 2026 – 15 August 2026
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“Xenon Protocol | $XP” (@XenonProtocol), 8 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/XenonProtocol.
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.