Channel
@pantherprotocolann
On this record: Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
1,204subscribers
+4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001273512663 |
|---|---|
| Type | Channel |
| Username | @pantherprotocolann |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 10 September 2026 |
| On Telegram | t.me/pantherprotocolann |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Sept 2026, 14:02 | 1,204 | -4 |
| 5 Sept 2026, 11:15 | 1,208 | +1 |
| 1 Sept 2026, 20:34 | 1,207 | +3 |
| 24 Aug 2026, 08:34 | 1,204 | +4 |
| 18 Aug 2026, 03:42 | 1,200 | +2 |
| 14 Aug 2026, 17:14 | 1,198 | -3 |
| 7 Aug 2026, 15:58 | 1,201 | +1 |
| 7 Aug 2026, 01:16 | 1,200 | first reading |
20 posts held, back to 1 June 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.
97 reactions across 20 posts, in 4 distinct kinds. The most used accounts for 88.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 86 | 88.7% | |
| ❤ | 5 | 5.15% | |
| 💯 | 4 | 4.12% | |
| 🏆 | 2 | 2.06% |
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 97 reactions 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 1 June 2026 to 2 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.
Stablecoins have become a cornerstone of DeFi, but almost every transfer is still completely transparent. Our latest blog explains why confidential stablecoin transfers matter and how Panther's Multi-Asset Shielded Pool (MASP) enables programmable privacy—allowing operators to define their own compliance and access requirements while using existing stablecoins within the DeFi ecosystems where liquidity already exist…
🔥3
Panther’s latest DAO proposal, PIP-40, has passed! The DAO voted in favor of minting and releasing an additional 4,000,000 $ZKP to the V1 Privacy Rewards contract, while simultaneously reducing the mainnet reward emission rate to ensure that privacy rewards remain available for a substantially longer period and to reduce unnecessary token emissions into the market. Onwards!
🔥4
PIP-40 is now LIVE for voting! This proposal authorizes the minting and release of an additional 4,000,000 $ZKP to the Privacy Rewards contract and sets the mainnet privacy reward emission rate to approximately 16,000 $ZKP per day. The objective of this proposal is to restore mainnet's privacy reward distributions while aligning ongoing emissions more closely with the protocol's usage. Check out the proposal and V…
🔥3
Panther’s next DAO proposal, PIP-40, will likely go live tomorrow. $ZKP holders can only vote with the tokens they hold in their own wallets, and not with those deposited in Panther’s shielded pool, so be prepared and cast your vote later this week!
💯4
The PIP-40 draft has been shared on the Panther forum today! This proposal authorizes the minting and release of an additional 4,000,000 $ZKP to the V1 Privacy Rewards contract while simultaneously reducing the mainnet reward emission rate to better reflect the protocol’s current TVL. The objective of this proposal is to ensure that privacy rewards remain available for a substantially longer period while reducing u…
🔥4
Dear Panther community, Today, we are sharing the latest update on what has been worked on this week. This week’s update mostly focuses on Panther’s Base deployment: ✅ The voucher update has been implemented on Polygon and Base, per PIP-39. ✅ The dev team’s currently working on enabling internal MASP transfers on Base. ✅ The latest dApp fixes on Base are currently being tested and will be refined if needed. Other…
🔥6❤1
Panther’s latest DAO proposal, PIP-39, has passed! The recharger voucher reserve will be increased to 50,000 PRP, and the account activation voucher reserve to 1,000,000 PRP. The internal MASP transfers will be enabled on Panther’s Base deployment with a $25,000 daily limit. Thanks to everyone who voted! Onwards!
🔥2
PIP-39 is now LIVE for voting! This proposal introduces a parameter change to vouchers across both the Polygon and Base deployments and re-enables the internal MASP transfers on Base. The voucher parameter changes are intended to make both voucher systems last much longer than before under current usage patterns. Check out the proposal details and VOTE: https://snapshot.org/#/s:pantherprotocol.eth/proposal/0x3b43e…
🔥7
Panther’s next DAO proposal, PIP-39, will likely go live tomorrow. $ZKP holders can only vote with the tokens they hold in their own wallets, and not with those deposited in Panther’s shielded pool, so be prepared! LFG
🔥7❤1
The PIP-39 draft has been shared on the Panther forum today! This proposal introduces a parameter change to vouchers across both deployments (Polygon and Base) and re-enables internal MASP transfers on Base. The voucher parameter changes are intended to make both voucher systems last much longer than before under current usage patterns. Check out the complete proposal draft here: https://forum.pantherprotocol.io/t/…
🔥5
Maximal Extractable Value (MEV) costs users hundreds of millions of dollars annually across blockchain networks, often worsening the overall UX in DeFi. On this blog, we explain how Panther mitigates the negative effects of MEV through its privacy-preserving infrastructure. https://blog.pantherprotocol.io/how-panther-protocol-shields-users-from-mev-privacy-as-a-powerful-defense/
🔥5
We are going live tomorrow at 5:00 pm UTC on Web3 Global with Access Protocol, GVNR, Spark, Alvey, Shido Network, Shift, Kaspa, and multiple speakers from other projects to discuss real-world adoption and payments in crypto. https://x.com/web3globalmedia/status/2072734497070629200?s=20 We hope to see you there!
🔥6
Showing the 12 most recent of 20 posts we hold for @pantherprotocolann. 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.
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.
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.
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 10 September 2026 — this entry's latest reading, not the date you are reading this.
“Panther Protocol Announcements” (@pantherprotocolann), 1,204 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/pantherprotocolann.
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.