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

Channel

Mintlayer Announcements

@mintlayer_announcements

On this record: Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

4,536subscribers

+4 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001319318856
TypeChannel
Username@mintlayer_announcements
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live7 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 7 September 2026
On Telegramt.me/mintlayer_announcements

Growth

4,5324,5574,544.56 August 2026 — 4,532 subscribers7 August 2026 — 4,532 subscribers10 August 2026 — 4,534 subscribers13 August 2026 — 4,535 subscribers16 August 2026 — 4,544 subscribers19 August 2026 — 4,549 subscribers22 August 2026 — 4,552 subscribers25 August 2026 — 4,557 subscribers28 August 2026 — 4,554 subscribers31 August 2026 — 4,552 subscribers2 September 2026 — 4,546 subscribers7 September 2026 — 4,536 subscribers4,5366 August 20267 September 2026
12 measurements spanning 32 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 4,528–4,561 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Sept 2026, 18:384,536-10
2 Sept 2026, 18:254,546-6
31 Aug 2026, 03:174,552-2
28 Aug 2026, 11:244,554-3
25 Aug 2026, 10:434,557+5
22 Aug 2026, 13:154,552+3
19 Aug 2026, 13:254,549+5
16 Aug 2026, 20:454,544+9
13 Aug 2026, 14:384,535+1
10 Aug 2026, 18:174,534+2
7 Aug 2026, 12:544,532no change
6 Aug 2026, 23:164,532first reading

Engagement

18 posts held, back to 15 May 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 7 pages 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 18 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

265 reactions across 16 posts, in 4 distinct kinds. The most used accounts for 41.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥10941.1%
9034.0%
👍3312.5%
😁3312.5%

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

Measured over the 18 most recent posts we hold, published 15 May 2026 to 3 August 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

3 Aug 2026, 15:37 UTC430 views15 reactionsread 12 August 2026

July Dev Update Features: 🟩 Mojito Wallet: New browser extension UI. 🟩 JavaScript SDK: Improved Node.js & React Native support. 🟩 Developer Docs: Added practical SDK examples. 🟩 Research: Published 3 new technical papers. Read all about it here: https://www.mintlayer.com/blog/mintlayer-development-update-2026-july/

🔥74👍2😁2

20 Jul 2026, 12:40 UTC703 views13 reactionsread 12 August 2026

🚀 Mintlayer Core v1.4.0 is out Ledger hardware wallet support (beta) You can now create, recover and open a Mintlayer wallet directly on a Ledger device, alongside the existing software and Trezor options. Requires Ledger app v1.0.0. Consensus tightening Token metadata URI changes now follow the same character rules as token creation, and zero-amount token transfers and burns are rejected. This activates through a

🔥10😁21

17 Jul 2026, 12:54 UTC597 views12 reactionsread 12 August 2026
Photo

🟩15,000+ attendees from 130+ countries 🟩 200+ star speakers 🟩 200+ leading companies and Tier 1 funds 🟩 Debut of AI Future Forum 🟩 Hundreds of side events 🗓️ December 1–2, 2026 The Mintlayer team will be attending one of the region's leading blockchain events, Blockchain Life 2026. If you're attending too, get 10% off your ticket with the code: mintlayer Get it now!

7🔥5

10 Jul 2026, 12:54 UTC708 views22 reactionsread 12 August 2026
Photo

We are proud to see our Co-founder join the stage as one of the leading voices at the Nobel Laureates Assembly on Artificial Intelligence and Nuclear War. As AI continues to reshape our world, the conversation must go beyond what machines can do. It must focus on how we preserve humanity, responsibility, and ethical progress. At Mintlayer, we have always believed that the future of technology must be built with inn

10🔥7👍3😁2

4 Jul 2026, 09:50 UTC748 views16 reactionsread 12 August 2026

Mintlayer Development Update: June This month the team focused on: • Core: consensus and P2P networking security improvements for a more resilient network. • Mojito Wallet: refreshed UI with cleaner design and better navigation. • Documentation: expanded and easier to navigate for builders. • JavaScript SDK: fixed a bug affecting certain wallet configurations, improving reliability. Read the full update: https://ww

🔥104😁2

25 Jun 2026, 15:11 UTC844 views8 reactionsread 12 August 2026

50 minutes to go! 🚨 https://twitter.com/i/spaces/1AGRnnVvwwDGl

🔥4😁21👍1

25 Jun 2026, 12:41 UTC763 views8 reactionsread 12 August 2026
Photo

Save the time: 8PM GST Our Co-founder Anna joins Fractionalized World as a Guest Speaker to talk all about Tokenizing Everything! https://twitter.com/i/spaces/1AGRnnVvwwDGl

5😁2🔥1

22 Jun 2026, 12:47 UTC776 views13 reactionsread 12 August 2026
Photo

https://x.com/mintlayer/status/2069039245831086242?s=20

5🔥4😁4

3 Jun 2026, 16:41 UTC≈1,160 views25 reactionsread 12 August 2026
Photo

TLDR: May Development Update 🔹 Core protocol (v1.3.1): Released with improvements to transaction processing, validation, networking reliability, and overall node stability. 🔹 Wallet fixes: Resolved issues around order command conflicts, cold wallet input commitments, and mempool access errors in cold mode. 🔹 Documentation: Ongoing improvements to the Mintlayer docs portal to make developer onboarding and ecosystem

🔥117👍6😁1

28 May 2026, 09:50 UTC981 views22 reactionsread 12 August 2026
Photo

Our Co-founder Anna will be joining an X Space session TODAY to speak about how AI agents can now hold wallets, move money, trade on-chain, and even drain themselves through prompt injection attacks! 📍 2:00 PM UTC | 6:00 PM GST Set a reminder now ⬇️ https://x.com/i/spaces/1yxBeePbAjoJN?s=20

🔥95😁5👍3

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

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

BOSS FIGHTERS - shoot, smash, win!
@PlayBossFighters_ann · 153,423
Telegram ranks this channel #6 of 82 here — alongside 81 others — read 18 August 2026
peaq
@peaqnetwork · 43,097
Telegram ranks this channel #7 of 94 here — alongside 93 others — read 28 August 2026
Casper Official Announcements
@casperofficialann · 36,197
Telegram ranks this channel #10 of 81 here — alongside 80 others — read 1 September 2026
Portal to Bitcoin Announcements
@portaltobitcoin_announcements · 88,107
Telegram ranks this channel #12 of 88 here — alongside 87 others — read 1 September 2026
MultiversX - Announcements
@MultiversXAnn · 301,582
Telegram ranks this channel #13 of 87 here — alongside 86 others — read 15 August 2026
Lumia News
@lumia_news · 106,808
Telegram ranks this channel #35 of 87 here — alongside 86 others — read 15 August 2026
The Crypto Gateway
@TheCryptoGateway · 89,581
Telegram ranks this channel #64 of 90 here — alongside 89 others — read 17 August 2026
📣 Vinu News
@Vinu_News · 145,376
Telegram ranks this channel #75 of 88 here — alongside 87 others — read 15 August 2026

This channel appears in 8 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Mintlayer Announcements” (@mintlayer_announcements), 4,536 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/mintlayer_announcements.

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.