[DIS] Fiber Link: A CKB Fiber-based Pay Layer (Tipping & Micropayments) for Communities

CKB Community Fund DAO
21

Hey team :waving_hand:

Thanks for sharing the milestone materials! Just a small suggestion — would you consider hosting these on a public GitHub repo instead of SwissTransfer?

A dedicated repo would make the materials permanently accessible, easier for the community and grants reviewers to track, and the commit history would serve as a natural audit trail for each milestone delivery. SwissTransfer links can expire, which might cause issues down the road.

Something like a simple fiber-link-milestones repo with a clear folder structure per milestone would work great.

嗨，团队好 :waving_hand:

感谢分享里程碑相关材料！我刚进swisstransfer时，被该网站上一些无关的弹窗迷惑了。有个小建议——是否可以考虑把这些内容放到一个公开的 GitHub repo 里，而不是 SwissTransfer 上，会不会更好？

SwissTransfer 的链接可能会过期，长期来看存在访问风险。相比之下，一个专门的 repo 不仅能永久存档，也更方便社区成员和 grants 审核方随时查阅，而且每次提交的 commit 记录天然就是里程碑交付的时间证明，透明度更高。

可以建一个简单的 fiber-link-milestones 仓库，按里程碑分文件夹管理就行，结构清晰，维护也不麻烦。

2 Likes
22

@yixiu.ckbfans.bit Thanks — I agree with the direction, but personally I don’t think GitHub should be used as a file hosting service / network disk for this kind of artifact storage.

For code and versioned text assets, GitHub is great. But for screenshots, videos, reports, and larger demo artifacts, it feels like the wrong home.

I’ll discuss this with the team. A more reasonable approach is probably for us to host and maintain a separate file storage service (or a small managed file server) specifically for these deliverables, so the project materials are easier to maintain and access in a cleaner way.

@yixiu.ckbfans.bit 感谢建议，这个方向我认同，不过以我个人的看法，GitHub 不太适合拿来当网盘或者文件托管服务用。

如果是代码、文档、版本化文本内容，GitHub 很合适；但如果是截图、视频、测试报告这类交付材料，我觉得放在那里并不是最舒服的做法。

我会和团队讨论一下。更合理的方式，可能还是由我们团队自己 host 一个独立的文件存储服务（或者维护一个专门的托管点），专门用来放这些交付文件，这样后续维护和访问都会更清晰一些。

2 Likes
23

Hi @Akane ，社区有成员在看到 M2 同步信息后提了一个问题：No code to show (for M2)?。能否补充一下M2相关的 repo 地址，方便社区成员查看？

Hi Akane, a community member raised a question after seeing the M2 update: No code to show (for M2)?. Could you share the M2 relevant repo URL here so community members can review directly?

Thanks!

1 Like
24

@zz_tovarishch Thanks — just to clarify, we already revealed the repo URL in the M1 report.

The repository is here:

I’m adding it again here for convenience so community members can review it directly from this thread.

@zz_tovarishch 感谢提醒，补充说明一下：我们其实已经在 M1 的报告里公开过 repo 地址了。

仓库地址在这里：

我这边再补一次，方便社区成员直接在这个帖子里查看。

3 Likes
25

@yixiu.ckbfans.bit Thanks for the suggestion — we’ve moved the M2 acceptance materials off SwissTransfer.

New permanent folder link (self-hosted):

Folder name: fiber-link-milestone-2-acceptance

We’ll keep subsequent milestone artifacts organized there as well.

感谢建议，我们已经把 M2 验收材料从 SwissTransfer 迁出。

新的长期文件夹链接（自托管）：

目录名：fiber-link-milestone-2-acceptance

后续里程碑材料也会继续按这个方式整理维护。

4 Likes
26

[Weekly Update] Fiber Link (Milestone 3) / 周报(里程碑 3)

Quick update for this week:

  • We completed the Admin controls scope for Milestone 3, including:
    • monitoring summary
    • global rate limiting controls
    • backup capture + restore-plan generation
  • Review hardening items for this scope were addressed and merged in:
  • This closes the admin-ops part of the M3 checklist on our side.

Admin controls preview (monitoring / rate limiting / backup):

step9-admin-restore-plan
step9-admin-restore-plan1280×3599 300 KB

本周简要更新：

step9-admin-restore-plan
step9-admin-restore-plan1280×3599 300 KB

7 Likes
CKB Ecosystem Biweekly Update
27

M2 Payout
https://explorer.nervos.org/transaction/0x85fb0634ab39ed5f9b5d0fd4f22d6352a76d3102dc5d35581c6c7afa05b0294c

5,111,822 CKB (equivalent to $8,000 at 0.001565 CKB/USD, representing the 40% of full grants)

2 Likes
CKB Ecosystem Biweekly Update
28

