#频道互推 #群组推荐 极客分享2.0 [震撼回归] (NSFW)mmd分享 奇趣吃瓜 App Store 限免应用 Fang的资源分享群 来一点医学科学前沿 财联社VIP文章分享 今日有羊毛 115影视资源分享频道 电报频道&群组索引

Channel
加密货币知识库
@jmhbzsk
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
11,972subscribers
+178 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1002276973739 |
|---|---|
| Type | Channel |
| Username | @jmhbzsk |
| Description | 分享加密货币相关的网站、软件资源以及加密货币相关的知识与资讯。 欢迎加入群组 @jmhbtalk 讨论 商务合作联系: @kklove |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 17 August 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 17 August 2026 |
| On Telegram | t.me/jmhbzsk |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Aug 2026, 19:53 | 11,972 | +19 |
| 16 Aug 2026, 17:04 | 11,953 | +26 |
| 15 Aug 2026, 03:57 | 11,927 | +22 |
| 13 Aug 2026, 18:18 | 11,905 | +23 |
| 12 Aug 2026, 15:24 | 11,882 | +19 |
| 11 Aug 2026, 15:26 | 11,863 | +12 |
| 10 Aug 2026, 13:03 | 11,851 | +17 |
| 9 Aug 2026, 16:03 | 11,834 | +19 |
| 8 Aug 2026, 18:31 | 11,815 | +3 |
| 7 Aug 2026, 19:43 | 11,812 | +16 |
| 6 Aug 2026, 17:00 | 11,796 | +2 |
| 6 Aug 2026, 09:34 | 11,794 | first reading |
Engagement
26 posts held, back to 19 July 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 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 12.6%
- avg views ÷ 11,972 subscribers
- Avg views / post
- 1,510
- 25 posts measured
- Reaction rate
- 0.128%
- reactions ÷ views · ER floor
- Posts in window
- 26
- of 26 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 20 of 25 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 16 August 2026 |
|---|---|
| Posts held | 26 (19 July 2026 – 16 August 2026) |
| Views total | 37,644 |
| Reactions total | 40 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Aug 2026, 20:26 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
- Photos
- 612
- Videos
- 7
- Links
- 128
Lifetime counters from Telegram’s own channel header, read 17 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Reaction mix
40 reactions across 18 posts, in 4 distinct kinds. The most used accounts for 87.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 35 | 87.5% | |
| 👍 | 2 | 5.00% | |
| 👏 | 2 | 5.00% | |
| 😐 | 1 | 2.50% |
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 26 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 40reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 26 most recent posts we hold, published 19 July 2026 to 16 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
⏺ 加密货币知识之——交易纪律 加密货币市场具备24小时无休、高波动性以及受宏观和微观事件双重驱动的特点。在这个市场中,长期的盈利往往不取决于某一次的暴击,而是取决于在极端行情下能否存活。 对于高频参与现货与衍生品合约的交易者而言,建立并严格遵守交易纪律是跨越“赌徒”与“专业交易员”鸿沟的唯一途径。以下是几个核心的加密货币交易纪律: 1. 仓位与保证金的绝对防御 在带有杠杆的合约市场中,风险管理永远先于利润计算。 动态保证金率监控: 必须时刻关注账户的维持保证金率。当面临深度的浮亏时,纪律要求你不能盲目扛单,而是应该果断执行部分平仓(减仓),以释放可用保证金并推远强平价格,保全核心本金。 限定单笔最大亏损(Risk Per Trade): 无论技术形态看起来多么完美,单笔交易的最大潜在亏损不应超过总资金的 1% 到 3%。 拒绝情绪化补仓: 永远不要在亏损的仓位上加仓以试图摊薄成本,除非这是你在开仓前就已经制定好的网…
❤3
✈️ 机场推荐——维云云 ▪️ 5.8元/月 300G ▪️ 不限制客户端数量 ▪️ 不限制节点速率 ▪️ 支持大流量下载 ▪️ 解锁流媒体 🧀 KK亲测好用 ➡️ 注册使用 ------------------------------------------- 🏷 #KK推荐
⏺ K线如何区分强阻力与弱阻力? 区分K线上的强阻力与弱阻力,核心在于评估该价格区域的筹码沉淀量、多空力量的耗竭程度以及多维度的技术共振。 以下是判断阻力强弱的几个关键分析维度: 1. 量价行为与筹码分布 (量价逻辑) 强阻力(派发与套牢): 当价格触及某一水平时,伴随巨量成交但价格滞涨。在威科夫(Wyckoff)逻辑中,这通常对应着抢购高潮(BC)或上冲回落(UT)的派发区间。巨量意味着主力在此处释放了大量筹码,形成了庞大的套牢盘,未来价格每次接近该区域都会面临强大的解套抛压。 弱阻力(无供应回落): 价格上涨至某一高点后缩量回落。这仅仅是自然的回调,说明该区域并没有发生激烈的筹码换手,缺乏实质性的套牢盘,再次上攻时较容易被突破。 2. 动能衰竭与多周期共振 强阻力: 结构性的高点如果叠加了动能耗竭信号,阻力会呈指数级增强。例如,价格触及前期高点附近时,日线或4小时级别恰好走出了DeMark序列(TD Sequent…
👍2
https://b23.tv/3qun5Wf CIA社区的博主测评。还是很有参考价值的。 有想要加入CIA社区的可以私聊我 @kklove
🆔 软件名称:Opptrix ⭐️ 软件功能:AI股票分析 ➡️ 支持平台:#Windows #macOS #Linux 📁 软件简介:一款开源的全球多市场投研数据助手,主要用于聚合公开或授权数据源,辅助投资者和研究人员进行数据查询、信息整理和投研分析。 支持A股、美股、港股、日股、韩股和加密货币等多个市场,并提供自然语言提问功能,通过大模型调用127个投研工具,将结构化数据整理为中文可读报告。 ⬇️ 软件下载:点击下载
❤3
1️⃣ 交易所: ① 币安(20%) ② Bitget(20%) ② weex(40%) 🔤 聚合群: CIA社区 3️⃣ 冷钱包: Tangem 4️⃣ K线指标:tradingview 5️⃣ 机场: 魔法云
#频道互推 #群组推荐 翻墙世界的梯子 山茶花の机场频道|免费机场推荐 趣味播报 影视软件 电视 TVBox 影视直播app分享 999感冒灵‖机场测评 TG宝藏频道-发现更多新频道 国产电视剧频道(每日更新) 频道藏馆 万象拾珍|全网资源合集 电报频道&群组索引
❤1
⏺ K线知识之——仙人指路 在K线技术分析中,“仙人指路”是一种经典的看涨试探性K线形态。它通常出现在交易标的阶段性底部、拉升初期或上升波段的中期。 它的核心逻辑是:主力资金在正式向上发起总攻前,先在盘中向上猛打一波,测试上方的抛压阻力,随后顺势回落。这根K线留下的长长上影线,就像仙人伸出的手指,提前指明了未来价格即将向上突破的方向。 形态特征 要确认一根K线是否为潜在的“仙人指路”,通常需要满足以下四个技术特征: 长上影线: 拥有非常长的上影线,长度通常是K线实体部分的两倍甚至更长,上影线越长往往试探意味越浓。 微小实体: 开盘价与收盘价相近,实体部分很小。小阳线或小阴线皆可,但通常收盘时仍会保持微幅上涨(例如1%-3%左右的涨幅)。 无下影线或极短: 几乎没有下影线,说明下方支撑强劲,空头没有向下打压的空间。 温和放量: 当天成交量通常会有所放大,代表有资金在盘中积极参与,但绝不能是极端的历史天量。如果是极端巨…
❤3
Photo, posted without a caption
❤2
好久没看到军长的喜报了,看看最近军长是不是又支棱起来了
⏺ 金融知识之——夏日淡季 夏日淡季 通常指在夏季(尤其是北半球的 7 月和 8 月),由于天气炎热、人们集中休假等因素,导致某些行业或市场出现活跃度下降、需求减少、成交量萎缩的周期性现象。 在交易市场中,夏日淡季是一个非常经典的现象,华尔街甚至有一句著名的交易谚语:"Sell in May and go away"(五月清仓离场)。 机构资金缺席:欧美的机构投资者、大型基金经理和做市商通常会在 7 月至 8 月集中休长假。主力资金的离场导致市场整体流动性和深度大幅下降。 横盘与区间震荡:由于缺乏足够的资金去推动趋势性行情,市场往往会陷入漫长的无序波动或缩量阴跌。从技术面来看,这段时间经常会演变成数月级别的大型吸筹或派发区间,市场在等待秋季机构资金回归后才会选择真正的突破方向。 波动率骤降与插针风险:夏季的整体波动率指标通常会降至年内低位。但在流动性极差的环境下,少数的抛售或买入指令就可能引发短期的剧烈价格波动(即“插…
❤3
Showing the 12 most recent of 26 posts we hold for @jmhbzsk. 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.
Posts edited after publishing
@jmhbzsk edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
- First edit seen
- 8 August 2026
- Most recent edit
- 8 August 2026
Citation-graph rank
Citation-graph rank — 847,815 of 1,548,671entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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
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.
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 17 August 2026 — this entry's latest reading, not the date you are reading this.
“加密货币知识库” (@jmhbzsk), 11,972 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/jmhbzsk.
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.