2 Aug 2026, 17:12 UTC4 viewsread 11 August 2026
Photo
Proposal vote ended! Prop #1036 (Recover expired IBC Client for Gravity Bridge) Status: Passed 🟢 97.9% of YES votes, 0% of NO votes, turnout: 53.43%
Channel
Osmosis Governance Alerts
@osmogov
On this record: Topic · Growth · Engagement · Posts · Cite this entry
27subscribers
+0 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 | -1001808101717 |
|---|---|
| Type | Channel |
| Username | @osmogov |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 11 October 2026 |
| On Telegram | t.me/osmogov |
Topic
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 1 October 2026 and assigned it the closest of 31 fixed categories, at 61% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Oct 2026, 19:00 | 27 | +1 |
| 10 Sept 2026, 06:21 | 26 | -1 |
| 11 Aug 2026, 07:15 | 27 | no change |
| 7 Aug 2026, 09:05 | 27 | first reading |
Engagement
20 posts held, back to 20 July 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 2 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
2 Aug 2026, 08:32 UTC6 viewsread 11 August 2026
Photo
Proposal vote ended! Prop #1035 ( Recover IBC Client: Osmosis ↔ QIE (07-tendermint-3681)) Status: Passed 🟢 (97.94% of YES votes, turnout: 54.55%)
1 Aug 2026, 17:12 UTC6 viewsread 11 August 2026
⏳ 24 hours left to vote for proposal: Prop #1036: Recover expired IBC Client for Gravity Bridge Status: Passing 🟢 97.8% of YES votes, 0% of NO votes, turnout: 50.89%
1 Aug 2026, 14:56 UTC7 viewsread 11 August 2026
Photo
Proposal vote ended! Prop #1032 (Increase Governance Proposal deposits) Status: Passed 🟢 95.77% of YES votes, 0.02% of NO votes, turnout: 55.46%
1 Aug 2026, 11:04 UTC7 viewsread 11 August 2026
Photo
Proposal vote ended! Prop #1031 (Alloyed BTC: Increase nBTC static limit to 60%) Status: Passed 🟢 97.94% of YES votes, 0.01% of NO votes, turnout: 55.37%
1 Aug 2026, 08:32 UTC7 viewsread 11 August 2026
⏳ 24 hours left to vote for proposal: Prop #1035: Recover IBC Client: Osmosis ↔ QIE (07-tendermint-3681) Status: Passing 🟢 97.71% of YES votes, 0.01% of NO votes, turnout: 49.08%
31 Jul 2026, 14:56 UTC6 viewsread 11 August 2026
⏳ 24 hours left to vote for proposal: Prop #1032: Increase Governance Proposal deposits Status: Passing 🟢 94.83% of YES votes, 0.02% of NO votes, turnout: 54.58%
31 Jul 2026, 11:04 UTC5 viewsread 11 August 2026
⏳ 24 hours left to vote for proposal: Prop #1031: Alloyed BTC: Increase nBTC static limit to 60% Status: Passing 🟢 97.02% of YES votes, 0.01% of NO votes, turnout: 54.47%
28 Jul 2026, 17:14 UTC7 viewsread 11 August 2026
Photo
New proposal available for voting: Prop #1036: Recover expired IBC Client for Gravity Bridge This proposal seeks to recover IBC Client 07-tendermint-1737 connecting CosmosHub to Gravity Bridge. The recovery process will replace the state of expired client with the state of newly created substitute client 07-tendermint-3737. Due to an exploit executed on Gravity Bridge, the network was down for several weeks, causin…
28 Jul 2026, 08:42 UTC8 viewsread 11 August 2026
Photo
New proposal available for voting: Prop #1035: Recover IBC Client: Osmosis ↔ QIE (07-tendermint-3681) Recover expired IBC light client 07-tendermint-3681 which tracks the QIE chain (qie_1990-1). This client is required for IBC channel channel-109956 (Osmosis) ↔ channel-0 (QIE) to function. The client expired following a planned 2-week maintenance halt on the QIE chain, during which the 9-day trusting_period elapsed…
27 Jul 2026, 18:56 UTC8 viewsread 11 August 2026
Photo
New proposal available for voting: Prop #1033: Recover expired IBC client 07-tendermint-3204 (Osmosis <> SEDA) 07-tendermint-3204 is an expired IBC light client of the SEDA chain (chain-id: seda-1). It is associated with the channel channel-75016, which so far has transferred approximately 1,150,859 SEDA under the denomination ibc/956AEF1DA92F70584266E87978C3F30A43B91EE6ABC62F03D097E79F6B99C4D8. This client recover…
27 Jul 2026, 15:02 UTC7 viewsread 11 August 2026
Photo
New proposal available for voting: Prop #1032: Increase Governance Proposal deposits [Governance Params Update] This proposal updates the governance module deposit parameters to increase the OSMO-denominated proposal deposits. Background Osmosis governance proposals require a deposit to reach the voting period. The deposit is denominated in OSMO: Minimum deposit: 6,000 OSMO Expedited minimum deposit: 20,000 OSMO…
Showing the 12 most recent of 20 posts we hold for @osmogov. 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.
“Osmosis Governance Alerts” (@osmogov), 27 subscribers as measured 1 October 2026. Telegram Register, tgregister.com/channel/osmogov.
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.