通道名称:易币付虚拟币 产 品:USDT充提 下发价格: 商户手动下发:ERC20,单笔15U;TRC20,单笔1U 会员代付:1)易币付地址提币,免手续费且快速到账;2)非易币付钱包地址提币,ERC20 单笔15U,TRC20 单笔1U 结算周期:D0 支持终端:PC及手机端 充值模式:扫码/复制地址转账充值 下发模式:支持代付,商户用户手动 商户号日限额:1000万U 充值单笔限额:10U-4万U 下发单笔限额:10U-4万U 交易时间:24H 下发时间:24H 到帐时间:实时 客服时间:24H 押金:无 后台对帐:商户后台支持对账 ————————————————— 🔴官方招商负责人: Telgram:@kyzs168 MeeTalk:ky789789 天下支付 代收付: @txlm78 易币付 代收付: @ybf78 EBpay钱包 代收付: @EBpay789 天下联盟 支付官方频道: @txzf1…

Channel
易币付 代收付
@ybf78
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
20subscribers
+0 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 | -1001969913259 |
|---|---|
| Type | Channel |
| Username | @ybf78 |
| Description | 🔴官方招商负责人: Telgram: @kyzs168 MeeTalk:ky789789 天下联盟 代收付招商频道: @txlm78 易币付 代收付招商频道: @ybf78 EBpay钱包 代收付招商频道: @EBpay789 KST 包网建站: @zsbage110 ———————————————- 代理自助开线机器人🤖 @kyzs188bot |
| Created | 17 August 2023 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 28 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/ybf78 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 15:32 | 20 | no change |
| 7 Aug 2026, 12:42 | 20 | first reading |
Engagement
9 posts held, back to 17 August 2023 — 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 pageof 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 9 posts for this entry, the most recent from 17 August 2023. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 7
Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Recent posts
生态伙伴 bitcoin bittrex bitz coinmarketcap ethereum tether bitmex poloniex localbitcoins etherdelta ————————————————— 🔴官方招商负责人: Telgram:@kyzs168 MeeTalk:ky789789 天下支付 代收付: @txlm78 易币付 代收付: @ybf78 EBpay钱包 代收付: @EBpay789 天下联盟 支付官方频道: @txzf186 KST 包网建站频道:@zsbage110 ———————————————- 代理自助开线机器人🤖 @kyzs188bot
开放支付 如果您已开始接纳数字货币,立即让您的用户可以通过数字货币或等值法币完成支付 ————————————————— 🔴官方招商负责人: Telgram:@kyzs168 MeeTalk:ky789789 天下支付 代收付: @txlm78 易币付 代收付: @ybf78 EBpay钱包 代收付: @EBpay789 天下联盟 支付官方频道: @txzf186 KST 包网建站频道:@zsbage110 ———————————————- 代理自助开线机器人🤖 @kyzs188bot
场外交易平台 一键跨法币和数字币兑换币种 跨法币和数字货币的自由兑换 简单、快速、最优汇率 跨币种支付 ————————————————— 🔴官方招商负责人: Telgram:@kyzs168 MeeTalk:ky789789 天下支付 代收付: @txlm78 易币付 代收付: @ybf78 EBpay钱包 代收付: @EBpay789 天下联盟 支付官方频道: @txzf186 KST 包网建站频道:@zsbage110 ———————————————- 代理自助开线机器人🤖 @kyzs188bot
多链钱包 轻松管理您的多链资产 支持多种虚拟资产 目前,我们已开放对BTC、USDT的支持,且会不断地加入更多币种。对主流全币种的支持,是我们不断努力的目标 易币付内转账0手续费 如果您与对方转账的地址同属易币付钱包的地址,则可以享受0手续费转账,且有更多优惠功能持续增加 极致简单收付款 告别繁琐秘钥输入和操作步骤、冗长地址等烦恼,体验二维扫描后一键收款/付款的极致简单功能。让您像使用法币一样使用数字货币 ————————————————— 🔴官方招商负责人: Telgram:@kyzs168 MeeTalk:ky789789 天下支付 代收付: @txlm78 易币付 代收付: @ybf78 EBpay钱包 代收付: @EBpay789 天下联盟 支付官方频道: @txzf186 KST 包网建站频道:@zsbage110 ———————————————- 代理自助开线机器人🤖 @kyzs188bot
易币付虚拟币渠道对接 商务条款: 通道名称:易币付虚拟币 产 品:USDT充提 充值费率:0.3% 下发价格: 商户手动下发:ERC20,单笔15U;TRC20,单笔1U 会员代付:1)易币付地址提币,免手续费且快速到账;2)非易币付钱包地址提币,ERC20 单笔15U,TRC20 单笔1U 结算周期:D0 支持终端:PC及手机端 充值模式:扫码/复制地址转账充值 下发模式:支持代付,商户用户手动 商户号日限额:1000万U 充值单笔限额:10U-4万U 下发单笔限额:10U-4万U 交易时间:24H 下发时间:24H 到帐时间:实时 客服时间:24H 押金:无 后台对帐:商户后台支持对账 一、业务模式确认 1. 会员提单是人民币还是U 2. 会员订单如果是人民币,转化为USDT,这个汇率是否平台自己去抓公网汇率; 3. 如果用我方汇率,默认okx买一价+卖一价 4. 从易币付获取汇率方式:对接文档里有接口 建…
区块链世界,从易币付开始 @ybf78 易币付钱包是一款专业的多币种钱包,由世界一流区块链技术团队及东南亚四大互联网集团公司投资成立;背靠集团千万级用户为基础; 为超过50万商家提供数字货币支付业务,已形成全面的数字经济产业生态体系。多重维度保障用户的数字资产安全,提供简单便捷、 安全可靠的数字资产管理服务。易币付钱包与泰国、菲律宾、新加坡、俄罗斯等多个国家展开区块链技术、应用领域合作,助推全球区块链应用落地。 易币付钱包在全球多个地区拥有数字资产营业牌照,在美国、日本、泰国等国家和地区设有子公司或合作公司。集团拥有超过5000名员工。为全球千万级用户提供数字资产安全服务。 ————————————————— 🔴官方招商负责人: Telgram:@kyzs168 MeeTalk:ky789789 天下支付 代收付: @txlm78 易币付 代收付: @ybf78 EBpay钱包 代收付: @EBpay789 天下联盟 …
Channel photo updated
Channel created
Showing the 9 most recent of 9 posts we hold for @ybf78. 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
Citation-graph rank — 754,628 of 1,627,445entries 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.
Mentions
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.
Handles this channel named that no longer answer
- Dead references
- 2
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 2
- vacant every time we have ever looked
@ybf78 named 2 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 7 posts, 12 August 2026 – 12 August 2026
named in 7 posts, 12 August 2026 – 12 August 2026
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“易币付 代收付” (@ybf78), 20 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/ybf78.
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.