Channel
@muur_posts
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
8,147subscribers
-104 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001993180528 |
|---|---|
| Type | Channel |
| Username | @muur_posts |
| Created | Between 1 October 2023 and 30 April 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/muur_posts |
Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 12 September 2026 and assigned it the closest of 31 fixed categories, at 95% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 09:37 | 8,147 | -13 |
| 15 Sept 2026, 05:57 | 8,160 | -16 |
| 11 Sept 2026, 16:20 | 8,176 | -15 |
| 6 Sept 2026, 19:56 | 8,191 | -9 |
| 2 Sept 2026, 03:04 | 8,200 | -4 |
| 26 Aug 2026, 20:56 | 8,204 | -2 |
| 24 Aug 2026, 00:33 | 8,206 | -9 |
| 20 Aug 2026, 12:42 | 8,215 | -5 |
| 17 Aug 2026, 14:53 | 8,220 | -14 |
| 14 Aug 2026, 02:15 | 8,234 | +1 |
| 10 Aug 2026, 17:03 | 8,233 | -18 |
| 7 Aug 2026, 04:45 | 8,251 | no change |
| 7 Aug 2026, 04:33 | 8,251 | first reading |
131 posts held, back to 4 August 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 21 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 131 posts for this entry, the most recent from 28 August 2026. An engagement rate over an empty window would be a number about nothing.
396 reactions across 129 posts, in 10 distinct kinds. The most used accounts for 62.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 249 | 62.9% | |
| 👍 | 124 | 31.3% | |
| 🔥 | 13 | 3.28% | |
| 😭 | 4 | 1.01% | |
| 💔 | 1 | 0.253% | |
| 💩 | 1 | 0.253% | |
| 😁 | 1 | 0.253% | |
| 😘 | 1 | 0.253% | |
| 🙈 | 1 | 0.253% | |
| 🤮 | 1 | 0.253% |
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 129 of the 131 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 396 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 131 most recent posts we hold, published 4 August 2026 to 28 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.
Fed chair Kevin Warsh's Jackson Hole speech is the key risk event ahead – Link Traders are positioning for Warsh's Jackson Hole address at 22:00 Beijing time / 14:00 UTC Aug 28. July PCE is still elevated at 3.7% y/y, Fed officials are split on how restrictive rates are, and futures price about a 36% chance of a September hike. Matters because: a hawkish surprise could hit crypto and other risk assets, while a neut…
❤1👍1
NUVA brings nvPRIME-backed USDC lending to Morpho through RockawayX – Link A while ago, I wrote that one of my biggest issues with RWAs is that bringing assets onchain means almost nothing without practical utility across DeFi. NUVA’s new RockawayX-curated vault is a step toward solving that. Users can deposit USDC and lend against nvPRIME collateral for a target return of 7.5%, with rewards distributed through Mer…
👍2
Fed's Jackson Hole speech looms as key catalyst for rate path – Link Fed Chair Kevin Warsh speaks at Jackson Hole this week (Aug 27–29). Markets are watching whether he frames above-target inflation as transitory or demand-driven, with CME pricing meaningful odds of a September hike instead of a cut. Matters because: A hawkish tone could pressure BTC and risk assets, while a dovish read may reinforce the recent ral…
Grayscale's Zcash ETF debuts on NYSE Arca, then cools – Link Grayscale's spot Zcash ETF began trading Aug 25 with roughly $314M in initial assets and a 2.5% sponsor fee. ZEC then pulled back about 8% from its 8-year high near $880, with price near $780. Matters because: The launch validated institutional demand for privacy-asset exposure, but the pullback suggests near-term upside may be capped until new demand eme…
❤2
SEC submits crypto custody rule overhaul to White House for review – Link The SEC sent a proposal to the White House OMB on Aug 25 aimed at modernizing how investment advisers and funds custody digital assets. The proposal would remove outdated requirements, but still needs OMB review, an SEC vote, and a public comment period. Matters because: If finalized, the change could reduce custody friction for institutions …
👍2
SEC proposes first crypto-specific offering framework ("Regulation Crypto Assets") – Link The SEC proposed tailored exemptions for non-security crypto offerings, including a $5M startup exemption, a $75M annual fundraising exemption, and a safe harbor from "investment contract" classification once a project is sufficiently decentralized. A 60-day comment period is now open. Matters because: It may signal a shift aw…
👍3
Treasury expands long-bond buyback program, sparking "debasement trade" and BTC rally past $78K – Link The U.S. Treasury raised its long-dated bond repurchase limit from $2B to at least $4B per operation for Sept 9–Nov 4. Markets read it as a dovish signal on fiscal stress, with the dollar weaker and gold and Bitcoin rallying; BTC gained roughly 23% on the week and broke above $78,000. Matters because: Risk assets …
👍4
BlackRock slashes IBIT in-kind conversion minimum to $1M – Link BlackRock cut the minimum for in-kind BTC-to-IBIT share conversions by 96%, from $25M to $1M. Cumulative in-kind conversions have topped $5B, up from $3B in October. Matters because: Lower access barriers may move more wealth from self-custody into regulated ETF wrappers and deepen ETF-linked liquidity over time.
👍5
US Treasury sanctions Iran's digital asset industry for the first time – Link The US Treasury/OFAC expanded its "Economic Outcast" sanctions program to explicitly cover Iran's digital asset industry. The action targets exchanges, OTC desks, payment processors, and wallet addresses tied to IRGC-linked actors as the Iranian rial hit a historic low near 202,000 IRR/USD. Matters because: It raises compliance risk for a…
👍3
Bitkub co-founder wallet moves 34,000 ZEC ($26.1M) to Hyperliquid, swaps for BTC – Link A wallet linked to Bitkub co-founder Sakolkorn Sakavee transferred roughly $26.1M in ZEC to Hyperliquid and swapped into 238 BTC over the past day. Matters because: Large identifiable-holder rotation out of a recently pumped asset into BTC may suggest profit-taking and a preference for the more liquid, ETF-backed asset.
❤4
Mina protocol confirms "Mesa" mainnet upgrade for September 3 – Link Mina Protocol announced its Mesa upgrade, scheduled for mainnet on September 3, 2026. The update brings faster blocks, higher zkApp capacity, and a smoother path for future protocol upgrades. • 90-second block times • Increased zkApp throughput • Streamlined future protocol upgrade path Matters because: Faster blocks and more zkApp throughput cou…
❤4👍1
Grayscale advances Zcash spot ETF filing, seeking NYSE Arca listing under "ZCH" – Link Grayscale's fifth amended SEC filing renames the product "The Zcash ETF" with a 2.5% management fee, Coinbase Custody as custodian, and BNY Mellon as transfer agent. It would convert Grayscale's existing $260M+ Zcash Trust. Matters because: This is a concrete regulatory step that may signal broader ETF issuer appetite beyond BTC …
❤3
Showing the 12 most recent of 131 posts we hold for @muur_posts. 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.
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.
Named by 3 registered channels — 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.
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.
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 5 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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“Stacy in Dataland (´⊙~⊙`)” (@muur_posts), 8,147 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/muur_posts.
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.