@zz_tovarishch Thanks for the update — confirmed on our side. We’ll continue posting progress updates here.

@zz_tovarishch 感谢同步，我们这边已确认。后续进展我们会继续在本帖更新。

3 Likes
29

[Weekly Update] Fiber Link (Milestone 3) / 周报(里程碑 3)

Quick update for this week:

We skipped the update last week because most of the work went into preparing a broader public test for Fiber Link.

At this point, people who want to try the creator side can contact us here to request a test account:

What is available for this round is mainly the creator flow:

  • receiving tips
  • checking balances
  • making withdrawals

The reader-side tipping experience still depends on liquidity from a shared public Fiber node. We’re actively discussing that part with the ECO Fund side.

We’ll keep posting updates here as things move forward.

本周更新：

上周没有发更新，主要是在准备 Fiber Link 面向更大范围公开测试的事情。

现阶段，如果有人想体验创作者侧流程，可以通过这里联系我们申请测试账户：

这一轮目前主要可以体验的是创作者流程，包括：

  • 接受打赏
  • 查看余额
  • 发起提现

读者侧的打赏体验，暂时还需要依赖公共 Fiber 节点提供流动性支持。这部分我们也在和 ECO Fund 持续沟通。

后面有新的进展，我们会继续在这个帖子里更新。

6 Likes
CKB Ecosystem Biweekly Update
30

[Weekly Update] Fiber Link (Milestone 3) / 周报(里程碑 3)

Quick update for this week:

We continued operating Fiber Link’s long-term public demo on Testnet, and the overall environment remains stable with all core services running normally.

As of now, the demo has accumulated:

  • 109 successful tips
  • 32 successful withdrawals
  • 1 channel rotation used to replenish withdrawal liquidity

Some representative samples and evidence are collected here:

At the same time, we are also preparing a more operator-friendly deployment and plugin installation guide to support future handoff and independent operation:

本周更新：

我们继续在 Testnet 上运行 Fiber Link 的长期公开 Demo，目前整体环境保持稳定，核心服务均正常运行。

截至目前，Demo 已累计完成：

  • 109 笔成功打赏
  • 32 笔成功提现
  • 1 次用于补充提现流动性的 channel rotation

部分样例与证据已整理在这里：

同时，我们也在准备一份更适合运营人员使用的部署与插件安装指南，用于后续交接和独立运维：

2 Likes
31

[Weekly Update] Fiber Link (Milestone 3) / 周报(里程碑 3)

Quick update for this week:

The public demo has now been running for 18 days, and the core functionality has stayed stable overall.

During this time, we found and fixed a few operations-side experience issues. After a bit more observation and verification, we will deliver Milestone 3.

本周更新：

Fiber Link 的 public demo 到现在已经运行了 18 天，核心功能整体比较稳定。

这段时间里，我们发现并修复了几个运维侧的体验问题。再经过一段时间的观察和验证后，我们将交付 Milestone 3。

7 Likes
32

demo.fiberlink.me

请问这个是 Demo 连接吗？目前是否已经暂时下架等待后续 Milestone 更新后再重新上架？

33

Hi @Ckroamer Demo 没有下架, 是最近一个更新要适配不同版本的 Discourse(即论坛服务), 导致论坛数据库迁移异常, 我们已经安排同事去处理了
异常出现在不同版本的 Discourse 部署迁移过程, 和 Fiber Link 服务无关, 也不影响支付和提现.

1 Like
34

我们先恢复了 Discourse 论坛服务以便公开访问和体验, 之前的论坛帖子等数据将在今天稍晚从上一版服务迁移过来

35

Fiber Link Product Delivery Report

1. Project Overview

Fiber Link is a payment and tipping infrastructure designed for community use cases, with initial support focused on Discourse communities. It enables community users to initiate Tips directly from posts or replies, and provides an end-to-end flow for payment request creation, payment, settlement, creator revenue visibility, and withdrawals.

The focus of this delivery is to move Fiber Link from an “engineering-usable implementation” to a “product-ready, reviewable, verifiable, and deployable” state. In addition to the Live Demo and Milestone 3 acceptance evidence, the main product documentation has also been completed for reviewers, deployers, Discourse administrators, and service operators.

Main entry point:

2. Delivery Scope

This delivery covers the following core areas:

  • Discourse Tip experience, including video demo
  • Backend service deployment documentation
  • Discourse plugin installation and configuration documentation
  • Architecture and Security Documentation
  • Milestone 3 acceptance and delivery evidence index

3. User-Facing Product Capabilities

Fiber Link currently supports the following core product loop:

YouTube: https://youtu.be/xdPp42APukw

4. Deployment and Service Documentation

4.1 Backend Stack Deployment

This document covers:

  • Postgres
  • Redis
  • Fiber node / FNN
  • Fiber Link RPC service
  • Fiber Link worker
  • health checks
  • smoke verification
  • basic deployment flow

