⚠️请各位还在使用老版本“独角数卡”的朋友,尽快切换到新版本Dujiao-Next。 接到消息确认,老版本存在支付伪造等高危漏洞, 老版本已经在今年年初停止维护更新以及漏洞响应了, 为了你的资产安全,请尽快下线“独角数卡”更新至 ”Dujiao-Next“或其他更安全的系统!

Channel
TokenPay
@TokenPayChannel
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
850subscribers
+2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001694556642 |
|---|---|
| Type | Channel |
| Username | @TokenPayChannel |
| 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 | 12 October 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/TokenPayChannel |
Topic
Hacking & security — 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 19 September 2026 and assigned it the closest of 31 fixed categories, at 61% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Oct 2026, 09:36 | 850 | +2 |
| 9 Sept 2026, 18:02 | 848 | -1 |
| 30 Aug 2026, 12:57 | 849 | +1 |
| 7 Aug 2026, 09:33 | 848 | no change |
| 7 Aug 2026, 09:29 | 848 | first reading |
Engagement
20 posts held, back to 17 March 2024 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 17 March 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
20 reactions across 9 posts, in 3 distinct kinds. The most used accounts for 60.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 12 | 60.0% | |
| ❤ | 7 | 35.0% | |
| 😁 | 1 | 5.00% |
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 11 of the 20 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 20 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 17 March 2024 to 17 March 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.
Recent posts
+888滞销,要租匿名号码的老板们快来! https://t.me/Zu888Bot
TokenPay v1.1.0 1. 本次更新用于适配Etherscan V2 更新要点:第一步:更新主程序;第二步,新手建议使用新版EVMChains.json覆盖旧配置文件并重新配置,老手可以手动修改配置文件,新配置文件删除了ApiHost字段,新增了ChainId字段,同时非ETH链(不含波场)的ApiKey需要重新申请,申请链接: https://docs.etherscan.io/etherscan-v2/getting-an-api-key 检查TokenPay支持的EVM系区块链:https://docs.etherscan.io/etherscan-v2/supported-chains 注意事项:Etherscan V2不支持的区块链仍然可以配置ApiHost字段,因此可以继续使用你之前的配置段。已经支持V2的区块链务必升级到V2的配置(即,删除ApiHost字段,新增ChainId字段,重新配置Api…
❤5
TokenPay 测试版 v1.1.0-2025061301 1. 本次更新用于适配Etherscan V2 更新要点:更新主程序并使用新版EVMChains.json覆盖旧配置文件并重新配置,新配置文件删除了ApiHost字段,新增了ChainId字段,同时非ETH链的ApiKey需要重新申请,申请链接: https://docs.etherscan.io/etherscan-v2/getting-an-api-key 注意事项:Etherscan V2不支持的区块链仍然可以配置ApiHost字段,因此可以继续使用你之前的配置段。已经支持V2的区块链务必升级到V2的配置(即,删除ApiHost字段,新增ChainId字段,重新配置ApiKey字段),因为后续V1版本的Api可能会被陆续暂停。 https://github.com/LightCountry/TokenPay/releases/tag/pre-v1.1.0…
完整的TokenPay目前支持的所有币种小数点位数的配置示例 对应代码:[public static int GetDecimals] 注意:静态地址模式下,小数点位数会影响同金额同时可下单次数,设置为1,同金额最多下10单,设置为2,同金额最多100单,设置为3最多1000单,以此类推,因此不建议设为0,也不支持负数。 "Decimals": { "TRX":2, "USDT_TRC20":2, "EVM_ETH_ETH":4, "EVM_ETH_USDT_ERC20":2, "EVM_ETH_USDC_ERC20":2, "EVM_BSC_BNB":4, "EVM_BSC_USDT_BEP20":2, "EVM_BSC_USDC_BEP20":2, "EVM_Polygon_POL":2, "EVM_Polygon_USDT_ERC20"…
TokenPay v1.0.9.3 1. EVM系列基本币转账支持内部交易; 2. 升级依赖版本,提升安全性。 说明:之前版本对于EVM系列各链的基本币(如ETH、BNB、POL等币种),查询转账记录时只包含了普通转账交易(Transactions),未包含内部交易(Internal Transactions),目前交易所或中心化钱包处理用户提币时,大多使用智能合约进行一对多批量转账,之前版本无法查询到这类交易记录,此测试版新增了对这类交易的支持。 https://github.com/LightCountry/TokenPay/releases/tag/v1.0.9.3
😁1
TRX疯了
👍5
TokenPay 测试版 v1.0.9.3-2024120101 1. EVM系列基本币转账支持内部交易; 2. 升级依赖版本,提升安全性。 说明:之前版本对于EVM系列各链的基本币(如ETH、BNB、POL等币种),查询转账记录时只包含了普通转账交易(Transactions),未包含内部交易(Internal Transactions),目前交易所或中心化钱包处理用户提币时,大多使用智能合约进行一对多批量转账,之前版本无法查询到这类交易记录,此测试版新增了对这类交易的支持。 从ETH区块浏览器上随便找了两个内部交易的示例链接 内部交易列表示例:https://etherscan.io/address/0xaa99fc695eb1bbfb359fbad718c7c6dafc03a839#internaltx 内部交易详情示例:https://etherscan.io/tx/0x10aefdbb88cd6230b19b4c…
👍2
TokenPay v1.0.9.2 1. 增加查单接口,可主动从TokenPay查询订单状态 2. 能量租用改为租用10分钟能量,节省归集成本 3. 处理PassThroughInfo被传递空字符串,导致签名不匹配的情况 4. 更新dockerfile到 .NET 8 重要⚠️:由于从 .NET 6 升级到了 .NET 8,TokenPay不再支持一些较旧的Linux系统, 点此查看当前支持的系统 低版本系统如果报错“GLIBCXX_3.4.x not found”,可尝试此解决方案:https://www.cnblogs.com/wangwangwangMax/p/17356130.html https://github.com/LightCountry/TokenPay/releases/tag/v1.0.9.2
TokenPay v1.0.9.1 1. 修复上个版本动态金额逻辑Bug(不使用动态金额功能可以不用更新) 2. 系统日志增加重要配置文件的显示 重要⚠️:由于从 .NET 6 升级到了 .NET 8,TokenPay不再支持一些较旧的Linux系统, 点此查看当前支持的系统 低版本系统如果报错“GLIBCXX_3.4.x not found”,可尝试此解决方案:https://www.cnblogs.com/wangwangwangMax/p/17356130.html https://github.com/LightCountry/TokenPay/releases/tag/v1.0.9.1
归集功能参数更新如图所示
‼️重要通知‼️:使用TokenPay自动归集的用户,建议今天20点前暂停归集功能,由于波场95号提案即将实施,会影响归集功能的正常使用,等新提案稳定后,需要修改归集参数,届时,新参数会发布在此频道
👍1
Showing the 12 most recent of 20 posts we hold for @TokenPayChannel. 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.
Cite this entry
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 October 2026 — this entry's latest reading, not the date you are reading this.
“TokenPay” (@TokenPayChannel), 850 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/TokenPayChannel.
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.