Channel
@fenchacaij
On this record: Topic · Growth · Engagement · Reactions · Posts · Telegram's recommendations · Cite this entry
231,542subscribers
-44,098 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1001515857362 |
|---|---|
| Type | Channel |
| Username | @fenchacaij |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 59 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/fenchacaij |
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 90% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 10:06 | 231,542 | -560 |
| 5 Nov 2026, 09:16 | 232,102 | -634 |
| 4 Nov 2026, 06:50 | 232,736 | -226 |
| 3 Nov 2026, 09:00 | 232,962 | -486 |
| 2 Nov 2026, 11:28 | 233,448 | -117 |
| 1 Nov 2026, 08:50 | 233,565 | -590 |
| 31 Oct 2026, 11:46 | 234,155 | -355 |
| 30 Oct 2026, 12:18 | 234,510 | -454 |
| 29 Oct 2026, 08:56 | 234,964 | -667 |
| 28 Oct 2026, 04:27 | 235,631 | -444 |
| 27 Oct 2026, 07:05 | 236,075 | -219 |
| 26 Oct 2026, 09:36 | 236,294 | +65 |
| 25 Oct 2026, 06:21 | 236,229 | -191 |
| 24 Oct 2026, 07:27 | 236,420 | -974 |
| 23 Oct 2026, 05:18 | 237,394 | -1,446 |
| 22 Oct 2026, 05:06 | 238,840 | -419 |
| 20 Oct 2026, 23:27 | 239,259 | -453 |
| 19 Oct 2026, 18:50 | 239,712 | -628 |
| 18 Oct 2026, 18:17 | 240,340 | -512 |
| 17 Oct 2026, 17:00 | 240,852 | first reading |
703 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 186 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 229 of 260 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 November 2026 |
|---|---|
| Posts held | 703 (4 August 2026 – 6 November 2026) |
| Views total | 175,877 |
| Reactions total | 576 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Nov 2026, 01:55 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,018 reactions across 490 posts, in 8 distinct kinds. The most used accounts for 85.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 868 | 85.3% | |
| ❤ | 131 | 12.9% | |
| 😁 | 5 | 0.491% | |
| 😢 | 5 | 0.491% | |
| 👏 | 3 | 0.295% | |
| 👻 | 3 | 0.295% | |
| 🥰 | 2 | 0.196% | |
| 🐳 | 1 | 0.098% |
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 507 of the 703 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,018 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 703 most recent posts we hold, published 4 August 2026 to 6 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 260 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).
【德州当选州长：所有目前获准建设的数据中心都将获准完工】 德克萨斯州当选州长吉娜·希诺霍萨明确表示，所有目前获准在德克萨斯州建设的数据中心都将获准完工。这基本涵盖了所有 2027 年的项目，并且很可能持续到 2028 年。希诺霍将通过法律，确保所有新获准建设的数据中心缴纳税款、承诺不向消费者涨电价、不影响民众的水资源供应、使用工会劳工进行建设，并给予德克萨斯人一个席位。
👍2
【迪拜国际金融中心法院提议设立争议解决预言机】 迪拜国际金融中心（DIFC）法院于 11 月 5 日发布“争议解决预言机”（DRO）白皮书，提出让链下法院或仲裁裁决直接触发链上代币化资产强制执行的方案。该机制完全基于自愿原则，当事方需提前指定争议解决论坛，DIFC 法院将作为首个合格提供商。DRO 本身不主动改变资产，而是负责验证执行指令，并在参与的区块链上生成可审计的执行记录；实际的争议裁决、仲裁和调解仍按传统方式进行。白皮书将该框架定位为开放技术和法律标准，并列出五个核心要素：具备执行能力的司法管辖区、可采纳的开放标准、合格提供商注册表、受控试点计划，以及关于相互承认的国际对话。该提案在迪拜未来代币化论坛上公布，属于 DIFC 法院 2026 至 2030 年增长战略的一部分。
👍1
【印度金融机构遭 AI 黑客攻击，至少两款工具关联中国】 印度计算机应急响应小组（CERT-In）发布安全通报称，黑客组织“狡猾猎鹰”（Crafty Falcon）利用公开可用的人工智能工具实施高速自动化入侵，已入侵非银行贷款机构、金融科技公司及加密货币交易所。该机构将相关威胁描述为“仍在发生，且持续活跃”。通报点名 ARTEX、PentAGI、Cairn 和 CyberStrikeAI 四款入侵工具。网络安全研究人员称，其中至少两款与中国有关联。CrowdStrike 此前表示，中国开发的 ARTEX 自 9 月底以来被用于攻击韩国银行，一个与中国有关联的黑客组织还曾利用该工具攻击至少 14 个国家的 200 多个组织。CERT-In 未说明攻击发动者及该组织运作地点，也未称攻击由国家支持或主导。上述工具均可免费获取。
👍2
【美国司法部成立超级智能特别工作组，打击 AI 滥用】 美国司法部宣布成立“超级智能”特别工作组（DOJ-SITF），由副总检察长 Stanley Woodward 和副副总检察长 Stephen Weiss 领导，专门监管先进人工智能被滥用的行为。该工作组的既定任务是确保美国在“超级智能”领域的领先地位不被不法分子破坏，目标对象包括外国政府及其代理人、跨国犯罪组织，以及利用 AI 实施欺诈等犯罪的企业和个人。司法部长 Todd Blanche 表示，“超级智能”的发展将继续由美国创新者推动，工作组将与 SI Force 主席 Jay Clayton 合作，防止关键 AI 技术被国内外不法分子操纵。他称司法部将持续识别并起诉利用超级智能违反法律的人员，包括恶意针对美国纳税人、美国关键基础设施或其他国家安全领域的行为。Weiss 表示，司法部同样有责任加强超级智能风险与应对的常规报告，并确保企业实施严格的内部控制，使相关技术“按…
❤1👍1
【FATF：虚拟资产已成洗钱核心渠道，呼吁全球行动打击诈骗园区及相关非法资金流】 国际组织金融行动特别工作组（FATF）发布新报告《打击与诈骗窝点相关的全链条非法资金流动》，呼吁各国采取全球协调行动，瓦解诈骗园区及其犯罪网络。报告指出，犯罪分子利用现金、虚拟资产、即时支付平台等渠道洗钱，并借助 AI、深度伪造和自动化技术扩大规模。其中，虚拟资产已成为洗钱的核心渠道；在某些案例中，诈骗窝点内甚至设有专门的场外交易柜台，用于办理虚拟资产兑换及境内资金转移。在其中一起案例中，通过区块链分析发现，受害者汇入的资金总额超过 1 亿美元，最终流入了与某诈骗园区相关联的虚拟资产钱包集群。为此，FATF 提出六项核心原则，包括聚焦更广泛犯罪生态系统、端到端阻断非法资金流、加强跨部门信息共享与合作、跨境快速行动（尤其事发后 24-72 小时）、以受害者为中心，以及持续适应犯罪手法变化。
👍4
【乌克兰央行反对现行加密法案，要求终审前修订】 乌克兰国家银行（NBU）表示，不支持当前版本的加密资产合法化与监管草案，呼吁议员在终审表决前继续修订。NBU 支持参照欧盟《加密资产市场法案》（MiCA）及国际货币基金组织建议推进监管，但认为第 10225-d 号草案仍未解决其关键关切，且最终文本周二晚才送达，审议时间不足，立法过程透明度不够。NBU 警告，未在发行地受到充分监管的境外代币可能进入乌克兰，其中部分可能发挥电子货币作用，威胁货币主权与金融稳定，并绕开适用于本土同类资产的要求。NBU 希望获得评估并在必要时限制其使用的权力。关于市场准入，NBU 称此前曾达成初期通过竞争选出三家加密交易平台运营商的妥协，但终稿将前五年的准入数量交由证券监管机构酌定，引发垄断与腐败风险担忧。根据草案，乌克兰国家证券与股票市场委员会将成为主要监管者，存量加密资产适用至 2028 年底的 5%过渡税率，加密资产之间的交易明确免税。
👍1
【马来西亚警方捣毁涉嫌利用虚假加密交易所实施诈骗的团伙，逮捕 13 人】 据《新海峡时报》援引马新社报道，马来西亚警方于 11 月 4 日在马六甲捣毁一个涉嫌实施婚恋诈骗及虚假加密货币交易所骗局的团伙，逮捕 13 名嫌疑人，年龄介于 24 至 36 岁。 警方表示，该团伙通过 Telegram、QQ 和 Soul 等应用接触中国受害者，以情感关系及高额回报承诺诱导其转账参与虚假加密货币交易，约三个月前开始在涉案地点活动。受害者损失总额仍在调查中，警方已查获 12 台笔记本电脑、1 台台式电脑及 26 部手机等设备。
👍2
【加拿大男子因劫持美国高校超级计算机挖矿被引渡至美国】 美国司法部周二表示，一名加拿大男子已被引渡至美国，面临协助入侵高校计算机、窃取登录凭证并秘密挖掘加密货币的指控。纽约西区联邦大陪审团起诉了 35 岁的萨斯喀彻温省居民 Ryan James Roach 和 41 岁的安大略省居民 Mathiew James Stubbings，罪名包括合谋获取并破坏受保护计算机信息、获取受保护计算机信息及故意破坏受保护计算机，最高可判处 10 年监禁及 25 万美元罚款。起诉书显示，2016 年 6 月至 2019 年 12 月期间，两人针对拥有超级计算机的美国教育机构，先研究其网络安全弱点再实施入侵。进入系统后，他们据称部署恶意软件、窃取登录凭证，并强制受害者计算机为其挖矿。受害者包括纽约州、田纳西州、北卡罗来纳州和马萨诸塞州的机构。两人据称使用在多个国家以虚假姓名注册的虚拟专用服务器发送恶意软件和挖矿程序并存储窃取凭证，还通过其他受害…
👍6
【韩国区块链产业协会正式提交代币化证券修订案意见：建议央行参与节点运营】 韩国区块链产业协会（KBIPA）已正式向韩国金融委员会提交代币化证券相关法令修订案意见书，提出 9 项主要修改建议和 10 项技术性修正意见，并额外提出 6 项供未来修法参考的建议，包括扩大分布式账本参与主体范围，允许符合条件的第三方技术企业运营验证、共识及查询节点，同时将证券信息的记载权限和账本管理责任继续保留在现有参与机构手中。此外，韩国区块链产业协会建议允许韩国央行等结算资产发行及清算机构在必要范围内参与节点运营，为未来实现证券与资金同步交割（DvP）预留空间。同时，需明确分布式账本运营标准变更程序；若现有账本不再符合监管要求，应允许代币化证券先迁移至其他合规账本，而非直接转换为普通电子证券。
👍3
【Binance 遭攻击后，美国监管机构紧急排查银行系统安全】 在 Binance 上周遭遇 63 亿美元黑客攻击后，美国联邦储备委员会（美联储）和货币监理署（OCC）于本周一开始联系银行，询问其系统是否出现异常活动或服务中断，以排查加密市场安全事件向传统金融体系蔓延的风险。 知情人士表示，多家银行正在对内部系统进行安全诊断，并评估是否存在可能被类似攻击手法利用的漏洞。一家美国大型银行的网络安全团队已联系 Binance，并着手编写内部报告，后续可能据此审查系统并更新网络安全措施。 Binance 表示，目前正与全球监管机构保持密切联系，及时通报此次安全事件。美联储和 OCC 拒绝置评。 知情人士还指出，AI 模型快速演进增加了银行防范黑客攻击的难度，银行正投入大量资源审查和修补网络安全代码。
👍4
【Vitalik：未来两年加密公司首要任务是生存，安全保障将成为重点】 以太坊联合创始人 Vitalik Buterin 在接受采访时表示，过去一段时间，行业安全形势出现值得关注的趋势。智能合约层面的安全漏洞和攻击事件正在减少，过去一年半发生的大多数重大黑客攻击，已更多集中在用户界面层和中心化组件上。黑客攻击仍在持续发生，但真正需要重点保障安全的底层核心部分，安全性实际上正在提升，能够提供较高安全保障的基础设施范围也在扩大。Vitalik 认为，越来越多的人已经意识到，未来两年的首要任务不是取得胜利，而是确保自己能够生存下来，整个行业都在思考如何实现这一目标。他预计，相关机构、大型交易平台、托管机构以及其他金融机构也会尽快采取行动。他认为，Binance 此前推出 BNB Chain 是一个正确决策，用户将业务部署在链上、通过智能合约执行相关操作时，也能受益于链上基础设施提供的较高安全保障，未来会有更多机构朝着这一方向发展。V…
👍3
【法国预算案遭否决，稳定币征税及钱包申报条款被搁置】 法国国民议会于周三晚间否决了 2027 年国家预算案中的“收入”部分，导致此前已纳入法案的三项加密货币相关修正案被剔除，不再包含在即将提交给参议院的法案版本中，但未来仍有可能在参议院审议阶段被重新提出。国民议会曾通过三项与加密货币相关的修正案。10 月 16 日，议员们通过一项修正案，规定将加密货币兑换为稳定币所产生的收益纳入征税范围。周二，议员们又通过另一项修正案，要求纳税人申报其持有的自托管加密资产；若总额达到或超过 10 万欧元（约合 11.2 万美元），即需申报，评估基准日为纳税年度的 12 月 31 日。此外，还有一项修正案提出，若加密货币平台未能按税务机关要求提供相关信息，其面临的罚款金额将从 1 万欧元提高至 5 万欧元。
👍2
Showing the 12 most recent of 703 posts we hold for @fenchacaij. 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.
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 25 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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“分叉财经(crypto news)” (@fenchacaij), 231,542 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/fenchacaij.
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.