Telegram RegisterThe public register of Telegram
Telegram profile photo for Persistence Validators Announcements

Channel

Persistence Validators Announcements

@PersistenceValidatorsUpdates

On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry

75subscribers

-4 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001604557365
TypeChannel
Username@PersistenceValidatorsUpdates
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live1 October 2026
Measurements held4
Confirmed unchanged1 time, most recently 1 October 2026
On Telegramt.me/PersistenceValidatorsUpdates

Topic

Technology — 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 1 October 2026 and assigned it the closest of 31 fixed categories, at 47% 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.

Growth

7579777 August 2026 — 79 subscribers9 August 2026 — 79 subscribers16 August 2026 — 78 subscribers1 October 2026 — 75 subscribers7 August 20261 October 2026
4 measurements spanning 55 days, net -4. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 74–80 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
1 Oct 2026, 19:1775-3
16 Aug 2026, 15:4678-1
9 Aug 2026, 19:3179no change
7 Aug 2026, 22:5779first reading

Engagement

20 posts held, back to 16 July 2025 — 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 8 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

39 reactions across 14 posts, in 2 distinct kinds. The most used accounts for 89.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍3589.7%
🫡410.3%

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 14 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 39 reactions 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 16 July 2025 to 8 July 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.

Recent posts

8 Jul 2026, 08:53 UTC43 viewsread 9 August 2026
Photo

🟠 [TESTNET] Persistence Testnet (test-core-2) Sunset Notice Hi everyone, As shared in our recent update, Persistence in the AI Era, we're refocusing the team and our resources toward AI transformation. As part of that shift, we're consolidating chain infrastructure that no longer aligns with our direction. That includes winding down the test-core-2 testnet. Our team currently operates the majority of the voting po…

Signed Promit | Persistence

27 Jan 2026, 04:51 UTC100 views3 reactionsread 9 August 2026

🟢 [MAINNET] PersistenceCore v16.0.1 Public Release The CometBFT security patch is now merged into the public persistenceCore repo. Release: https://github.com/persistenceOne/persistenceCore/releases/tag/v16.0.1 Anyone who prefers can now build directly from source using the v16.0.1 tag. Thank you!

👍3

Signed Promit | Persistence

16 Jan 2026, 03:56 UTC189 views3 reactionsread 9 August 2026

🔴 [MAINNET] Emergency Upgrade for core-1 chain to v16.0.1 We’ve been notified of a high-severity vulnerability impacting Persistence and many other Cosmos chains. A patched binary is available: once 66.67% of voting power upgrades, the chain will effectively be patched against the vulnerability. Please upgrade to the attached binary ASAP; this is a critical security update. The patched binary is not consensus brea…

👍3

Signed Promit | Persistence

24 Nov 2025, 06:47 UTC173 views3 reactionsread 9 August 2026
Photo

🟠 [MAINNET] Reminder for Persistence core-1 v16.0.0 Upgrade ETA: ~ 5 hours 27 minutes

👍3

Signed Promit | Persistence

23 Nov 2025, 14:40 UTC219 viewsread 9 August 2026

🟢 [MAINNET] PersistenceCore v16.0.0 Upgrade 🏗️ Would request everyone to prepare accordingly! Upgrade details: Proposal: https://www.mintscan.io/persistence/proposals/154 Height: 24,838,400 Release: https://github.com/persistenceOne/persistenceCore/releases/tag/v16.0.0 Timelines: Upgrade time: Nov 24th 2025, 12:15 UTC Countdown: https://www.mintscan.io/persistence/block/24838400

Signed Promit | Persistence

18 Nov 2025, 06:53 UTC138 views2 reactionsread 9 August 2026
Photo

🟠 [ TESTNET ] Reminder for Persistence test-core-2 v16.0.0-rc0 Upgrade ETA: ~5 hours 08 mins

🫡2

Signed Promit | Persistence

17 Nov 2025, 10:16 UTC118 viewsread 9 August 2026

🟡 [TESTNET] Upcoming Software upgrade on test-core-2 chain to v16.0.0-rc0 Upgrade Height: 13,938,200 Proposal: https://www.mintscan.io/persistence-testnet/proposals/96 Tag: https://github.com/persistenceOne/persistenceCore/releases/tag/v16.0.0-rc0 ETA to upgrade: ~1 day 1 hour 50 mins Countdown: https://www.mintscan.io/persistence-testnet/block/13938200 Would request all our testnet validators to prepare for upgr…

Signed Promit | Persistence

22 Oct 2025, 08:04 UTC162 views3 reactionsread 9 August 2026
Photo

🟠 [MAINNET] Reminder for Persistence core-1 v15.0.0 Upgrade ETA: ~ 2 hours 54 mins

👍3

Signed Madhur Satija

22 Oct 2025, 08:03 UTC273 views2 reactionsread 9 August 2026

🟢 [MAINNET] PersistenceCore v15.0.0 Upgrade 🏗️ Would request everyone to vote and prepare accordingly! Upgrade details: Proposal: https://www.mintscan.io/persistence/proposals/149 Height: 24,345,500 Release: https://github.com/persistenceOne/persistenceCore/releases/tag/v15.0.0 Timelines: Upgrade time: Oct 22nd 2025, 10:58 UTC Countdown: https://www.mintscan.io/persistence/block/24345500

👍2

Signed Madhur Satija

15 Oct 2025, 20:49 UTC196 views4 reactionsread 9 August 2026

🟡 [MAINNET] Rolling emergency upgrade for core-1 chain to v14.0.1 w.r.t: https://github.com/cometbft/cometbft/security/advisories/GHSA-hrhf-2vcr-ghch Repo: https://github.com/persistenceOne/persistenceCore/releases/tag/v14.0.1 Tag: v14.0.1 Would request everyone to perform the rolling upgrade and update your status with 👍 on the discord message

👍4

Signed Madhur Satija

15 Oct 2025, 20:35 UTC114 views2 reactionsread 9 August 2026

🟡 [TESTNET] Upcoming Software upgrade on test-core-2 chain to v15.0.0-rc0 Upgrade Height: 13,428,700 Proposal: https://www.mintscan.io/persistence-testnet/proposals/95 Tag: https://github.com/persistenceOne/persistenceCore/releases/tag/v15.0.0-rc0 ETA to upgrade: ~15 hours 28 mins Countdown: https://www.mintscan.io/persistence-testnet/block/13428700 Would request all our testnet validators to prepare for upgrade …

👍2

Signed Madhur Satija

4 Oct 2025, 10:12 UTC204 views1 reactionsread 9 August 2026

🟢 [MAINNET] PersistenceCore v14.0.0 Upgrade 🏗️ Would request everyone to vote and prepare accordingly! Upgrade details: Proposal: https://www.mintscan.io/persistence/proposals/147/ Height: 24,153,500 Release: https://github.com/persistenceOne/persistenceCore/releases/tag/v14.0.0 Timelines: Upgrade time: Oct 9th 2025, 12:03 UTC Countdown: https://www.mintscan.io/persistence/block/24153500

👍1

Signed Madhur Satija

Showing the 12 most recent of 20 posts we hold for @PersistenceValidatorsUpdates. 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.

Cite this entry

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 1 October 2026 — this entry's latest reading, not the date you are reading this.

“Persistence Validators Announcements” (@PersistenceValidatorsUpdates), 75 subscribers as measured 1 October 2026. Telegram Register, tgregister.com/channel/PersistenceValidatorsUpdates.

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.