Channel
@jiamihuobishenchao
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
44,851subscribers
-391 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002941821980 |
|---|---|
| Type | Channel |
| Username | @jiamihuobishenchao |
| Created | Between 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 32 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/jiamihuobishenchao |
International news — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 31% 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 |
|---|---|---|
| 18 Sept 2026, 00:57 | 44,851 | -19 |
| 15 Sept 2026, 17:18 | 44,870 | -11 |
| 14 Sept 2026, 01:21 | 44,881 | -11 |
| 12 Sept 2026, 09:57 | 44,892 | -20 |
| 10 Sept 2026, 04:20 | 44,912 | -35 |
| 7 Sept 2026, 00:02 | 44,947 | -32 |
| 4 Sept 2026, 09:38 | 44,979 | -17 |
| 2 Sept 2026, 23:13 | 44,996 | -9 |
| 1 Sept 2026, 21:25 | 45,005 | -8 |
| 31 Aug 2026, 23:26 | 45,013 | -12 |
| 30 Aug 2026, 22:55 | 45,025 | -7 |
| 30 Aug 2026, 02:13 | 45,032 | -9 |
| 29 Aug 2026, 02:55 | 45,041 | -7 |
| 28 Aug 2026, 00:34 | 45,048 | -9 |
| 26 Aug 2026, 21:37 | 45,057 | -8 |
| 25 Aug 2026, 19:18 | 45,065 | -14 |
| 24 Aug 2026, 18:47 | 45,079 | -13 |
| 23 Aug 2026, 05:38 | 45,092 | -18 |
| 21 Aug 2026, 17:57 | 45,110 | -4 |
| 20 Aug 2026, 13:56 | 45,114 | first reading |
201 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 94 pages of Telegram’s post history, 20 posts per page.
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 11 of 128 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 24 September 2026 |
|---|---|
| Posts held | 201 (4 August 2026 – 24 September 2026) |
| Views total | 18,450 |
| Reactions total | 14 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 24 Sept 2026, 09:33 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.
Lifetime counters from Telegram’s own channel header, read 24 September 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.
19 reactions across 14 posts, in 2 distinct kinds. The most used accounts for 68.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 13 | 68.4% | |
| 👍 | 6 | 31.6% |
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 14 of the 201 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 19 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 201 most recent posts we hold, published 4 August 2026 to 24 September 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.
美国布鲁克林男子因网络钓鱼被判 4 至 12 年监禁 据美国布鲁克林地区检察官办公室，23 岁的布鲁克林男子 Ronald Spektor 因实施网络钓鱼与社会工程诈骗，被判处 4 至 12 年监禁。Spektor 在约一年时间内，冒充 Coinbase 客服，以“账户遭黑客攻击、资产面临风险”为由，诱骗约 100 名美国用户将加密货币转移至其控制的钱包，累计盗取近 1594 万美元。随后，他通过多次兑换、混币服务及加密赌博平台洗钱。他于 9 月 2 日对包括一级洗钱、一级重大盗窃等全部 31 项指控认罪，并被责令没收价值超 50 万美元的现金、加密货币及个人财产，同时需赔偿近 1600 万美元。调查显示，他曾在 Telegram 等平台公开炫耀犯罪所得。
俄罗斯央行允许共同基金投资加密货币相关工具 俄罗斯央行修改共同基金投资规则，允许面向专业投资者的基金投资与数字货币报价挂钩的结算指数。零售共同基金也可配置部分非上市俄罗斯证券及外国证券，包括代币化证券和与加密货币价格挂钩的美国交易所交易基金份额，相关资产投资比例上限为 10%，封闭式基金上限为 20%。
👍1
SEC 代理主席称：为避信誉风险撤回加密诉讼 9 月 24 日，SEC 委员 Mark Uyeda 在最近一次公开会议上披露，美国证券交易委员会（SEC）在 2025 年初撤回了一系列针对加密公司的民事诉讼。Uyeda 曾于 2025 年 1 月至 4 月担任 SEC 代理主席，他解释称，由于机构正计划在规则制定方面进行“180 度”的政策转变，继续执行前任政府授权的案件可能会导致机构在法律立场上前后矛盾，进而损害其在法庭上的公信力。 Uyeda 表示，他不希望看到律师在法庭上坚持旧的立场，随后委员会却发布与之截然相反的司法解释。他指出，当时内部对于这些案件的合法性存在“严重担忧”。此次被撤诉的案件涉及多家大型加密企业，其中包括备受关注的 Kraken、Ripple Labs 以及 Coinbase。此外，报道提到部分批评者将这一行动解读为该行业对美国总统 Donald Trump 2024 年竞选活动提供支持的回报。
哈塞特批评美联储官员近期支持加息言论 要求恢复“独立性” 9月24日，美国白宫国家经济委员会主任哈塞特周三批评近期支持进一步加息的美联储官员，称在核心通胀率已接近2%的情况下，美联储继续收紧政策令人担忧。哈塞特表示，“为什么还要加息”，并质疑部分未由特朗普任命的官员近期发表支持更多加息的言论。哈塞特称，美联储主席沃什正在管理一个“高度政治化的美联储”，恢复美联储独立性是其面临的重要任务。哈塞特还批评，美联储一些高层官员即使离开原来的领导岗位，仍继续留在美联储任职。他点名鲍威尔和巴尔，认为这种情况与过去美联储领导层更替后的惯例不同。最近多名美联储官员均释放鹰派信号。巴尔表示，可能需要进一步加息以推动通胀回到2%目标；柯林斯和穆萨莱姆也表示支持进一步加息。美联储最新经济预测显示，16名官员预计今年至少还将加息一次。
成都“天府词元智造工厂”算力公共服务平台正式发布 9月23日，“天府词元智造工厂”算力公共服务设施平台正式发布，该平台由成都市联合中国电信打造，定位为成都算力调度与Token枢纽运营的核心载体。据悉，该平台集算力调度、模型适配、词元计量、数据流通、应用赋能、跨境安全于一体的算力公共服务平台，将全面整合全市算力与Token资源，推动算力资源“像水电一样”便捷可得、按量计费；以Token为统一计量基准，贯通“申领—使用—核销—兑付”全流程闭环，对接成都市算力券、词元券政策体系，简化券类申领、使用、兑付流程。
美司法部为特朗普禁三家媒体辩护：白宫采访权限“是特权，而非权利” 9 月 23 日，美国司法部敦促一名联邦法官不要阻止特朗普全面禁止三家新闻机构进入白宫的决定，并表示：“进入白宫的权限是一项特权，而不是一项权利。”该政府机构在一份新的法庭文件中表示，特朗普周五突然禁止 MS NOW、CNN和 Politico 进入白宫，是出于对国家安全的担忧。 这份文件提交之际，美国华盛顿特区联邦地区法院定于周三举行电话听证会。法官蒂莫西·凯利（Timothy Kelly）将听取这三家媒体的律师陈述。三家媒体已提起诉讼，要求法院发布禁令，阻止特朗普继续实施这一禁令。
俄罗斯拟建立加密货币综合监管框架，非法经营或面临刑责 9 月 23 日，俄罗斯副财政部长伊万·切贝斯科夫表示，俄罗斯将推动建立透明、合法的加密货币市场。该国约有 2000 万名加密货币用户，居民相关投资总额约 3.7 万亿卢布，日均交易规模约 500 亿卢布。 非银行加密货币兑换商的最低自有资金要求已降至 1500 万卢布；自 2027年 7月 1 日起，未经许可组织加密货币流通可能面临刑事责任，但个人处置自有加密货币不在此列。俄罗斯还将要求税务居民申报监管体系外的加密货币交易，并研究发行本土稳定币的可行性。
CFTC：警告“提及市场”预测合约存在较高操纵风险 美国商品期货交易委员会（CFTC）市场监管部门发布公告称，以特定人物是否提及某些词语或出席活动为结算依据的预测合约，面临较高的市场操纵风险，仅在有限情况下可由指定合约市场上线。CFTC 建议相关平台评估能够影响合约结果的个人是否受到法律、职业、合同、信义或保密义务约束，并采取主动交易规则及风控措施防范操纵。
贝莱德：智能体机器支付，稳定币为最优结算工具 传统支付网络（ACH、银行卡）在高频、亚美分小额、不间断机器交易场景存在短板，存在开户门槛高、手续费不经济、结算时效限制。x402、ACP、MPP 等新兴 Agent 支付协议，可配合稳定币完成无需人工干预的机器‑机器交易。 数据显示，2025 年调整后稳定币交易规模超“11 万亿美元”，已经达到 Visa、万事达卡同一量级；2020—2025 年复合增速 80%，远高于 ACH 网络 8.5% 增速。随着全球各地稳定币监管框架落地，稳定币将承接 AI 智能体大量微支付场景。 与此同时，报告提出算力容量可以做成标准化链上凭证，实现算力的融资、质押、可编程交割；未来有望出现算力期货等标准化衍生品。AI Agent 可直接通过 x402 等协议按需采购、自动结算算力资源。Stripe 收购 OpenRouter 被视作算力调度 + 可编程支付融合的早期行业信号。
纽约联储官员：货币政策工具箱运作良好，国库券购买视市场需要而定 9 月 23 日，纽约联储系统公开市场账户经理佩尔利表示，美联储的货币政策控制工具箱继续非常有效。“我们保持了非常强的利率控制，将准备金维持在充足区间，我们的国库券购买也顺利运行，”佩尔利称。他还表示，美联储近期向金融体系增加流动性的行动（目前处于暂停状态）并非预设路径，暗示如果美联储认为需要提振市场流动性，可能会再次购买国库券。他还表示，所谓的准备金管理购买（RMP）国库券将根据市场流动性需求进行调整。
Visa 合作伙伴 Reap 拟推墨西哥比索稳定币，探索 24/7 链上外汇 Visa 合作伙伴、香港金融科技平台 Reap 创始人 Daren Guo 表示，Reap 计划在其卡片、跨境支付和资金管理产品中新增墨西哥比索稳定币，并正在探索港元、欧元、韩元及日元稳定币，以支持全天候链上外汇结算，降低跨境成本。Reap 是 Visa 在香港和墨西哥的主要发卡机构成员（VPIM），由 Kraken 母公司 Payward 所有，可在自有 BIN 上发卡，并称能支持 100 多个市场的合作伙伴。Guo 表示，公共区块链持续运行，但全球外汇仍依赖银行营业时间、代理行和可能耗时数日的结算，新兴及跨境市场中部分货币走廊的转账费用高达 5% 至 7%，而目前稳定币支付中近 99% 以美元计价。该公司正将稳定币结算整合进卡片、跨境支付、资金管理及合规风控等更广泛的产品体系。Reap 表示，2026 年上半年卡片和支付量同比增长 33%，202…
欧洲央行：反对将稳定币储备强制存为银行存款 欧洲央行及欧盟各国央行在就加密资产监管法规 MiCA 征求意见时表示，反对要求主要稳定币发行方将至少 60% 储备资产以银行存款形式持有，理由是这可能让银行暴露于稳定币市场波动，并削弱存款稳定性。央行体系建议改为规定一定比例储备资产必须为 1 个和 5 个工作日内到期的短期资产。同时，央行指出，尽管 MiCA 已生效，未合规的加密企业仍可触达欧盟客户，监管执行面临“重大挑战”，带来投资者保护风险。
Showing the 12 most recent of 201 posts we hold for @jiamihuobishenchao. 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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“TechFlow 深潮 加密货币＆区块链新闻” (@jiamihuobishenchao), 44,851 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/jiamihuobishenchao.
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.