4.2 Compose Service Reference

This document helps operators understand the Docker Compose service structure, service names, ports, runtime behavior, and local smoke test flow.

4.3 Mainnet / Production-Like Deployment Checklist

This document supports pre- and post-launch checks, including:

  • preflight checks
  • rollback
  • post-deploy verification
  • production readiness

4.4 Monitoring and Operations

This document is used to verify runtime status and monitoring after deployment.

5. Discourse Plugin Installation and Configuration Documentation

Discourse administrators can use the following documentation to install, enable, configure, and verify the Fiber Link plugin.

5.1 Discourse Plugin Admin

This document covers:

  • Fiber Link plugin installation
  • Discourse admin settings
  • backend service URL configuration
  • app ID / app secret configuration
  • Tip action verification
  • creator dashboard verification
  • plugin-to-backend connectivity checks

5.2 Admin Installation

This document provides a shorter installation and verification guide for administrators who need a quick execution path.

6. Architecture and Security Documentation

Fiber Link currently uses an MVP model based on a hosted hub and an internal ledger, so its security boundaries and operational assumptions must be clearly documented.

Core documents:

  1. Current Architecture

  2. Security Assumptions

  3. Threat Model

  4. Security Controls Evidence Map

These documents explain:

  • relationships between system components
  • hosted custody / hosted hub assumptions
  • assets that operators must protect
  • risk boundaries
  • security controls and evidence mapping

7. Milestone 3 Acceptance and Evidence

7.1 Acceptance Tracker

Used to review the milestone and checkpoint overview.

7.2 Milestone 3 Acceptance Index

Used to review Milestone 3 acceptance items, including:

  • creator withdrawal workflow
  • admin controls
  • production hardening
  • mainnet deployment checklist
  • final acceptance criteria

7.3 Milestone 3 Evidence Index

Used to review the delivery evidence index for Milestone 3.

8. Recommended Reading Path for Reviewers

If reviewers have limited time, the following six links are recommended:

  1. Product overview
    fiber-link/README.md at main · Keith-CY/fiber-link · GitHub

  2. Getting started
    fiber-link/docs/getting-started.md at main · Keith-CY/fiber-link · GitHub

  3. Current status
    fiber-link/docs/current-status.md at main · Keith-CY/fiber-link · GitHub

  4. Backend deployment
    fiber-link/docs/runbooks/fiber-link-stack-deployment.md at main · Keith-CY/fiber-link · GitHub

  5. Discourse plugin installation / admin guide
    fiber-link/docs/runbooks/discourse-plugin-admin.md at main · Keith-CY/fiber-link · GitHub

  6. Milestone 3 acceptance
    fiber-link/docs/acceptance/milestone-3/index.md at main · Keith-CY/fiber-link · GitHub

9. Delivery Artifacts

Fiber Link 产品交付报告

1. 项目概览

Fiber Link 是一个面向社区场景的支付与打赏基础设施，当前优先支持 Discourse 社区。它允许社区用户直接在帖子或回复中发起 Tip，并提供从支付请求生成、支付、结算，到创作者收入展示与提现的完整流程。

本次交付的重点，是将 Fiber Link 从“工程上可运行的实现”，整理为“产品级、可评审、可验证、可部署”的状态。除了提供 Live Demo 和 Milestone 3 验收证据 外，也补充完善了面向 reviewer、部署者、Discourse 管理员以及服务运营者的主线产品文档。

主入口：

2. 本次交付范围

本次交付主要覆盖以下核心内容：

  • Discourse Tip 使用体验与视频演示
  • Backend service 部署文档
  • Discourse 插件安装与配置文档
  • 架构与安全文档
  • Milestone 3 验收与交付证据索引

3. 用户可见产品能力

Fiber Link 当前支持的核心产品闭环：

YouTube: https://youtu.be/xdPp42APukw

4. 部署与服务文档

4.1 Backend Stack 部署

该文档覆盖：

  • Postgres
  • Redis
  • Fiber node / FNN
  • Fiber Link RPC service
  • Fiber Link worker
  • health check
  • smoke verification
  • 基础部署流程

4.2 Compose 服务参考

该文档用于帮助运营者理解 Docker Compose 的服务结构、服务名称、端口、运行方式以及本地 smoke 测试流程。

4.3 主网 / 类生产环境部署检查

该文档用于上线前后的检查，包括：

  • preflight checks
  • rollback
  • post-deploy verification
  • production readiness

4.4 监控与运维

该文档用于部署后的运行状态检查与监控确认。

5. Discourse 插件安装与配置文档

Discourse 管理员可以通过以下文档完成 Fiber Link 插件的安装、启用、配置与验证。

5.1 Discourse Plugin Admin

