Telegram RegisterThe public register of Telegram
Telegram profile photo for KIRA Announcements

Channel

KIRA Announcements

@KiraAnnouncements

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

492subscribers

-3 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001424861637
TypeChannel
Username@KiraAnnouncements
CreatedBetween 1 April 2019 and 31 October 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live27 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 27 August 2026
On Telegramt.me/KiraAnnouncements

Growth

4924964946 August 2026 — 495 subscribers6 August 2026 — 495 subscribers13 August 2026 — 496 subscribers19 August 2026 — 495 subscribers27 August 2026 — 492 subscribers6 August 202627 August 2026
5 measurements spanning 20 days, net -3. 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 491–497 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Aug 2026, 05:54492-3
19 Aug 2026, 19:35495-1
13 Aug 2026, 11:24496+1
6 Aug 2026, 20:04495no change
6 Aug 2026, 19:56495first reading

Engagement

19 posts held, back to 14 October 2022the 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 19 posts for this entry, the most recent from 2 January 2023. An engagement rate over an empty window would be a number about nothing.

Reaction mix

126 reactions across 17 posts, in 6 distinct kinds. The most used accounts for 42.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥5342.1%
👍4535.7%
🥰2217.5%
👌21.59%
👎21.59%
🤡21.59%

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 18 of the 19 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 126reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 14 October 2022 to 2 January 2023, 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

2 Jan 2023, 09:04 UTC≈2,300 views22 reactionsread 6 August 2026

Happy New Year everyone, and dont worry, things are being readjusted a bit on social media, more announcements coming soon, stay tuned please.

🥰12👍10

25 Dec 2022, 06:52 UTC≈2,070 views7 reactionsread 6 August 2026
Photo

Happy Christmas 🎄🎉❤️ to all of our #KIRA community. Stay tuned for our latest improvements on mainnet release and roadmap. https://twitter.com/kira_official/status/1606905564440956930?s=46&t=qqIXqR2Or9sDGcT3S0YGAw

👍7

20 Dec 2022, 19:11 UTC≈1,670 views9 reactionsread 6 August 2026
Photo

WEEKLY DEVELOPMENT UPDATES FRONTEND (miro) 🔹Working on automatic deployment and release versioning 🔹Updated supported version of flutter to 2.3.9 🔹Fixed URL path on IPFS 🔹Next step : Adjustments before release of MVP MIDDLEWARE (interx) 🔹Correct the output for transactions endpoint. 🔹Finalize filtering feature by date, status, and type. 🔹Add pagination to the endpoint response. 🔹Add integration, and unit tests for

👍9

10 Dec 2022, 15:13 UTC≈1,120 views0 reactionsread 6 August 2026
Photo

WEEKLY DEVELOPMENT UPDATES FRONTEND 🔹 Working on automatic deployment and release versioning 🔹 Added proxy support 🔹 Next step: Adjustments before release of MVP MIDDLEWARE 🔹 Investigate the way to fetch failed transactions per user 🔹 Filter cached transactions by date, status, and type 🔹 Next step : Complete filtering feature by direction as well as sorting and write integration tests for the api. BACKEND 🔹 Commu

6 Dec 2022, 14:14 UTC799 views5 reactionsread 6 August 2026
Photo

📰Welcome to the November edition of the #KIRA monthly newsletter, highlighting everything we have done in November and what to expect going forward. Let us know what you would like to see in December and going forward into 2023. 🤝 https://blog.kira.network/kira-newsletter-november-2022-dab3747ae829 https://twitter.com/kira_official/status/1600128337803763712?s=46&t=IFvN8vnUlv1M3SmPRiwsZw

🔥5

4 Dec 2022, 15:44 UTC781 viewsread 6 August 2026
Photo

WEEKLY DEVELOPMENT UPDATES FRONTEND 🔹 Finished work on responsive transaction fee 🔹 Started work on automatic deployment and release versioning 🔹 Next step : Adjustments before release of MVP MIDDLEWARE 🔹 Implement new cache db for user transaction management(WIP) 🔹 Find optimized ways to bypass tendermint limitations for querying transactions by various filtering options (WIP) 🔹 Add new filtering options as param

28 Nov 2022, 16:40 UTC700 views2 reactionsread 6 August 2026
Photo

WEEKLY DEVELOPMENT UPDATES FRONTEND 🔹 Continued work on responsive transaction fee 🔹 Next step: Automatic deployment and release versioning MIDDLEWARE 🔹 Add integration tests for EVM endpoints 🔹 Update uint64 to uint256 for evm balances BACKEND 🔹 Create message, proposal, keys, codecs on types for collectives 🔹 Create basic infrastructure for keeper (grpc query, msg server, collective getter/setter, keeper, cli) 🔹

👍2

22 Nov 2022, 15:33 UTC631 views10 reactionsread 6 August 2026
Photo

KIRAs revolutionary Multi-Bonded Proof-of-Stake consensus model solves the limitations of current Proof-of-Stake models, providing unprecedented security, added utility for old and new-age assets, and new avenues for potentially unlimited capital inflows. Find out more about MBPoS and how it solves the limitations of current PoS models in the presentation below: https://www.youtube.com/watch?v=oceGUa9B3Jg&ab_channel

🔥8👌2

20 Nov 2022, 14:27 UTC647 views7 reactionsread 6 August 2026
Photo

WEEKLY DEVELOPMENT UPDATES FRONTEND 🔹 Finished bug with pages routing in Account Send Page 🔹 Started work on responsive transaction fee 🔹 Next step: Automatic deployment and release versioning MIDDLEWARE 🔹 Eliminated old endpoints from interx 🔹 Added filtering options for sort and status to transactions query endpoint 🔹 Added unit tests for evm endpoints 🔹 Made endpoints accept epochs not only date format for dateS

🔥3👍2👎2

18 Nov 2022, 13:14 UTC616 views5 reactionsread 6 August 2026

KIRA Quiz Welcome everyone to the first KIRA quiz in our telegram. The quiz will start at exactly 1500 UTC on 19/11/2022 in this Telegram channel, and the winner will receive $50 so stay tuned! The questions will be based on the MBPoS article below, and are in a timed short answer format: https://blog.kira.network/mbpos-consensus-and-asset-liquidity-through-staking-derivatives-8e729ea6663f There will be 5 question

👍5

17 Nov 2022, 10:28 UTC≈4,240 views12 reactionsread 6 August 2026
Photo

GIVEAWAY ALERT At KIRA we believe in giving back to the community, especially after everything that's happened in Crypto recently, which is why we are giving away another $200 to one lucky winner. 🍀 See the tweet below for details on how to enter: https://twitter.com/kira_official/status/1593187496745373699?s=46&t=4pKcOoc6cH2or76Pnoclcw If you haven't already make sure to check out our latest article, explaining o

🥰8👍2🤡2

15 Nov 2022, 15:43 UTC573 views7 reactionsread 6 August 2026
Photo

MULTI BONDED PROOF OF STAKE EXPLAINED KIRA’s revolutionary Multi-Bonded-Proof-of-Stake consensus model enables liquid staking through 1:1 staking derivatives, ensuring the security of the network whilst maintaining full ownership of your assets. This means you can stake any digital/virtual asset to secure the network rather than the native network token that is the case with traditional PoS consensus, and receive s

👍5🥰2

Showing the 12 most recent of 19 posts we hold for @KiraAnnouncements. 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 27 August 2026 — this entry's latest reading, not the date you are reading this.

“KIRA Announcements” (@KiraAnnouncements), 492 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/KiraAnnouncements.

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.