Channel
@ugblockchain
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
511subscribers
+0 since we began measuring on 13 November 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004402999005 |
|---|---|
| Type | Channel |
| Username | @ugblockchain |
| Description | 区块链和Web3.0领域领先的智库型信息平台 |
| Created | Between 1 June 2026 and 30 September 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 November 2026 |
| Last confirmed live | 13 November 2026 |
| Measurements held | 2 |
| On Telegram | t.me/ugblockchain |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Nov 2026, 15:22 | 511 | no change |
| 13 Nov 2026, 14:47 | 511 | first reading |
20 posts held, back to 13 November 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.
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.
| Window | Rolling 30 days · latest post in window 13 November 2026 |
|---|---|
| Posts held | 20 (13 November 2026 – 13 November 2026) |
| Views total | 20 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Nov 2026, 15:22 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 13 November 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.
Telegram’s own ‘edited’ marker: 0 of 20 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
#快讯 Coinbase CEO Brian Armstrong 在其 X 账号发文称，Coinbase Pro 即将上线。Armstrong 称，Coinbase 多年来一直推动股票永续合约以合规方式落地美国，并感谢 SEC 主席 Atkins 与 CFTC 主席 Selig 推进相关产品。安全方面，Coinbase 托管的加密资产超过 99% 存放在冷钱包，与全球最大银行中的 7 家合作，在全球持有 80 余张牌照。Armstrong 还表示，预计到 2030 年 AI 代理将处理 3 万亿至 5 万亿美元的交易，Base 上代币化股票的交易量已超过 50 亿美元。 #监管 #AI
#快讯 据 BitGo 最新披露，Unocoin 账户已于 11 月 6 日被冻结，冻结措施按预期生效。BitGo 审查发现，Unocoin 钱包近期的转出交易由 Unocoin 持有的用户密钥和备份密钥签名，BitGo 没有参与，交易从外部直接广播上链。Unocoin 钱包采用 2-of-3 多签自托管方案，Unocoin 持有其中两把密钥，BitGo 只持有第三把，且这把密钥从未被使用。BitGo 表示，其系统未因此事件遭入侵，其他客户未受影响。有关 Unocoin 用户资金的问题，应向 Unocoin 咨询。 今日稍早，Unocoin称BitGo多签备份机制疑遭利用，正调查资产损失。 #安全事件
#快讯 据Whale Alert监测，北京时间22:42，USDC Treasury再次铸造2.5亿枚USDC，价值约2.5亿美元。此前在北京时间21:45，USDC Treasury已铸造2.5亿枚USDC，近一小时内累计新铸造5亿枚。 #稳定币
#快讯 据币安行情，美股三大指数盘中集体下跌，道指日内跌幅达0.04%，纳指日内跌幅达1.09%，标普500指数日内跌幅达0.50%。 #美股
#快讯 币安行情显示：英伟达(NVDA.O)回吐盘初涨幅，转跌1.3%。 #美股
#快讯 币安行情显示：人工智能芯片制造商Cerebras Systems股价大涨17%，为8月以来最大涨幅。 #AI
#快讯 据Investing.com报道，美国银行全球研究把2027年1月加息25个基点纳入预测，现在预计美联储将在今年12月、明年1月和3月各加息25个基点，联邦基金利率峰值升至4.50%–4.75%。此前美银预计按季度再加息两次，峰值为4.25%–4.50%。美银经济学家Aditya Bhave表示，10月CPI公布后，美联储在通胀问题上显得更加落后，已不能再按季度节奏加息。 #宏观
#快讯 据币安行情，美股开盘，道指涨0.33%，纳指跌0.01%，标普500指数涨0.27%。 #美股
#快讯 香港交易所(00388.HK)宣布，将于12月14日推出新的数字支付方案，便利结算参与者在衍生产品市场收市后交易时段支付预缴按金。这次新服务是基于香港交易所与香港金管局的合作计划推出的，探索使用数码港元支付收市后交易时段的预缴按金。新方案推出后，合资格的香港期货结算有限公司结算参与者可选用此数字支付方式，于下午5时至凌晨1时30分提交预缴按金申请，以便有关款项可用于相应的收市后交易时段。延长后的支付时段将作为现有支付安排的补充，让结算参与者可于一般银行营业时间以外，更灵活地管理其以资本额厘定的持仓限额使用情况。 #新闻
#快讯 在 DeepSeek App（含网页端）的对话服务中，联网搜索、文件输入、阅读链接、语音交互及安全等能力与模型推理相互配合，构成了用户熟悉的对话体验。而开发者如果想要在应用中实现类似功能，除接入原有 DeepSeek API 外，往往还需耗费大量精力去对接外部工具、处理调用衔接。 今天，我们正式开放这套全家桶应用 API：在原有 API 中开启对应参数，即可获得深度思考搜索、文件输入等对话功能；语音及相关底层能力也已开放独立接口（含 OCR、ASR、TTS 等），支持单独或组合调用。开发者可以在自己的应用中轻松实现复杂的对话功能，甚至 1:1 复刻出完整的 DeepSeek App。 #新闻
#快讯 据Upbit公告，Upbit将于12月14日15:00（韩国时间）终止MANTRA（MANTRA）韩元、BTC和USDT交易对的交易支持，出金支持至2027年1月13日。Upbit称，MANTRA曾发生原因未查明或未修复的黑客等安全事件，已于8月21日被列为警示代币。经进一步审查，Upbit认定指定事由仍未消除，因此决定终止交易支持。 #安全事件 #稳定币 #比特币
#快讯 据The Information报道，马斯克旗下AI团队裁撤了Grok Imagine视频生成团队约60名员工。该团队此前几个月已经裁过员。Grok Imagine是聊天机器人Grok内置的图像和短视频生成功能。xAI于2026年2月并入SpaceX，此后AI业务重组为四个方向：Grok Main and Voice、编程工具、Imagine和Macrohard。合并以来，多名联合创始人和资深研究员已离职。2025年9月，xAI曾裁撤约500名数据标注员。官方未公布视频功能的后续计划。 #AI
Showing the 12 most recent of 20 posts we hold for @ugblockchain. 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 2 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.
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.
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 November 2026 — this entry's latest reading, not the date you are reading this.
“区块链信息平台 | 加密货币” (@ugblockchain), 511 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/ugblockchain.
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.