该文档覆盖：

  • Fiber Link 插件安装
  • Discourse 管理员设置
  • backend service URL 配置
  • app ID / app secret 配置
  • Tip 功能验证
  • creator dashboard 验证
  • plugin 与 backend 的连接检查

5.2 Admin Installation

该文档提供更简洁的安装与验证说明，适合管理员快速执行。

6. 架构与安全文档

Fiber Link 当前采用基于 hosted hub 与内部 ledger 的 MVP 模型，因此其安全边界与运营假设需要被明确记录。

核心文档包括：

  1. Current Architecture

  2. Security Assumptions

  3. Threat Model

  4. Security Controls Evidence Map

这些文档说明了：

  • 系统组件之间的关系
  • hosted custody / hosted hub 的假设
  • 运营者需要保护的资产
  • 风险边界
  • 安全控制与证据映射

7. Milestone 3 验收与证据

7.1 Acceptance Tracker

用于查看 milestone 与 checkpoint 总览。

7.2 Milestone 3 Acceptance Index

用于查看 Milestone 3 的验收项，包括：

  • creator withdrawal workflow
  • admin controls
  • production hardening
  • mainnet deployment checklist
  • final acceptance criteria

7.3 Milestone 3 Evidence Index

用于查看 Milestone 3 的交付证据索引。

8. Reviewer 推荐阅读路径

如果 reviewer 时间有限，建议优先阅读以下 6 个链接：

  1. Product overview
    fiber-link/README.md at main · Keith-CY/fiber-link · GitHub

  2. Getting started
    fiber-link/docs/getting-started.md at main · Keith-CY/fiber-link · GitHub

  3. Current status
    fiber-link/docs/current-status.md at main · Keith-CY/fiber-link · GitHub

  4. Backend deployment
    fiber-link/docs/runbooks/fiber-link-stack-deployment.md at main · Keith-CY/fiber-link · GitHub

  5. Discourse plugin installation / admin guide
    fiber-link/docs/runbooks/discourse-plugin-admin.md at main · Keith-CY/fiber-link · GitHub

  6. Milestone 3 acceptance
    fiber-link/docs/acceptance/milestone-3/index.md at main · Keith-CY/fiber-link · GitHub

9. 交付物

7 Likes
CKB Ecosystem Biweekly Update
CKB Ecosystem Biweekly Update
36

Great job. Is there any future plan for this project? I am wondering if there is a chance that we can use FiberLink to tip posts in the nervos talks.

1 Like
37

Yes we do have a plan, we are extending the scope to other platforms, e.g.

In fact, our first real-world target is Nervos Talk, that’s why we chose Discourse as the first platform to integrate with.

But, to be honest, Fiber Link entering the real-world tipping ecosystem isn’t something that can be done from just one side. As I mentioned before, there are two key pieces we still need:

  1. a wallet with strong Fiber support and good liquidity;
  2. and a stablecoin that can be on-ramp/off-ramp easily.
3 Likes
38

我觉得如果第一个真实目标是 Nervos Talk，那么稳定币并不是问题。在 Nervos Talk 上打赏用 CKB 是非常自然的事情。对 Nervos Talk 的用户来说，我相信接受度不会比稳定币来得低。

2 Likes
39

Yes, for adoption on Nervos Talk, the liquidity of stablecoin won’t be a problem.
But we should not be limited in CKB ecosystem, becuase users of CKB are already in. The target should be users outside the circle. For those users, the liquidity of stablecoin would be in the first place.
As we said before, CKB will be the underlying infra, Apps are built opon it. CKB should be invisble to users.

1 Like
41

但我们不应该局限于 CKB 生态系统，因为 CKB 的用户已经在其中了。目标应该是圈子外的用户。对于那些用户来说，稳定币的流动性将是首要考虑的问题。

我觉得这属于第二阶段。如果第一个真实目标是 nervos talk，那么就不应该在这个阶段考虑是否会局限于 CKB 生态系统。它应该是个由内而外、从 CKB 生态向更多非 CKB 用户扩散的过程。在这个扩散的过程中，产品有时间慢慢去迭代解决这些更深度的问题。

反过来说，如果一开始我们考虑的场景就是面向圈外的主流用户，那么把 CKB 隐藏起来是对的，使用稳定币、更好的钱包这些都是正确的思路。

我认为这两种思路都可以尝试。但这里我担心的是，我们瞄准的第一个真实的目标（nervos talk）并没有先用起来，同时，对外的非 CKB 用户对此也不关心。这就像我看到目前已经在考虑集成 discourse 之外的其他类似 telegram 这样的平台，我其实会打个问号，是否应该马上去支持更多的平台，还是先把第一个主力平台做起来。

当然，我理解做产品的人有自己的想法和节奏。我仅提供一些个人视角的反馈。期待 Fiber Link 后面有更多的进展。

3 Likes