【以色列贴现银行将开放 App 内比特币和以太坊交易】 以色列贴现银行(Discount Bank)官网披露,该行将从 11 月 26 日起,允许个人客户直接在银行 App 中买入、持有和卖出比特币和以太坊,无需另开数字钱包或境外交易所账户。这在以色列银行业尚属首次。服务只向开通证券账户、年满 18 岁的以色列居民开放。每笔交易手续费为交易额的 2%,上线后前半年免收托管费,之后每季度收 0.25%。资产由 Fireblocks 提供托管基础设施。
👍5

Channel
@jinsecaijinpingdao
On this record: Topic · Observations · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
213,809subscribers
-44,963 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1001697024078 |
|---|---|
| Type | Channel |
| Username | @jinsecaijinpingdao |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 67 |
| Confirmed unchanged | 1 time, most recently 17 November 2026 |
| On Telegram | t.me/jinsecaijinpingdao |
Crypto & trading — 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 8 August 2026 and assigned it the closest of 31 fixed categories, at 87% 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 3 other registered channels. 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 |
|---|---|---|---|
| @jinsecaijinpingdao/12293 · this entry8 Oct 2026, 03:01 UTC | @qklwushuo/18618 Oct 2026, 03:06 UTC | 1.00 | 5 minutes |
| @jinsecaijinpingdao/12512 · this entry3 Nov 2026, 06:42 UTC | @qklwushuo/19803 Nov 2026, 07:36 UTC | 1.00 | 54 minutes |
| @jinsecaijinpingdao/12527 · this entry4 Nov 2026, 14:34 UTC | @qklwushuo/19894 Nov 2026, 14:36 UTC | 1.00 | 2 minutes |
| @jinsecaijinpingdao/12540 · this entry5 Nov 2026, 22:39 UTC | @qklwushuo/19965 Nov 2026, 23:53 UTC | 1.00 | 75 minutes |
| @jinsecaijinpingdao/12559 · this entry7 Nov 2026, 23:26 UTC | @qklwushuo/20097 Nov 2026, 23:30 UTC | 1.00 | 5 minutes |
| @jinsecaijinpingdao/12576 · this entry10 Nov 2026, 02:12 UTC | @qklwushuo/201810 Nov 2026, 03:00 UTC | 1.00 | 48 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @qklwushuo | 15 (8/8 hand-verifiable sample passed) | 0.99 | 6 minutes | this entry (15–0) |
| @Blockbeats001 | 12 (8/8 hand-verifiable sample passed) | 0.98 | 10 minutes | this entry (10–2) |
| @jiamihuobishenchao | 7 (7/7 hand-verifiable sample passed) | 1.00 | 4 minutes | this entry (6–1) |
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 734 comparable posts for this entry, running 5 August 2026 to 12 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_source, last confirmed 13 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 |
|---|---|---|
| 17 Nov 2026, 15:57 | 213,809 | -1,354 |
| 14 Nov 2026, 07:18 | 215,163 | -1,066 |
| 11 Nov 2026, 06:47 | 216,229 | -638 |
| 9 Nov 2026, 09:38 | 216,867 | -672 |
| 7 Nov 2026, 23:47 | 217,539 | -621 |
| 7 Nov 2026, 00:31 | 218,160 | -345 |
| 6 Nov 2026, 03:07 | 218,505 | -383 |
| 5 Nov 2026, 00:17 | 218,888 | -571 |
| 4 Nov 2026, 02:27 | 219,459 | -317 |
| 3 Nov 2026, 02:15 | 219,776 | -282 |
| 1 Nov 2026, 23:55 | 220,058 | -373 |
| 1 Nov 2026, 02:58 | 220,431 | -301 |
| 31 Oct 2026, 02:19 | 220,732 | -533 |
| 30 Oct 2026, 02:19 | 221,265 | -202 |
| 29 Oct 2026, 05:31 | 221,467 | -573 |
| 28 Oct 2026, 01:55 | 222,040 | -482 |
| 27 Oct 2026, 01:29 | 222,522 | -246 |
| 26 Oct 2026, 03:48 | 222,768 | -433 |
| 25 Oct 2026, 00:56 | 223,201 | -296 |
| 24 Oct 2026, 04:30 | 223,497 | first reading |
738 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 208 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 190 of 211 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 12 November 2026 |
|---|---|
| Posts held | 738 (5 August 2026 – 12 November 2026) |
| Views total | 159,149 |
| Reactions total | 703 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 14:29 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.
1,605 reactions across 564 posts, in 16 distinct kinds. The most used accounts for 85.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 1,377 | 85.8% | |
| ❤ | 193 | 12.0% | |
| 🔥 | 6 | 0.374% | |
| 🤔 | 6 | 0.374% | |
| 🤣 | 4 | 0.249% | |
| 🥰 | 4 | 0.249% | |
| ✍ | 2 | 0.125% | |
| 🎉 | 2 | 0.125% | |
| 👏 | 2 | 0.125% | |
| 🤓 | 2 | 0.125% | |
| 🫡 | 2 | 0.125% | |
| 😇 | 1 | 0.062% | |
| 🤗 | 1 | 0.062% | |
| 🤝 | 1 | 0.062% | |
| 🤩 | 1 | 0.062% | |
| 🤯 | 1 | 0.062% |
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 576 of the 738 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 1,605 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 738 most recent posts we hold, published 5 August 2026 to 12 November 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.
Telegram’s own ‘edited’ marker: 0 of 211 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).
【以色列贴现银行将开放 App 内比特币和以太坊交易】 以色列贴现银行(Discount Bank)官网披露,该行将从 11 月 26 日起,允许个人客户直接在银行 App 中买入、持有和卖出比特币和以太坊,无需另开数字钱包或境外交易所账户。这在以色列银行业尚属首次。服务只向开通证券账户、年满 18 岁的以色列居民开放。每笔交易手续费为交易额的 2%,上线后前半年免收托管费,之后每季度收 0.25%。资产由 Fireblocks 提供托管基础设施。
👍5
【香港警方捣毁加密货币洗钱集团,拘捕22人,3个月涉案金额达1.5亿港元】 香港警方捣毁一个利用虚拟货币场外交易(OTC)渠道洗钱的跨境犯罪集团,拘捕22人,包括21男1女,年龄介乎21至54岁。 警方调查发现,该集团自今年8月起活跃,通过招揽内地人员来港开设傀儡银行账户、提取犯罪所得现金,再将资金转移至集团经营的虚拟货币OTC店铺,通过买卖虚拟货币等方式清洗资金。警方估计,该集团仅今年8月至10月期间涉洗黑钱金额已超过1.5亿港元。 据悉,该集团分工明确,首先安排持双程证的内地人员来港开设网上银行账户,用于接收犯罪所得;随后招募提款人员,利用集团派发的银行卡在不同地点、不同银行的ATM提取现金,再由跑腿人员集中收取并运送至OTC店铺完成洗钱。
👍5❤1
【FSB 敦促土耳其进一步完善加密资产监管,拟建立稳定币专项监管制度】 金融稳定委员会(FSB)发布对土耳其的同行评估报告,指出土耳其近年来在加强加密资产市场监管、监督和审查方面取得了实质性进展,但仍需进一步完善监管框架,使其与 FSB《加密资产活动全球监管框架》保持一致。 报告指出,土耳其已将加密资产市场中的大部分活动纳入监管范围,并对加密资产服务提供商(CASPs)引入注册和许可要求。同时,土耳其还实施了严格的资产托管隔离措施,并禁止在境内使用加密资产进行支付,以限制相关风险向支付和银行体系传导。此外,土耳其当局已建立集中式数据平台,用于监测加密资产活动。 不过,FSB 认为土耳其仍需在以下方面采取进一步措施:落实金融稳定监测框架、建立稳定币专项监管制度、加强监管与执法力度,以及推动跨境监管合作和信息共享。报告还指出,土耳其此前已完成加密资产监管框架建设,但稳定币监管制度仍有待完善。此次评审旨在推动土耳其进一步落实 F…
👍6
【美 SEC 2026 财年执法行动下降 23.7%,加密案件受关注】 美国证券交易委员会(SEC)在 2026 财年提起 348 项执法行动,较上一财年的 456 项下降 23.7%,为 1991 年以来最低。该年度执法结果包括涉嫌加密欺诈和 FTX 审计失败的案件。SEC 称已指控三个所谓的加密交易平台和四个投资俱乐部参与一项涉嫌诈骗投资者至少 1,400 万美元的计划;另一起案件中,一家比特币矿业公司创始人被控挪用 4,850 万美元,该公司此前从约 6,400 名投资者处筹集超过 9,560 万美元。4 月,SEC 与负责 FTX 审计的 Prager Metis 合伙人 Francis Decker 就未达到专业审计标准达成和解。2026 财年是 SEC 主席 Paul Atkins 上任后的首个完整财年,独立执法行动从上一年的 303 项降至 235 项。
👍5
【黄仁勋妻子“大格局声明”刷屏社媒,结果竟是网友代笔】 几日前,英伟达创始人黄仁勋在致全体员工的内部信中公开承认对结婚逾 40 年的妻子 Lori Huang 不忠,并就此事向家人、员工及股东致歉。该事件在全球范围内引发热烈讨论,两日内英伟达市值蒸发约 4000 亿至 4700 亿美元,股价累计跌幅约 11%。事件发酵后,X 上流传了一份据称来自 Lori Huang 的公开回应。传达信息大意如下:丈夫在公开披露出轨前先告知了她,充分给予尊重,但公开道歉无法一夜恢复信任;她不了解针对黄女士的指控真相,认为国家安全问题应由调查人员而非媒体处理;她不会加入对相关女性的围攻,真相应由证据认定;婚姻去留应由家人自己决定,并请求外界给予家人时间和隐私空间。这份回应在网络上迅速传播,少数相关推文甚至达成了浏览量破百万的成就,不少网友给予高度评价。许多人认为其措辞冷静、理性、有分寸,既没有情绪化指责,也没有急于站队,体现了成熟与得体;也有人…
👍5
【Cash App 创始人 Bob Lee 刺杀案凶手被判 16 年至终身监禁】 旧金山法院周二判处科技顾问 Nima Momeni 16 年至终身监禁。Momeni 因刺死 Cash App 创始人 Bob Lee 被定罪。2024 年 12 月,陪审团裁定其二级谋杀罪成立,并驳回其正当防卫主张。Momeni 自 2023 年案发后被捕以来一直被羁押。法官在宣判前驳回其重新审判请求,其律师计划上诉。检方称,Momeni 因 Lee 将其妹妹介绍给一名毒品贩子而愤怒,用刀刺了 Lee 三次,其中一次刺中心脏。Lee 随后在医院死亡,时年 43 岁。Lee 曾创建移动支付服务 Cash App,去世时担任加密货币公司 MobileCoin 首席产品官。2023 年 4 月,Cash App 创始人 Bob Lee 在旧金山遇刺身亡。
👍2
【英伟达独立董事聘请前检察官与华尔街顶级律所,就黄仁勋事件展开调查】 英伟达董事会周日宣布调查后,于美东时间 11 月 10 日发布声明,确认聘请前纽约南区代理联邦检察官 Joon H. Kim(金俊铉)及其新东家 Wachtell, Lipton, Rosen & Katz,对 CEO 黄仁勋事件展开“全面、独立的调查”。董事会同时表示,目前没有理由相信公司机密受到影响,黄仁勋本人表态支持调查并承诺配合。公开信息显示,Joon H. Kim 于 2017–2018 年升任纽约南区代理联邦检察官(SDNY 是美国最有声望的联邦检察官办公室,俗称“主权区”),统领 220 多名助理检察官,辖区案件涵盖经济间谍、窃取商业秘密、制裁违规和网络犯罪。2021 年 3 月,受纽约州总检察长 Letitia James 指派,他与 Anne Clark 共同独立调查州长科莫性骚扰案。调查报告发布后不久,科莫于 2021 年 8 月辞职。2…
【德国拟将加密账户纳入账户查询程序,草案允许冻结五个工作日】 德国联邦财政部 10 月 28 日的一份部级草案显示,德国账户查询系统未来将覆盖加密账户。根据草案,加密交易所及其他加密资产服务商须将客户账户主数据录入《德国银行法》第 24c 条规定的账户查询程序,当局可据此查看用户在哪家平台开户、开户时间及账户是否仍存在,但不包括余额和单笔交易。此外,金融情报机构(FIU)在怀疑洗钱时可将加密资产账户冻结最多五个工作日,且异议不能解除冻结。该草案仍在政府部门间协调,尚未生效;新的反洗钱法计划于 2027 年 7 月 10 日取代现行法律。
👍3
【巴西交易所 Mercado Bitcoin 拟下周通过 Pix 恢复雷亚尔充提】 巴西加密交易所 Mercado Bitcoin 宣布,拟于下周起通过巴西即时支付系统 Pix 恢复巴西雷亚尔的充值与提现业务。此时距离该交易所热钱包遭遇攻击、损失约 4900 万美元已过去逾两周。用户仅能向本人同名账户提现,固定收益产品结算收益也将入账。加密货币充值与提现目前仍处于暂停状态,交易所尚未公布具体恢复日期。
👍3❤1
【IMF:敦促肯尼亚引入加密货币旅行规则,要求平台共享客户信息】 国际货币基金组织(IMF)在 11 月 6 日发布的一份技术援助报告中建议,肯尼亚应要求加密平台收集、核实并传送受监管转账中汇款人和收款人的身份信息,包括姓名、账户信息、住址、身份证号码及钱包信息,即引入“旅行规则”(Travel Rule)。 IMF 称,肯尼亚在加密交易国际信息共享要求方面“存在重大缺口”,建议尽快将相关义务纳入其虚拟资产服务提供商(VASP)法规或其他合适的法律文件。肯尼亚《虚拟资产服务提供商法》已于 2025 年 11 月生效,由肯尼亚央行和资本市场管理局分领域监管。
👍6
【币安将停止处理涉及 MEXC 及关联实体的资金转账】 币安发布公告称,在美国财政部金融犯罪执法网络(FinCEN)将 MEXC 列为主要洗钱关注对象后,币安将停止处理涉及 MEXC 及公告所列关联实体的资金转账。币安表示,从币安钱包向上述实体转出资金的请求将被拒绝,来自上述实体的充值将被暂时扣留并接受合规审查。审查期间,相关账户可能受到限制,币安也可能依据使用条款采取进一步措施,包括终止向相关用户提供服务。
👍4❤1
【英伟达早知黄乐遭调查,法务高管曾联系美国商务部】 英伟达早在 2025 年就已得知黄乐被新加坡警方扣留,并主动向美国商务部高层打听情况。几周后,负责调查其关联企业 Megaspeed 涉嫌芯片走私的美国官员开始受到严格限制,到年底商务部被要求停止调查。2025 年夏末,英伟达总法律顾问 Tim Teter 直接致电美国商务部副部长 Jeffrey Kessler,询问其主管的工业与安全局(BIS)是否参与了新加坡警方对黄乐的扣留。当时黄乐已被新加坡警方问话并限制出境,美国商务部也在调查 Megaspeed 是否违规转运英伟达 AI 芯片。这通电话打出几周后,BIS 调查人员接到新要求,联系英伟达须先经过 Kessler 或获得其批准,对外调查时甚至不能提及 Megaspeed 及其马来西亚子公司的名字。Teter 后来要求直接与调查人员见面但遭到拒绝,随即称已获得 Kessler 许可,不明白为何仍被拒绝。调查人员担心英伟达…
👍6❤2
Showing the 12 most recent of 738 posts we hold for @jinsecaijinpingdao. 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 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.
@jinsecaijinpingdao named 3 handles 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.
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 17 August 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 14 seed channels' Telegram-generated recommendation lists in total. 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 17 November 2026 — this entry's latest reading, not the date you are reading this.
“金色财经” (@jinsecaijinpingdao), 213,809 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/jinsecaijinpingdao.
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.