Channel
@KyveProposals
On this record: Growth · Engagement · Reactions · Posts · Cite this entry
309subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001518888709 |
|---|---|
| Type | Channel |
| Username | @KyveProposals |
| Created | Between 1 August 2021 and 18 July 2022— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 23 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 23 August 2026 |
| On Telegram | t.me/KyveProposals |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Aug 2026, 07:58 | 309 | -1 |
| 14 Aug 2026, 21:45 | 310 | +1 |
| 8 Aug 2026, 00:53 | 309 | +1 |
| 7 Aug 2026, 06:17 | 308 | first reading |
20 posts held, back to 18 July 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 25 November 2022. An engagement rate over an empty window would be a number about nothing.
103 reactions across 20 posts, in 6 distinct kinds. The most used accounts for 86.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 89 | 86.4% | |
| 👎 | 5 | 4.85% | |
| 💩 | 4 | 3.88% | |
| 🤔 | 3 | 2.91% | |
| ❤ | 1 | 0.971% | |
| 🤯 | 1 | 0.971% |
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 103reactions 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 18 July 2022 to 25 November 2022, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
New proposal #170 ***Version 0.7.0 Upgrade*** This update includes the integration of the latest Cosmos SDK v0.46, a refactoring of the overall code structure to ensure full optimization of the chain and protocol, as well as a new inter-pool security feature, automated testing improvements, and UI/UX upgrades.\n\nAdditional information can be found at https://docs.kyve.network\nAfter this upgrade please refer to ht…
👍6
New proposal #169 ***KYVE at Lisbon Blockchain Week 2022*** <div><b>Authors:</b> Margaux, Paul</div><div><b>Date:</b> 19th October 2022</div><div><br></div><div><br></div><div><b>Abstract:</b></div><div><br></div><div>This proposal draft requests approval and seeks input from the KYVE DAO regarding the KYVE team’s participation at a few of the main blockchain events (detailed below) taking place during Lisbon Block…
👍2
New proposal #168 ***Create Sei Pool*** The KYVE Team proposes that the next pool should archive data for the Sei network. Start: 2022-09-05 End: 2022-09-05 To vote: https://app.kyve.network/#/governance/168
👍3
New proposal #167 ***Upgrade Near Runtime*** Upgrade @kyve/near to v0.3.6 Start: 2022-09-05 End: 2022-09-05 To vote: https://app.kyve.network/#/governance/167
👍5
New proposal #166 ***Pause Zilliqa Pool*** Due to an unreliable endpoint, we are pausing this pool for now. Start: 2022-08-29 End: 2022-08-29 To vote: https://app.kyve.network/#/governance/166
👍2
New proposal #165 ***Upgrade Cosmos Runtime*** Upgrade @kyve/cosmos to v0.3.6 Start: 2022-08-23 End: 2022-08-23 To vote: https://app.kyve.network/#/governance/165
👍5
New proposal #164 ***Test*** <span style="background-color: rgba(0, 0, 0, 0.2);">https://forum.kyve.network/</span> Start: 2022-08-22 End: 2022-08-23 To vote: https://app.kyve.network/#/governance/164
🤔3
New proposal #163 ***Test *** https://forum.kyve.network/ Start: 2022-08-22 End: 2022-08-23 To vote: https://app.kyve.network/#/governance/163
👍3
New proposal #162 ***Create Archway Constantine Pool*** The KYVE Team proposes that the next pool should archive the Constantine network from Archway. Start: 2022-08-17 End: 2022-08-17 To vote: https://app.kyve.network/#/governance/162
👍8
New proposal #161 ***Test*** Test Start: 2022-08-11 End: 2022-08-12 To vote: https://app.kyve.network/#/governance/161
👍3
New proposal #160 ***Version 0.6.4 Upgrade*** For a full description see: https://github.com/KYVENetwork/chain/releases/tag/v0.6.4 Start: 2022-08-04 End: 2022-08-04 To vote: https://app.kyve.network/#/governance/160
👍1👎1
New proposal #159 ***Increase Undelegation Unbonding Time*** Increase undelegation time to 21 days. Start: 2022-08-02 End: 2022-08-02 To vote: https://app.kyve.network/#/governance/159
👍7👎4❤1🤯1
Showing the 12 most recent of 20 posts we hold for @KyveProposals. 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.
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 23 August 2026 — this entry's latest reading, not the date you are reading this.
“Kyve testnet proposals” (@KyveProposals), 309 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/KyveProposals.
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.