Channel
@VEILAnnouncements
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
33subscribers
-1 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001250215177 |
|---|---|
| Type | Channel |
| Username | @VEILAnnouncements |
| Created | Between 1 March 2018 and 31 October 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 4 times, most recently 10 October 2026 |
| On Telegram | t.me/VEILAnnouncements |
Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 30 September 2026 and assigned it the closest of 31 fixed categories, at 58% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 13:20 | 33 | -1 |
| 11 Aug 2026, 00:45 | 34 | no change |
| 8 Aug 2026, 00:07 | 34 | first reading |
20 posts held, back to 31 October 2020 — 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 16 May 2023. An engagement rate over an empty window would be a number about nothing.
The website has been updated for the addition of the community bounty incentivised setup guide for the Veil wallet on Ubuntu Linux GUI OS, and a matching blog post with mention of the currently active Twitter campaign. https://veil-project.com/get-started/ contains a link to the new guide, and has been cleaned up and reworded for anticipated developments. People will no longer be distracted by inactive link icons for…
Having been announcing in other places, not really being Telegram users, we're setting up to support our Telegram channels better from now on. I notice, of course, that the above announcement is obsolete! The current released version is Veil Core 1.4.0, (https://github.com/Veil-Project/veil/releases) which was also a mandatory upgrade. We should have a minor upgrade soon, before any subsequent mandatory upgrade to su…
https://medium.com/veil-project/veil-core-mandatory-wallet-update-v1-3-0-is-available-now-13db3c63ffed All users and services need to upgrade to this 1.3.0.0 Veil Core wallet. Mandatory update. Deadline, block 2 million, but people need to see that exchanges have upgraded for reasonable confidence to remain.
In late April, the Veil team received a vulnerability report about the consensus validation of RingCT transactions. This vulnerability was not exploited and a fix was implemented. https://veil-project.com/news/2021-ringct-double-spend-fixed/
Have you updated to Veil Core mandatory wallet v1.2.1 yet? We’re now past the protocol enforcement time and nodes must be updated to be on the correct chain. Download here ➡️ https://github.com/Veil-Project/veil/releases/tag/v1.2.1.1
The new mandatory Veil Core wallet v1.2.1 is now available. We strongly recommend updating ASAP, and not to wait until the protocol enforcement fork date of May 16, 2021. Please refrain from trading on exchanges that have not updated to v1.2.1. Read more and download ➡️ https://veil-project.com/news/2021-wallet-121/
In today’s Meet the Team #interview, we chat with Veil QA and support guru Sean, where he shares his beginnings in crypto, observations on how digital currencies have evolved, and insights on his work and interests. https://veil-project.com/blog/meet-the-team-sean/
We have released Veil Core wallet v1.1.2, which includes a RandomX hash speed increase, various RandomX fixes, and an update to QR codes on address selection. Updating is not mandatory but is recommended. Download here: https://github.com/Veil-Project/veil/releases/tag/v1.1.2.1 #corewalletupdate
Looking ahead to 2021! Read on for more information about the broader objectives that Veil has set for the new year. ➡️ https://veil-project.com/blog/2021-project-itinerary/ #update
In this special Veil monthly #update, we outline progress made in December 2020 and look back at our accomplishments over the past year. https://veil-project.com/news/2020-december-update/
Veil Core wallet v1.1.1 is now available. It is a recommended update containing various improvements, optimizations, bug fixes, and GUI changes - most notably the mitigation of the Assertion PIndexWalk error. Download here: https://github.com/Veil-Project/veil/releases/tag/v1.1.1.1 #corewalletupdate
It’s time for our Twitter Holiday giveaway! ❄️ Check the official tweet for more details and participate for a chance to win a KeepKey or VEIL in prizes: https://twitter.com/ProjectVeil/status/1339269065836138496
Showing the 12 most recent of 20 posts we hold for @VEILAnnouncements. 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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“Veil Announcements” (@VEILAnnouncements), 33 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/VEILAnnouncements.
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.