Telegram RegisterThe public register of Telegram

Channel

Minter Dev Notifications

@minterdev_en

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

40subscribers

+1 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-1001151507167
TypeChannel
Username@minterdev_en
Created26 March 2020measured — cross-checked against a third-party dataset (TGDataset)
First recorded10 August 2026
Last confirmed live13 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/minterdev_en

Growth

394039.57 August 2026 — 39 subscribers10 August 2026 — 39 subscribers13 August 2026 — 40 subscribers7 August 202613 August 2026
3 measurements spanning 6 days, net +1. 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 39–40 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 13:2640+1
10 Aug 2026, 19:4639no change
7 Aug 2026, 04:3739first reading

Engagement

20 posts held, back to 20 April 2021the 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 13 August 2023. An engagement rate over an empty window would be a number about nothing.

Recent posts

13 Aug 2023, 06:30 UTC66 viewsread 10 August 2026
Forwarded from @webcounters_public

⚙️ Minter TypeScript SDK — The SDK is written in TypeScript with native gRPC transport support (excluding the browser). Suitable for creating WEB 3.0 applications, console and desktop applications. SDK used in Hermes (Web 3.0 multi-wallet application for multirouting trading) Github: https://github.com/counters/minter-typescript-sdk Donation address: Mx72b9ccf56eb6e1a0d00b50dd92314109649033be Validator: Counter (Mp1

29 Jan 2023, 14:08 UTC96 viewsread 10 August 2026
Forwarded from @webcounters_public

💼 Hermes — Web 3.0 multi-wallet application for multirouting trading. • Managing multiple addresses • Multi routing trading that allows you to buy and sell more profitably • Secure storage of private keys (AES encryption) • Support for most operating systems (Windows, Linux, Mac OS, Android, iOS) • No dependence on infrastructure (explorer, gate, API, etc.) • Complete anonymity of use • M

17 Jun 2022, 12:55 UTC≈2,660 viewsread 10 August 2026

🔗 Crosschain Smart Wallets Very soon, a unique and long-awaited feature will go live on Minter—Crosschain Smart Wallet. Crosschain Smart Wallet will allow for calling any smart contract on interconnected networks right within Minter. Key points: 1. Call smart contracts and pay Ethereum or BNB Chain fee with any coin inside Minter. 2. Fully decentralized service. Access to funds is granted exclusively via your priv

27 May 2022, 05:06 UTC72 viewsread 10 August 2026
Forwarded from @webcounters_publicPhoto

Notifications about the buy/sale of coins/tokens and their movements with a filter by volume are now available in the telegram bot @MinterNotificationBot When adding a coin, you choose the type of transaction (buy, sell, or any) and optionally filter by volume and information on moving between wallets. You will receive notifications if: • Exchange transactions (through pools and directly) • Triggering of li

7 May 2022, 06:19 UTC55 viewsread 10 August 2026
Forwarded from @webcounters_publicPhoto

Telegram notification bot @MinterNotificationBot updated. Now it supports all events: • Unbond — Completion of the return of coins from the delegation • StakeKick — ejection of coins from the delegation • OrderExpired — Expiration of the order and return coins to the wallet • Unlock — Unlock coins • StakeMove — Completion of the process of transferring a stake between validators • UpdateNetwork — network

14 Apr 2022, 14:25 UTC63 viewsread 10 August 2026
Forwarded from @webcounters_public

Kotlin SDK update for Minter node v3.0.0 and higher Support for transaction types LOCK_STAKE(37) and LOCK(38), new events: UpdatedBlockRewardEvent, StakeMoveEvent, UnlockEvent and other minor fixes

29 Mar 2022, 22:11 UTC≈4,100 viewsread 10 August 2026

🔗 Minter 3 Testing We’re launching public tests. This version is dedicated to the tokenomics update. Docs github.com/MinterTeam/minter-network-web/pull/51/files?w=1 Sites Explorer: explorer.toronet.minter.network Console: console.toronet.minter.network Bip Wallet: wallet.toronet.bip.to Tx debugger: tx-debug.toronet.minter.network API Node: https://node-api.toronet.minter.network/v2/ Gate: https://gate-api.toronet

31 Jan 2022, 20:01 UTC≈5,230 viewsread 10 August 2026

BIP MegaPool The Minter team is currently developing a solution that would allow the owners of BIP to earn and significantly increase the native coin’s liquidity. The holders will have a unique opportunity to put their coins into a pool with USDT and benefit from fees, farming, and BIP’s growth. They will not even need USDT, which will be supplied by external providers. To create MegaPool, we will set up a multisig

3 Dec 2021, 08:52 UTC137 viewsread 10 August 2026
Forwarded from @webcounters_public

Remote build, sign and send any Minter transaction -> minter-rpc-wallet-js Application cases: - Isolation of the wallet secret phrase from the application - Execution of transactions even if there is no SDK in the application language

30 Nov 2021, 14:43 UTC112 viewsread 10 August 2026

⚠️ We remind all node owners to update the executable files before the block #7683130 (01/12/2021, 15:49:05). After this block, old nodes will halt.

29 Nov 2021, 16:31 UTC104 viewsread 10 August 2026

Minter Node v2.6.0 Release https://github.com/MinterTeam/minter-go-node/releases/tag/v2.6.0

27 Nov 2021, 13:01 UTC79 viewsread 10 August 2026
Forwarded from @webcounters_public

☕️ Updated Kotlin SDK for Minter Major additions in version 2.0-beta: • Support for gRPC transport (speed advantages are ~ 10 * times) • Support for asynchronous methods in several modes (Coroutines, Java Thread) I also published the generated (protoc) Java and Kotlin classes for low-level access via gRPC transport Donation address: Mx72b9ccf56eb6e1a0d00b50dd92314109649033be

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

Republishes

Channels on the register whose posts this channel has forwarded.

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

Names

Channels on the register whose handles appear in this channel's posts.

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.

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

“Minter Dev Notifications” (@minterdev_en), 40 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/minterdev_en.

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.