【快讯】美元指数升至去年4月以来最高 金色财经报道,11月11日消息,美元指数DXY突破上月前高,升至去年4月以来最高水平102.95。 原文链接:https://www.jinse.com.cn/lives/540520.html
Signed 金色财经JinSeFinance

Channel
@jinse2017
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
22,579subscribers
-573 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001748596288 |
|---|---|
| Type | Channel |
| Username | @jinse2017 |
| Description | 金色财经是集行业新闻、资讯、行情、数据等一站式区块链产业服务平台。 推特:https://twitter.com/jinsefinance 加入讨论: https://t.me/Jinse2022 电报频道:https://t.me/jinse2017 官网:jinse.cn APP:https://app.jinse.cn 广告合作:[email protected] 媒体合作:[email protected] 商务合作:[email protected] |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 62 |
| Confirmed unchanged | 1 time, most recently 10 November 2026 |
| On Telegram | t.me/jinse2017 |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 64% 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 the other topics.
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 in near-verbatim form 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 |
|---|---|---|---|
| @jinse2017/69210 · this entry27 Sept 2026, 23:41 UTC | @jinseBTC/22578127 Sept 2026, 23:42 UTC | 0.89 | 72 seconds |
| @jinse2017/68625 · this entry26 Aug 2026, 14:18 UTC | @jinseBTC/22122626 Aug 2026, 14:20 UTC | 0.84 | 2 minutes |
| @jinseBTC/2300383 Nov 2026, 14:31 UTC | @jinse2017/70039 · this entry3 Nov 2026, 14:32 UTC | 0.83 | under a minute |
| @jinseBTC/2300393 Nov 2026, 14:37 UTC | @jinse2017/70040 · this entry3 Nov 2026, 14:38 UTC | 0.81 | under a minute |
| @jinseBTC/2302895 Nov 2026, 02:14 UTC | @jinse2017/70079 · this entry5 Nov 2026, 02:15 UTC | 0.76 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @jinseBTC | 5 (5/5 hand-verifiable sample passed) | 0.83 | under a minute | @jinseBTC (3–2) |
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. 3 of the 3 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 1,028 comparable posts for this entry, running 5 August 2026 to 11 November 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.
Recorded under the key clone_mutual, last confirmed 11 November 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Nov 2026, 20:27 | 22,579 | -6 |
| 7 Nov 2026, 22:21 | 22,585 | +4 |
| 6 Nov 2026, 17:17 | 22,581 | -11 |
| 5 Nov 2026, 14:26 | 22,592 | +2 |
| 4 Nov 2026, 11:49 | 22,590 | +4 |
| 3 Nov 2026, 11:34 | 22,586 | +3 |
| 2 Nov 2026, 08:46 | 22,583 | -5 |
| 31 Oct 2026, 05:28 | 22,588 | +1 |
| 30 Oct 2026, 05:20 | 22,587 | -5 |
| 29 Oct 2026, 07:29 | 22,592 | -12 |
| 28 Oct 2026, 07:27 | 22,604 | -6 |
| 27 Oct 2026, 07:25 | 22,610 | -10 |
| 26 Oct 2026, 08:26 | 22,620 | +35 |
| 25 Oct 2026, 11:28 | 22,585 | -5 |
| 24 Oct 2026, 11:49 | 22,590 | -8 |
| 23 Oct 2026, 11:46 | 22,598 | -8 |
| 22 Oct 2026, 10:56 | 22,606 | -7 |
| 21 Oct 2026, 01:40 | 22,613 | -9 |
| 20 Oct 2026, 00:18 | 22,622 | -13 |
| 18 Oct 2026, 21:04 | 22,635 | first reading |
1,077 posts held, back to 5 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 104 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.
| Window | Rolling 30 days · latest post in window 11 November 2026 |
|---|---|
| Posts held | 1,077 (5 August 2026 – 11 November 2026) |
| Views total | 170,263 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 15:09 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 11 November 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.
Telegram’s own ‘edited’ marker: 0 of 280 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).
【快讯】美元指数升至去年4月以来最高 金色财经报道,11月11日消息,美元指数DXY突破上月前高,升至去年4月以来最高水平102.95。 原文链接:https://www.jinse.com.cn/lives/540520.html
Signed 金色财经JinSeFinance
【快讯】美股三大指数高开,CoreWeave大涨超16%,英伟达涨近3% 【美股三大指数高开,CoreWeave大涨超16%,英伟达涨近3%】金色财经报道,11月11日,美股三大指数集体高开,纳指涨1.53%,标普500指数涨0.93%,道指涨0.14%。 英伟达涨近3%,高盛称半导体板块进入“超卖”区间,英伟达估值吸引。 谷歌A涨超1%,AnthropicIPO前夕披露与微软、谷歌达成114亿美元新云计算协议。 CoreWeave涨超16%,Q3营收同比飙升168%,上调全年业绩指引。 原文链接:https://www.jinse.com.cn/lives/540515.html
Signed 金色财经JinSeFinance
中期选举、美联储政策、美股波动 谁在左右加密行情 近日,加密市场行情回落,BTC、ETH等主流资产均跌势为主。美国中期选举带来的监管政策不确定、美联储后续政策预期、科技股波动等因素都在影响加密行情。 原文链接:https://www.jinse.com.cn/blockchain/3740895.html
Signed 金色财经JinSeFinance
【快讯】ZEC跌破1000美元,24小时跌幅达14.3% 【ZEC跌破1000美元,24小时跌幅达14.3%】金色财经报道,行情显示,ZEC跌破1000美元,现报价986.75美元,24小时跌幅达14.3%,行情波动较大,请做好风险控制。 原文链接:https://www.jinse.com.cn/lives/540483.html
Signed 金色财经JinSeFinance
【快讯】美国现货以太坊ETF昨日净流出132万美元 金色财经报道,11月11日,据Trader T监测,美国现货以太坊ETF昨日净流出132万美元。 原文链接:https://www.jinse.com.cn/lives/540478.html
Signed 金色财经JinSeFinance
【快讯】美国现货比特币ETF昨日净流出9500万美元 【美国现货比特币ETF昨日净流出9500万美元】金色财经报道,11月11日,据Trader T监测,美国现货比特币ETF昨日净流出9500万美元。 原文链接:https://www.jinse.com.cn/lives/540477.html
Signed 金色财经JinSeFinance
Multicoin:AI时代DeFi的三道护城河 什么协议能捕获价值 你可以在一顿饭时间用 AI 生成一个借贷协议,但生成不了 100 亿美元存款。 原文链接:https://www.jinse.com.cn/blockchain/3740881.html
Signed 金色财经JinSeFinance
【快讯】金色午报 | 11月11日午间重要动态一览 【金色午报 | 11月11日午间重要动态一览】7:00-12:00关键词:Gram、高盛、以太坊基金会 1.Telegram CEO:代币Gram仍被严重低估; 2.美联储传声筒”:更大幅度、更快加息的压力正在加大; 3.美联储官员Paulson称目前逐步收紧政策似乎是合适的; 4.高盛预计美联储将在今年12月和2027年3月各加息25个基点; 5.韩国在野党议员宋彦锡:韩国应直接废除加密货币所得税计划; 6.以太坊基金会关联钱包于9小时前再次抛售1000枚ETH,约合203万美元。 原文链接:https://www.jinse.com.cn/lives/540469.html
Signed 金色财经JinSeFinance
【快讯】高盛预计美联储将在今年12月和2027年3月各加息25个基点 金色财经报道,11月11日,高盛预计美联储将在今年12月和2027年3月各加息25个基点,此前预测为今年12月加息。(金十) 原文链接:https://www.jinse.com.cn/lives/540468.html
Signed 金色财经JinSeFinance
ANT上市倒计时:Pre-IPO永续合约市场如何解读Anthropic的IPO定价 解析不同Pre-IPO合约的结算规则,以及Anthropic IPO在总市值估值与单股估值之间的换算逻辑。 原文链接:https://www.jinse.com.cn/blockchain/3740875.html
Signed 金色财经JinSeFinance
【快讯】美联储官员Paulson称目前逐步收紧政策似乎是合适的 【美联储官员Paulson称目前逐步收紧政策似乎是合适的】金色财经报道,11月11日,费城联邦储备银行行长Anna Paulson表示,她赞成循序渐进地提高利率,并补充称薪资压力有限,通胀预期仍与央行2%的目标一致。Paulson周二在费城联储组织的一次活动上表示,“就目前而言,进一步逐步收紧政策似乎是合适的。”她补充说,“如果通胀预期上升、工资压力增大或潜在通胀走高,我会希望更快地采取行动。但目前,我还没有看到这种情况。”美联储官员上月将基准利率维持在3.75%至4%的区间不变,此前他们在9月加息0.25个百分点。自10月会议以来,多位政策制定者表示,需要进一步收紧政策才能将通胀率控制在2%的目标范围内。 Paulson表示,“一次会议不行动,那只是节奏问题,而不是方向的问题。可能还有更多工作要做。但我倾向于在条件允许的情况下逐步收紧政策。”她补充说,放慢节奏可…
Signed 金色财经JinSeFinance
【快讯】金色晨讯 | 11月11日隔夜重要动态一览 【金色晨讯 | 11月11日隔夜重要动态一览】21:00-7:00关键词:CPI、Binance、Path Robotics、波兰 1.美国CPI高于预期; 2.胡塞武装称将发表重要声明; 3.Binance:用户持有的传统金融资产超30亿美元; 4.交易员加大了对美联储下月加息50个基点的押注; 5.Path Robotics融资3亿美元,估值升至24.5亿美元; 6.波兰下议院通过制裁法案,加密资产纳入可冻结资金范围; 6.Binance黑客近三日经THORChain与Chainflip转移约8.91亿美元; 7.富达FCAT成为Ondo Bridge必需验证者,覆盖450余只代币化股票。 原文链接:https://www.jinse.com.cn/lives/540448.html
Signed 金色财经JinSeFinance
Showing the 12 most recent of 1,077 posts we hold for @jinse2017. 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 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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 20 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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 37 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 10 November 2026 — this entry's latest reading, not the date you are reading this.
“金色财经新闻频道” (@jinse2017), 22,579 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/jinse2017.
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.