Channel
@IOdevannouncements
On this record: Growth · Engagement · Posts · Telegram's recommendations · Cite this entry
365subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001276606987 |
|---|---|
| Type | Channel |
| Username | @IOdevannouncements |
| Created | Between 1 April 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/IOdevannouncements |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 07:07 | 365 | -1 |
| 8 Aug 2026, 06:31 | 366 | no change |
| 7 Aug 2026, 21:26 | 366 | first reading |
20 posts held, back to 13 September 2022 — 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 20 posts for this entry, the most recent from 1 November 2024. An engagement rate over an empty window would be a number about nothing.
Join us for the November SPO Call this coming Thursday, 15:00 UTC. 🔹 We'll be talking node 10.1.1, Chang #2 timelines, and ecosystem readiness. 🔹 We'll also hear updates from IO Engineering, the IO Partnerchains team, and Intersect's Parameters Committee. You can join the call in discord, we'll be sending a reminder with a calendar link next week. We look forward to speaking with you! https://discord.gg/fWr3fnKn…
Signed Matthew Capps
The Intersect Cardano Product Committee is running this survey with the aim to gather initial input which will help create a Cardano roadmap proposal. Please respond to it. https://docs.google.com/forms/d/e/1FAIpQLScBcVsUDfT1yTccitYGgupeNHe33AkuAbCREgeKbIjAht8AjA/viewform
Signed 👉 Ben
Chang technical Q&A Join IO Engineering an other members of the HFWG Thursday at 2pm UTC for a final technical Q&A covering what to expect leading up to the hardfork, providing support, and reiterating what anyone not yet caught up with the rest of the ecosystem should do to prepare for the Chang Hard Fork. ICYMI 👀 - Intersect's Hard Fork Working Group has set the hard fork date: September 1st. The agenda for this…
Signed Matthew Capps
Greetings! 👋 re: Open office session and preprod fork. The IO Engineering team, along with some other members of Intersect's Hard Fork Working Group (HFWG), are having an open office session, Monday 3-3:45pm UTC, to provide support and answer questions about upgrades for the Chang hard fork. Some additional reminders: 🔹 Mainnet hard fork target: September 1st. Intersect announced on Friday that based on consensus o…
Signed Matthew Capps
Chang dapp upgrade Q&A Join IOE and Intersect's Hard Fork WG Thursday at 3pm UTC for a final dedicated walkthrough of the reference info dapps should use to prepare for the Chang Hard Fork, followed by a Q&A session. The agenda for this event is as follows: 1️⃣ Intro: 'Minimal Viable Chang' for DApps (15m) - node upgrade - cost model - plutus v2 / v3 2️⃣ Structured Q&A (30m) - testing and PreProd - cost model suppo…
Signed Matthew Capps
The target for mainnet hardfork is Tuesday 27th August, with a final go/no go decision scheduled for early Friday 23rd August. https://x.com/IntersectMBO/status/1825946121765896609
Signed 👉 Ben
Chang upgrade guide for dapps Join us Thursday at 1pm UTC for our second dedicated walkthrough of the reference info dapps should use to prepare for the Chang Hard Fork, followed by a Q&A session. The agenda for this event is as follows: 1. Cost Model 2. Migrating a Dapp from Plutus V2 to Plutus V3 3. Q&A + Other reference info 4. Call To Action - signal your team's readiness We anticipate that most people will be…
Signed Matthew Capps
https://x.com/rhyslbw/status/1817869327145554303
Signed 👉 Ben
IOG remains committed to the principles of open source and Cardano community collaboration, which will only strengthen in the age of Voltaire. For the past 12 months, in the spirit of transparency & collaborative development, the IOG Hydra and Mithril teams have been holding monthly open dev calls. Now, both the IOG Plutus and Consensus teams have established technical working groups under Intersect, following a simi…
Signed 👉 Ben
Join us today in Discord for our April DApp Call https://discord.com/events/826816523368005654/1095771688668495993 The DApp call features Patrick Kolesar, Scrum Master for DApp Store & Lace, as a speaker. Patrik will be discussing the CIP72 initiative and its potential impact on the Cardano ecosystem. CIP72 is a community-driven initiative aimed at creating a mechanism for DApp registration, discovery, and certific…
Signed Rebecca Hopwood
@here starting now: https://discord.com/events/826816523368005654/1078333906991972472
Signed Rebecca Hopwood
🥑 I'm looking for a #DevRel Lead who is technically adept with a coding background while also being a good listener and strong communicator. https://apply.workable.com/io-global/j/2C68C5F602/
Signed 👉 Ben
Showing the 12 most recent of 20 posts we hold for @IOdevannouncements. 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.
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.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“🥑 IOG DEV Announcements” (@IOdevannouncements), 365 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/IOdevannouncements.
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.