三菱日联金融集团拟利用区块链推出日本国债即时结算服务 BlockBeats 消息,8 月 13 日,日本最大银行集团三菱日联金融集团(MUFG)计划利用区块链技术,为部分日本国债(JGB)交易提供即时结算服务。 报道称,MUFG 计划利用代币化货币市场基金及稳定币开展基于区块链的日本国债回购交易,以缩短传统证券交易的结算流程。(日本经济新闻) 原文链接 https://m.theblockbeats.info/flash/361270
👎1

Channel
@theblockbeats
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
37,005subscribers
-25 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001387109317 |
|---|---|
| Type | Channel |
| Username | @theblockbeats |
| Description | BlockBeats-专业的区块链研究机构与资讯平台。 交流群:https://t.me/BlockBeats_App |
| Created | Between 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/theblockbeats |
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 62% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @theblockbeats/189557 · this entry7 Aug 2026, 15:53 UTC | @DiscussWeb3News/1406777 Aug 2026, 22:43 UTC | 1.00 | 6.8 hours |
| @theblockbeats/189556 · this entry7 Aug 2026, 15:37 UTC | @DiscussWeb3News/1406787 Aug 2026, 22:43 UTC | 1.00 | 7.1 hours |
| @theblockbeats/189555 · this entry7 Aug 2026, 15:36 UTC | @DiscussWeb3News/1406797 Aug 2026, 22:43 UTC | 1.00 | 7.1 hours |
| @theblockbeats/189554 · this entry7 Aug 2026, 15:32 UTC | @DiscussWeb3News/1406807 Aug 2026, 22:43 UTC | 1.00 | 7.2 hours |
| @theblockbeats/189561 · this entry7 Aug 2026, 16:40 UTC | @DiscussWeb3News/1406827 Aug 2026, 22:44 UTC | 1.00 | 6.1 hours |
| @theblockbeats/189560 · this entry7 Aug 2026, 16:33 UTC | @DiscussWeb3News/1406837 Aug 2026, 22:44 UTC | 1.00 | 6.2 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @DiscussWeb3News | 11 (8/8 hand-verifiable sample passed) | 1.00 | 6.3 hours | this entry (11–0) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 62 comparable posts for this entry, running 6 August 2026 to 8 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Across the whole group of 2, the earliest publisher we hold is @theblockbeats — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 8 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 07:52 | 37,005 | -9 |
| 11 Aug 2026, 09:18 | 37,014 | +7 |
| 10 Aug 2026, 05:52 | 37,007 | -2 |
| 9 Aug 2026, 09:11 | 37,009 | -6 |
| 8 Aug 2026, 07:19 | 37,015 | -10 |
| 6 Aug 2026, 11:21 | 37,025 | -5 |
| 6 Aug 2026, 08:16 | 37,030 | first reading |
296 posts held, back to 6 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 17 pagesof 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 101 of 296 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 12 August 2026 |
|---|---|
| Posts held | 296 (6 August 2026 – 12 August 2026) |
| Views total | 173,518 |
| Reactions total | 245 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 20:48 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 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
219 reactions across 79 posts, in 18 distinct kinds. The most used accounts for 21.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤡 | 48 | 21.9% | |
| 👍 | 42 | 19.2% | |
| 🤣 | 29 | 13.2% | |
| ❤ | 26 | 11.9% | |
| 👎 | 19 | 8.68% | |
| 🥰 | 18 | 8.22% | |
| 👏 | 12 | 5.48% | |
| 💩 | 6 | 2.74% | |
| 🔥 | 6 | 2.74% | |
| 🤮 | 3 | 1.37% | |
| ⚡ | 2 | 0.913% | |
| 🐳 | 2 | 0.913% | |
| 🍌 | 1 | 0.457% | |
| 👌 | 1 | 0.457% | |
| 🖕 | 1 | 0.457% | |
| 😁 | 1 | 0.457% | |
| 😢 | 1 | 0.457% | |
| 🥴 | 1 | 0.457% |
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 101 of the 296 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 245reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 296 most recent posts we hold, published 6 August 2026 to 12 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.
三菱日联金融集团拟利用区块链推出日本国债即时结算服务 BlockBeats 消息,8 月 13 日,日本最大银行集团三菱日联金融集团(MUFG)计划利用区块链技术,为部分日本国债(JGB)交易提供即时结算服务。 报道称,MUFG 计划利用代币化货币市场基金及稳定币开展基于区块链的日本国债回购交易,以缩短传统证券交易的结算流程。(日本经济新闻) 原文链接 https://m.theblockbeats.info/flash/361270
👎1
DeepSeek V4 Pro 正式版上线 - 链接
❤2🔥1
高盛预计核心PCE为0.23%,略高于核心CPI和市场共识 BlockBeats 消息,8 月 13 日,CPI 数据之后,市场焦点转向 8 月 26 日日公布的 7 月核心 PCE 数据。高盛预计 7 月核心 PCE 环比上涨 0.23%,略高于核心 CPI 和市场共识。其中,投资组合管理费预计将增加 8 个基点,反映第二季度股市收益。 高盛表示,即将到来的方法论变动可能导致 PCE 读数波动,并降低年度核心通胀率。该行预计 8 月核心通胀率接近 0.2%,并认为美联储将维持利率稳定至年底。 原文链接 https://m.theblockbeats.info/flash/361269
美银宣布2500亿美元基础设施投资计划 BlockBeats 消息,8 月 13 日,美国银行(Bank of America)于周三宣布一项 2500 亿美元的基础设施投资计划,承诺在未来一年内投入美国关键基础设施领域,投资范围涵盖数据中心与算力、可再生能源发电、储能、天然气、输电网络及关键矿产与采矿等多个领域,目标是支持能源安全、就业增长和经济竞争力。 原文链接 https://m.theblockbeats.info/flash/361268
🔍 链上侦探 | USDC Treasury在Solana新铸2.5亿枚USDC BlockBeats 消息,8 月 12 日,据链上信息,USDC Treasury 在 10 分钟前于 Solana 新铸 2.5 亿枚 USDC。 原文链接 https://m.theblockbeats.info/flash/361265
摩根士丹利维持SpaceX增持评级,牛市情景下目标价600美元 BlockBeats 消息,8 月 12 日,摩根士丹利重申对 SPCX 的增持评级,目标价 300 美元,牛市情景下为 600 美元。 分析师 Adam Jonas 认为,市场低估了 SpaceX 更广泛的 AI 平台,包括其计算、连接性和实时数据能力。即将发布的 Grok 模型可能有助于缩小这一估值差距。Jonas 将即将到来的锁定期到期视为机会而非风险,为投资者提供潜在的入场点。 原文链接 https://m.theblockbeats.info/flash/361264
👎3👍2
美银对冲基金客户继续大买美股,单周规模创出2008年以来之最 BlockBeats 消息,8 月 12 日,美国银行对冲基金客户以接近创纪录的金额买入美国股票后一周,投资水平又达到了 2008 年以来最高。 该行 Jill Carey Hall 牵头的策略师在研报中写道,截至 8 月 7 日当周,客户连续第六周净买入美股,向 ETF 注入 41 亿美元,从个股撤资 24 亿美元。同期机构和散户客户均净卖出,而企业客户则加速回购。客户卖出了 11 个板块中的 7 个,其中工业股资金流出量最大,而科技板块则录得有史以来第二大吸金周。(彭博) 原文链接 https://m.theblockbeats.info/flash/361262
SpaceXAI推出Grok 4.6 BlockBeats 消息,8 月 12 日,据官方消息,SpaceXAI 正式推出 Grok 4.6。 原文链接 https://m.theblockbeats.info/flash/361261
巴基斯坦调解方正寻求延长美伊停火期限 BlockBeats 消息,8 月 12 日,据沙特阿拉伯阿拉比亚电视台:巴基斯坦调解方正寻求延长(美伊)60 天停火期限。 原文链接 https://m.theblockbeats.info/flash/361260
🤣2
⚡️高盛拟以最高22.5亿美元收购Neos,由此获得规模约10亿美元的比特币期权收益ETF BlockBeats 消息,8 月 12 日,高盛将通过现金及股权交易,以最高 22.5 亿美元收购 ETF 发行商 Neos Investments。Neos 旗下拥有近 24 只期权收益型 ETF,管理资产约 320 亿美元;交易完成后,高盛 ETF 管理资产预计增至约 1,300 亿美元。 彭博 ETF 分析师 Eric Balchunas 表示,高盛将由此获得 Neos 旗下规模约 10 亿美元的 Bitcoin Premium Income ETF(BTCI)。据悉,该基金通过 比特币相关资产与期权策略获取收益,显示分配率约为 27%,可捕捉比特币大部分涨幅。 原文链接 https://m.theblockbeats.info/flash/361259
Coinbase将暂停MEME、SAND、BIRB等10种代币永续合约交易 BlockBeats 消息,8 月 12 日,Coinbase 将于 8 月 26 日 21:00 前后暂停以下永续合约交易:Memecoin(MEME-PERP)、The Sandbox(SAND-PERP)、Moonbirds(BIRB-PERP)、Blur(BLUR-PERP)、Katana(KAT-PERP)、SPX6900(SPX-PERP)、ZORA(ZORA-PERP)、Axie Infinity(AXS-PERP)、Gensyn(AI-PERP)及 LayerZero(ZRO-PERP)。 届时剩余未平仓头寸将自动结算,最终结算价格为暂停交易前 60 分钟的平均指数价格,最后一个资金费率周期的费率将设为零。 原文链接 https://m.theblockbeats.info/flash/361258
👎1
Hyperliquid拟为HIP-1新增代币面额调整功能 BlockBeats 消息,8 月 12 日,Hyperliquid 创始人 Jeff 在 Discord 发文表示,根据开发者反馈,HIP-1 将新增由部署者控制的 scaleWei 功能,可按用户持有参考代币的余额比例,以原子方式分配系统地址中的代币,并支持代币面额调整。 调整期间,未成交订单将按实际比例取消并重新挂单,且可通过负数参数实现反向调整。由于 EVM 不支持相同的原子操作,相关合约可能需要加入自定义余额处理逻辑。 原文链接 https://m.theblockbeats.info/flash/361257
Showing the 12 most recent of 296 posts we hold for @theblockbeats. 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.
Citation-graph rank — 28,775 of 1,151,006entries 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.
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.
@theblockbeats named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“BlockBeats” (@theblockbeats), 37,005 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/theblockbeats.
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.