Channel
@DevvEAnnouncements
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
4,370subscribers
-34 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001883690885 |
|---|---|
| Type | Channel |
| Username | @DevvEAnnouncements |
| Created | Between 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 17 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 17 August 2026 |
| On Telegram | t.me/DevvEAnnouncements |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Aug 2026, 10:44 | 4,370 | -12 |
| 13 Aug 2026, 13:07 | 4,382 | -9 |
| 10 Aug 2026, 13:32 | 4,391 | -10 |
| 7 Aug 2026, 21:01 | 4,401 | -3 |
| 6 Aug 2026, 21:32 | 4,404 | first reading |
20 posts held, back to 11 February 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 6 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 25 June 2026. An engagement rate over an empty window would be a number about nothing.
1,327 reactions across 20 posts, in 19 distinct kinds. The most used accounts for 46.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 613 | 46.2% | |
| ❤ | 390 | 29.4% | |
| 👍 | 142 | 10.7% | |
| 👏 | 100 | 7.54% | |
| 🤪 | 12 | 0.904% | |
| 🦄 | 12 | 0.904% | |
| ❤🔥 | 11 | 0.829% | |
| 🤷♂ | 10 | 0.754% | |
| ⚡ | 8 | 0.603% | |
| 🎉 | 6 | 0.452% | |
| 🥰 | 6 | 0.452% | |
| 👌 | 3 | 0.226% | |
| 💩 | 3 | 0.226% | |
| 😴 | 3 | 0.226% | |
| 🙏 | 3 | 0.226% | |
| 🕊 | 2 | 0.151% | |
| 🍓 | 1 | 0.075% | |
| 🤔 | 1 | 0.075% | |
| 🤩 | 1 | 0.075% |
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 20 of the 20 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 1,327reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 11 February 2026 to 25 June 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
A look ahead: Introducing DevvX Hello everyone. I want to share where we are headed, and some news I am excited about. When we created DevvE, the second "E" in the name stood for ESG, and the token was built around an ESG philosophy and the goals that came with it. Since then, the landscape has changed. ESG has become highly politicized, and as a category it has not only stalled but in many situations has turned ne…
🔥20❤16👏8💩3🦄3🙏2
Here's a second video, that shows professional applications being built on Fias - again, it shows the type of things that will be able to be tied in to the blockchain... I had an amazing experience on Fias last week, building powerful applications for a customer who gave us a challenge. We took their challenge, that they thought was aggressive, and not only did what they thought might be impossible, but did 4x the w…
❤40🦄6👏5🔥5
First look at Fias. On the Devv side of things, one thing I’ll point out is that Fias will let people easily build blockchain applications on top of DevvX. Fias is also being used to create the new version of DevvX and the business around it. It's very powerful and a big day for Devv as well. Fias Beta Launch First Look
🔥44❤9👏3🦄3👍1
I just did the first cross shard transfer a few minutes ago. This is an enormous milestone and big day for the new DevvX architecture.
👏59🔥33❤20⚡4👍2🕊2👌1
Hey everyone, here is a first iteration of the new roadmap strategy. We'll hone the approach over time, but the general idea is to have a list of items we're working on available for people to see so that everyone can see what is coming, and see progress. I think a little more granular view of what we are doing is a better approach than what Forevver did in the past. The update includes information on both Fias and D…
🔥33❤19
Just had another nice DevvX milestone - I got a three validator shard benchmark on staging (actual AWS servers) - It was approaching 2k tps per shard (and you simply add as many shards as you need to reach the overall throughput you're looking to get). The previous note I made a few days ago was on a local computer. This test was transactions coming from the local computer (as is the case in real world use), but hitt…
🔥65👏14❤12👍7
Hey Everyone, nice DevvX milestone this morning. I just ran a benchmarking test of 100,000 transactions, and it processed it at about 1000 transactions per second on the test shard. That's the right order of magnitude that I need. Then, if you need 1 million tps, you would spin up 1000 shards. I'll caveat that it was a local system running localstack for the simulation (though I expect I can do better on better AWS h…
🔥82❤🔥11❤6👍4🎉3👏1🥰1
I just had my first 3 validator transaction on staging go through on the new DevvX. This means that we have a shard with permanence running on staging with decentralized validators giving consensus through the newly designed proof of validation consensus mechanism. When I go into the block on the new block explorer, I see all three proof of validation signatures on the block. so awesome.
🔥63❤16⚡4🎉3👏3👍2🤪1
Hey Everyone, we're ramping up for the Fias closed Beta. I'm going to keep this to our Telegram community to start, and expand our awareness efforts soon. We will let people into the closed beta in waves. Put anything you want us to consider in your application - what you would like to build (this is the main thing),the amount of time and the ways you've been supporting the project, anything else you think we should …
🔥33❤12👍8🥰3
Big progress today on two fronts!! First I created the first DevvX transaction on staging (a minting of 100,000,000 TestCoin). This represents the first DevvX transaction in the new AI created version of DevvX, on a persistent blockchain. I had the local version working before, but for an online server, I had to get key management in, all of the AWS stacks in place, auth working, wallet generation, and the blockchai…
❤58🔥28🤷♂4🤪2👍1
Hey everyone, I’m gearing up for a more regular flow of information and videos. We are creating a social media arche that makes it easier to post. Also, I am figuring out the mechanical process to do AI led interviews. I am writing here as I would like to hear from folks what topics they want to hear about. A lot of my videos will focus on entrepreneurship and what it takes to start a business. I’ll also give techni…
🔥29❤7🤷♂6
Ok Everyone, this post may be the most significant post I've done at Devv. This morning is a key moment driving us into the future. After two weeks of design, I am actually starting the programming of the new DevvX platform right now. The first file with code will be created when I tell the AI to start in just a moment. It has already reviewed the entire design document, and has put together a phased plan for impleme…
🔥93❤31👏4👌2🤩1
Showing the 12 most recent of 20 posts we hold for @DevvEAnnouncements. 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 — 1,220,734 of 1,550,220entries 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.
Named by 1 registered channel — 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.
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 17 August 2026 — this entry's latest reading, not the date you are reading this.
“DevvE Announcements” (@DevvEAnnouncements), 4,370 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/DevvEAnnouncements.
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.