Channel
@Xpose_Protocol
On this record: Growth · Engagement · What this channel posts · Posts · Cite this entry
387subscribers
-8 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001221317987 |
|---|---|
| Type | Channel |
| Username | @Xpose_Protocol |
| Description | Welcome to the official announcement channel of Xpose Protocol 💎 |
| 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 September 2026 |
| Last confirmed live | 6 September 2026 |
| Measurements held | 6 |
| On Telegram | t.me/Xpose_Protocol |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Sept 2026, 19:23 | 387 | no change |
| 6 Sept 2026, 07:41 | 387 | -1 |
| 29 Aug 2026, 23:14 | 388 | -4 |
| 22 Aug 2026, 03:09 | 392 | -1 |
| 14 Aug 2026, 20:25 | 393 | -2 |
| 7 Aug 2026, 00:10 | 395 | first reading |
20 posts held, back to 16 September 2021 — 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 2 November 2021. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 6 September 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.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Dear holders, The team is working, plans are being made, and conversations have been taking place with multiple industry experts to proceed towards the NFT market. The project didn't stop, even after many false rumors and accusations. This has only been in the interest of a few people who are spreading these lies. We will not be elaborating on this topic as it will not help $XP holders. In the upcoming month, the …
Dear community, Today, the 26th of October is 5 months after reaching the ATH of the 25th of May. This was also the beginning of taking necessary steps to turn around this project from unhealthy to healthy. The aim was to shift from a big liability to a solid project. The liability was created by the overwhelming growth of the project and the low liquidity pool in comparison with the market cap. This made people ha…
Dear community! If you are still facing issues regarding your XP tokens, please send a new E-mail to [email protected]. Use subject: XP token issue #
Dev here! Nothing exciting to announce. Stay awake! 👊
Token distribution is completed. Have a good day! 🙌
Good afternoon! We once again want to point out the importance of filling in your BEP20 withdrawal address on the XP dashboard. If your dashboard account does not have a filled-in withdrawal address, the team will not be able to distribute the tokens to your preferred wallet. How do I fill in my BEP20 withdrawal address? - Log in on the XP dashboard. - Go to the "personal tab". - Go to the tab "financial". - Fill…
Dear community! We don't want to bore you with meaningless news, so we won't be doing that It seems calm regarding $XP, calm before the storm? Behind the scenes, development for all Q4 calendar points is in full swing. Before we bring you any updates, we want things to go smoothly Soon, you will find out what this waiting period is all about.
Poll results! 🔥 Option 2 has got the most votes in the community-driven marketing campaign poll. We will reach out to the person who submitted option 2.
Community-driven marketing campaign! After looking at all the submitted marketing pitches provided by the community, these are the top 3 pitches. One extra option has been added by the Xpose Protocol team: This is option 4! 🔥 In the end, the community member who has submitted the pitch, is responsible for the execution. Of course, the Xpose Team will execute option 4 if the community decides to go with this campai…
Community. 🏁 It’s quiet. We know! There is a reason for this and you will soon find out! 🚩 Soon 👀 1️⃣4️⃣-6️⃣-2️⃣0️⃣ There is nothing more to announce. Sit back, put down your phone and keep an eye on the official announcement channel. ⚽️⚾️🏀🏈
File, posted without a caption
🚀$XP is launched on CMC! 🤯 We can boost the project some more, but we need your help for that. 🔥UPVOTE GOOD “👍🏻” 🔥Get us trending by making an account on CMC and add us to your watchlist “⭐️” https://coinmarketcap.com/currencies/xpose-protocol/
Showing the 12 most recent of 20 posts we hold for @Xpose_Protocol. 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.
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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“Xpose Protocol - Announcements” (@Xpose_Protocol), 387 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/Xpose_Protocol.
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.