Channel
@Timpi_Announcments
On this record: Topic · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
1,128subscribers
-37 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002048331706 |
|---|---|
| Type | Channel |
| Username | @Timpi_Announcments |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/Timpi_Announcments |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 78% 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 |
|---|---|---|
| 17 Sept 2026, 12:59 | 1,128 | -2 |
| 13 Sept 2026, 11:21 | 1,130 | -4 |
| 9 Sept 2026, 23:01 | 1,134 | -2 |
| 1 Sept 2026, 09:34 | 1,136 | -2 |
| 29 Aug 2026, 08:57 | 1,138 | -4 |
| 26 Aug 2026, 13:35 | 1,142 | -3 |
| 24 Aug 2026, 00:16 | 1,145 | -5 |
| 19 Aug 2026, 22:42 | 1,150 | -5 |
| 16 Aug 2026, 20:37 | 1,155 | -2 |
| 13 Aug 2026, 07:27 | 1,157 | -6 |
| 10 Aug 2026, 15:07 | 1,163 | -2 |
| 7 Aug 2026, 23:33 | 1,165 | no change |
| 7 Aug 2026, 17:51 | 1,165 | first reading |
20 posts held, back to 5 April 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 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 28 July 2026. An engagement rate over an empty window would be a number about nothing.
📢 Synaptron: v2 is required for rewards from 1 August Synaptron 2.0.2 is out — it's the version that reports to the new Orca Controller, and it's what earns under v2. From 5 August , a Synaptron must run version 2.x to be eligible. July is not affected — nobody loses July for being on 1.x. Use the time until then to upgrade. Each month a Synaptron needs both v2.x and 70% uptime. 🔧 How to upgrade — pick your platf…
Reminder: v2 is required for rewards from 1 August — 6 days left From Saturday 1 August, a node must run version 2.x to earn. July is unaffected — nobody loses July for being on 1.x. But August is paid on version and uptime from day one, so the switch needs to happen before the month turns. Take 30 seconds and check your own nodes now: 🔹 /collector <guid> 🔹 /geocore <guid> 🔹 /guardian <guid> If the bot says v2.x —…
📢 Guardian: v2 is required for rewards from 1 August We've fixed the reward system — uptime is now measured correctly, and the payout numbers are trustworthy again. The last piece is the version requirement. From 1 August, a Guardian must run version 2.x to be eligible. July is not affected — nobody loses July for being on 1.x. Each month a Guardian needs both v2.x and 90% uptime. ✅ v2 is on :latest right now. If…
📢 Collector: v2 is required for rewards from 1 August We've fixed the reward system — uptime is now measured correctly, and the payout numbers are trustworthy again. The last piece is the version requirement. From 1 August, a Collector must run version 2.x to be eligible. July is not affected — nobody loses July for being on 1.x. Use the time until then to get updated. Each month a Collector needs both v2.x and 70…
IT’S LIVE. THE TIMPI WORLD MAP The 3D globe visualisation of the Timpi network is now up and running. Real data, real nodes, real network activity. This isn’t a mock-up. It’s the actual network breathing in real time. ━━━━━━━━━━━━━━━━━━━━━━━━━ What You’re Looking At, Live nodes and regional clusters across the globe, Real-time network communications pulling straight from the TAP network, Node operator dashboard, …
🎉 GeoCore: **NEW Update + turn on auto-updates — do it once, never update manually again** Our latest GeoCore image fixes a connection-handling issue that could reduce crawling across the network. Run one small Watchtower container — it brings you to the current fix within ~1 hour and keeps your GeoCore on the latest version automatically from now on. Updated guide: https://github.com/Timpi-official/Nodes/blob/ma…
🎙️ TIMPI MONTHLY AMA, REMINDER Our next AMA is coming up shortly: 📅 Wednesday 17 June 🕗 20:00 UTC 🔗 Microsoft Teams Join here: https://teams.microsoft.com/meet/48639368097404?p=vRlCwQAHOGnMuE9frT ━━━━━━━━━━━━━━━━━━━━━━━━━ 📝 Got a question for the team? Drop it in the AMA form so it can be prepared and answered properly: https://forms.office.com/e/nySzhgp5eJ ⏰ Form closes Friday 13 June to give the team time to p…
Today we are announcing two closely related decisions that will help shape the future of the Timpi ecosystem. The first is that we have decided to begin the process of removing NTMPI from its current centralized exchange listings. The second is that we are formally initiating the process of migrating NTMPI to a new blockchain ecosystem. While our exchange listings have provided accessibility for some users, they ha…
Guardian storage is already in use for online Guardians (European clusters live). US clusters come online once out of the reboot loop. ━━━━━━━━━━━━━━━━━━━━━━━━━ 🏗 6. NETWORK ARCHITECTURE — HOW IT FITS TOGETHER Joerg explained the layered design: 🔹 Cold storage (Guardians) — full dataset, source of truth 🔹 Warm storage — already live, serves queries 🔹 Hot cluster (HW deployment) — coming next, major performance gain…
🔹 Got free time and want to help? Reach out. Marketing especially needs more support. 🔹 Got a product idea built on Timpi's data? Contact the team. They'll offer favourable terms on data access to get businesses started. 🔹 Resources/funding can't be offered, but access to the index — normally a major cost — can be.
🎙 TIMPI MONTHLY AMA RECAP Tuesday 20 May 2026 · 1h 42m · Microsoft Teams Hosts: Gareth Evans & Joerg Buss The first monthly Timpi AMA covered around half of the 75 questions submitted in advance. Below is a detailed recap across 5 posts. Remaining questions will be answered in writing and at the next AMA. ━━━━━━━━━━━━━━━━━━━━━━━━━ 🔑 TOP-LINE NEWS ▸ APY extended to 31 December 2026 at the current 17% ▸ Buyback mode…
@everyone we are now live https://teams.microsoft.com/meet/45392442966498?p=ApQKhQOGO3tUuZGU8p
Showing the 12 most recent of 20 posts we hold for @Timpi_Announcments. 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.
@Timpi_Announcments named 2 handles 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.
References a handle that is not a live channel — we have no record it ever was one.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“Timpi (Official) Announcements” (@Timpi_Announcments), 1,128 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/Timpi_Announcments.
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.