[DIS] Nexus Platform 提案

Nexus Video Platform — CKB 生态去中心化内容平台
CKB Community Fund DAO 提案
申请类别: CKB Community Fund DAO
申请人: Zhang Hao
联系方式: Discord
申请金额: 等值 $40,000 USD(100% 以 CKB 结算)
项目周期: 12 周
项目状态: 已有可运行原型(v2.8.0),申请资金用于 UI 优化、Bug 修复、测试、安全加固与主网部署

  1. 项目概述
    Nexus 是一个生产级全栈去中心化内容平台,融合了 YouTube/Spotify/Medium 的用户体验与 CKB 区块链的所有权和支付基础设施。

一句话定位
基于 CKB 生态的多媒体内容平台 — 视频·音乐·文章·直播·AI 工具,集成 JoyID 免助记词登录、Fiber Network L2 按秒计费、Spore NFT 内容确权、RGB++ 自动分账。

核心特性
特性 说明 CKB 生态协议
:clapper_board: 按秒计费流支付 看多少付多少,不订阅 Fiber Network L2
:id_button: 无助记词登录 生物识别 Passkey JoyID
:artist_palette: 内容 NFT 7 类数字物 (DOB) Spore Protocol
:money_bag: 自动分账 创作者 70% / 平台 20% / 推荐人 10% RGB++
:robot: AI 工具市场 AI 工具所有权 NFT + Fiber 支付 Spore + Fiber
:classical_building: DAO 治理 代币加权投票提案 CKB 原生
已建成规模
指标 数值
后端微服务 18 个 (Fastify 4, TypeScript)
前端页面 65 个 (React 18, Vite 5)
UI 组件 58+
Prisma 数据模型 30+ (1,176 行 Schema)
CLI 命令 30+ (Agent-Native)
CKB 协议集成 7 个 (JoyID / Fiber / Spore / RGB++ / CCC / .bit / Nostr)
版本 v2.8.0
IMPORTANT

Nexus 不是概念或白皮书。它是一个 已可运行的产品(v2.8.0),拥有完整的前后端代码、CI/CD 流水线、测试套件和 Docker 部署配置。
本提案申请的资金用于 UI 打磨、Bug 修复、全面测试、安全加固和主网上线。

  1. 问题背景
    内容创作者在 Web3 中面临的困境
    现有方案 问题
    YouTube / Bilibili 平台控制分发与收入;创作者无内容所有权
    订阅制 (Netflix) 用户为不看的内容付费;创作者收入不透明
    L1 链上 NFT 平台 Gas 费高、确认慢、用户需管理助记词
    现有 CKB DApp 功能单一,缺少多媒体内容场景的完整产品
    Nexus 的价值
    对用户: JoyID 生物识别登录(零助记词),按秒付费(看 30 秒只付 30 秒的钱)
    对创作者: RGB++ 自动分账,零代码铸造内容 NFT,AI 创作工具
    对 CKB 生态: 首个综合性多媒体 DApp,展示 Fiber / Spore / RGB++ 的真实应用场景
  2. 技术架构
    3.1 系统全景
    ┌──────────────────────────────────────────────────────────┐
    │ Client (React 18 + Vite 5) │
    │ 65 Pages · 58+ Components │
    └───────────────────────┬──────────────────────────────────┘

    ┌──────────────────────────────────────────────────────────┐
    │ Identity / API Gateway (:8080) │
    │ JWT · Route Proxy · Circuit Breaker · Rate Limit │
    └──┬───┬───┬───┬───┬───┬───┬───┬───┬───┬───┬───┬────┬────┘
    ▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼
    Payment Content Meta Royalty NFT Live Govern Achieve Engage
    :8091 :8092 :8093 :8094 :8095 :8096 :8098 :8097 :8104
    • 9 more: AI-Gen, Bridge, Search, Transcode,
      Messaging, Moderation, Recommend, Collab
      ┌──────────────────────────────────────────────────────────┐
      │ Infrastructure (Docker Compose) │
      │ PostgreSQL 16 · Redis 7 · MinIO · MeiliSearch │
      │ Consul · Prometheus · Grafana · Fiber Node │
      └──────────────────────────────────────────────────────────┘
      3.2 CKB 生态集成
      协议 状态 实现
      JoyID Passkey :white_check_mark: 已集成 生物识别登录 + CKB 转账签名验证
      Fiber Network :white_check_mark: 已集成 完整 RPC Client (455 行): 发票/查询/支付/通道
      Spore Protocol :white_check_mark: 已集成 7 类 NFT 铸造 + 市场交易
      RGB++ :white_check_mark: 已集成 自动分账合约 (Rust/Cargo)
      CCC :white_check_mark: 已集成 统一钱包连接器
      .bit (d.id) :white_check_mark: 已集成 去中心化身份解析
      3.3 支付系统
      用户操作 后端处理 区块链层
      ───────────────────────────────────────────────────────────────
      按秒观看视频 ──→ Stream Pay State Machine ──→ Fiber Invoice
      购买内容 ──→ Points Deduction ──→ CKB L1
      打赏创作者 ──→ Tip Settlement Worker ──→ Fiber Payout
      NFT 铸造 ──→ Spore Mint Pipeline ──→ CKB L1
      分账结算 ──→ Universal Split Engine ──→ RGB++ Contract
      积分充值 ──→ CKB Purchase Intent ──→ CKB L1 验证
  3. 本提案工作范围
    :white_check_mark: 已完成(不在本提案范围内)
    模块 状态
    18 后端微服务核心逻辑 :white_check_mark:
    65 前端页面 + 58 组件 :white_check_mark:
    JoyID / Fiber / Spore / RGB++ 全部集成 :white_check_mark:
    Docker Compose 开发环境 :white_check_mark:
    CI/CD 6 阶段流水线 :white_check_mark:
    Prometheus + Grafana 监控 :white_check_mark:
    Agent-Native CLI (30+ 命令) :white_check_mark:
    AI Studio (文章/音乐/视频生成) :white_check_mark:
    :wrench: 本提案资金覆盖的工作
    模块 优先级 说明
    UI 优化与打磨 P0 65 页面的视觉一致性、骨架屏、响应式适配、动画优化、设计 Token 统一
    Bug 修复 P0 网关路由 404/500 已知问题、支付流程边界 case、前端状态同步问题
    全面测试 P0 E2E 全流程覆盖、支付安全测试、并发压力测试、CKB 链上验证测试
    安全加固 P0 密钥管理加固、依赖审计、渗透测试、支付防重放、速率限制完善
    主网部署 P1 Fiber Hub 节点主网 + 通道流动性 + Spore 主网铸造 + RGB++ 主网分账
    生产部署 P1 Docker 生产镜像、Nginx、SSL、日志归集、备份策略
    前端性能优化 P1 Bundle 拆分、虚拟列表、LazyImage、React Query v5 升级
    文档与社区 P2 API 文档、用户指南、运维手册、CKB 集成教程
  4. 里程碑与时间计划(12 周)
    里程碑 1(第 1-4 周):Bug 修复 + 安全加固 + UI 打磨
    交付项 细节
    已知 Bug 修复 网关 404/500 路由问题、支付边界逻辑、前端状态不同步
    安全审计与加固 密钥管理 (加密存储)、依赖 npm audit、渗透测试、支付防重放
    UI 一致性优化 设计 Token 统一 (颜色/间距/圆角)、骨架屏完善、响应式适配
    核心页面体验打磨 优先打磨核心用户路径页面 (Home / Login / VideoPlayer / PointsCenter / CreatorDashboard / NFTMarketplace 等约 20 个高频页面),其余页面持续迭代
    验收标准: 零 Critical/High 安全漏洞、已知 Bug 全部修复、核心页面 UI 一致性达标

里程碑 2(第 5-8 周):全面测试 + 性能优化 + 链上闭环
交付项 细节
E2E 测试覆盖 核心支付路径 100% 覆盖:注册 → 充值 → 观看 → 付费 → 打赏 → NFT → 提现
压力测试 k6 负载测试:并发支付、高频打赏、大量 Fiber 发票
前端性能优化 Bundle 拆分 (video.js/three.js 按路由)、虚拟列表、缓存策略
Fiber 主网部署 Hub 节点主网部署 + 初始流动性 + 多通道建立
CKB L1 转账闭环 端到端验证:构建 → 签名 → 广播 → 确认 → 入账
Spore + RGB++ 主网 NFT 主网铸造验证 + 分账合约主网部署
验收标准: 核心支付路径 E2E 100% 通过、k6 p95 ≤ 500ms、Fiber/Spore/RGB++ 主网可验证

NOTE

主网部署视 CKB Fiber Network / Spore Protocol 主网协议状态而定。如主网协议尚未完全就绪,将提供测试网完整端到端演示,并在主网就绪后第一时间完成迁移部署。

里程碑 3(第 9-12 周):生产部署 + 文档 + 运维
交付项 细节
生产环境部署 Docker 生产镜像 + Nginx 反代 + SSL + 日志归集
监控完善 Grafana Dashboard 扩充、异常告警规则、业务指标
运维自动化 备份脚本、数据库迁移、日志轮转、紧急回滚流程
完整文档 用户指南、API 文档 (OpenAPI)、运维手册、CKB 集成教程
开源社区 Contributing Guide、Issue 模板、README 完善、技术博客
生态推广 演示视频、CKB 社区展示、测试网 + 主网 Demo 实例
验收标准: 主网可访问的实例、完整文档、监控告警正常运行

  1. 预算申请
    申请金额
    项目 金额
    总额 等值 $40,000 USD
    结算方式 100% 以 CKB 支付
    成本明细
    类别 预算 (USD) 说明
    UI 优化与打磨 $5,000 65 页面视觉一致性、响应式、动画、设计 Token
    Bug 修复 $3,000 已知路由问题、支付边界、状态同步
    安全加固 $5,000 安全审计 + 密钥管理 + 渗透测试 + 防重放
    全面测试 $4,000 E2E 覆盖 + 压力测试 + 链上验证测试
    主网部署工程 $6,000 Fiber/Spore/RGB++ 主网部署 + 链上闭环验证
    性能优化 $3,500 前端 Bundle + 后端缓存 + 数据库调优
    生产 DevOps $3,500 Docker 配置 + Nginx + SSL + 监控 + 日志
    文档与社区 $2,000 API 文档 + 用户指南 + 运维手册 + 博客
    Fiber 通道流动性 $2,000 主网通道初始 CKB + UDT 流动性
    基础设施 (12 个月) $3,400 VPS + DB + 监控 + 备份 ≈ $280/月
    预备金 (~7%) $2,600 Fiber 协议升级适配、未预见 Bug
    合计 $40,000
    付款计划
    里程碑 比例 等值 USD
    里程碑 1 完成 25% $10,000
    里程碑 2 完成 40% $16,000
    里程碑 3 完成 35% $14,000
    总计 100% $40,000
  2. 为什么 CKB 社区应该支持这个项目
    对 CKB 生态的贡献
    首个综合性多媒体 DApp — 让 Fiber/Spore/RGB++ 有真实的应用场景和链上交易量
    用户零门槛 — JoyID 生物识别登录,对 Web2 用户完全友好
    协议集成代码全部开源 — 其他项目可参考 Fiber/Spore/RGB++ 集成最佳实践
    真实交易量 — 按秒计费 + 打赏 + NFT 市场为 CKB 网络带来真实活跃用户
    差异化优势
    维度 Nexus 竞品/现有
    内容类型 视频 + 音乐 + 文章 + 直播 + AI(尝试做AI结算曾,AI工具市场,调用,确权+自动化结算) 通常单一类型
    支付方式 Fiber L2 按秒计费 L1 按次或订阅
    身份验证 JoyID (无助记词) MetaMask (需助记词)
    内容确权 Spore NFT
    分账机制 RGB++ 自动合约分账 手动或中心化
    项目状态 v2.8.0 已可运行 多数为概念/MVP
    微服务数 18 个生产级服务 通常单体
  3. 公开进度更新
    :memo: 每周论坛帖子发布进度
    :laptop: GitHub 提交记录与 Release Tag
    :clapper_board: 每个里程碑交付演示视频
    :bar_chart: 链上交易数据公开透明
    :globe_with_meridians: 测试网 + 主网 Demo 实例实时可访问
  4. 团队与联系
    项目 说明
    申请人 Zhang Hao
    联系方式 Discord
    GitHub github.com/alefnt/nexus-video-platform
    项目版本 v2.8.0 (2026-03-10)
    代码语言 TypeScript 100%
    许可证 MIT

English:

Nexus Video Platform — Decentralized Content Platform on CKB

CKB Community Fund DAO Proposal

Category: CKB Community Fund DAO
Applicant: Zhang Hao
Contact: Discord
Requested Amount: $40,000 USD equivalent (100% settled in CKB)
Timeline: 12 weeks
Project Status: Working prototype (v2.8.0) — funding for UI polish, bug fixes, testing, security hardening, and mainnet deployment


1. Summary

Nexus is a production-grade, full-stack decentralized content platform (DCP) that merges the user experience of YouTube, Spotify, and Medium with the ownership and payment infrastructure of the CKB blockchain.

One-liner

A multi-media content platform built on the CKB ecosystem — Video · Music · Articles · Live Streaming · AI Tools — featuring JoyID passwordless login, Fiber Network L2 per-second billing, Spore NFT content ownership, and RGB++ automated revenue splits.

Core Features

Feature Description CKB Protocol
:clapper_board: Per-Second Billing Pay only for what you watch — no subscriptions Fiber Network L2
:id_button: Passwordless Login Biometric Passkey authentication JoyID
:artist_palette: Content NFTs 7 categories of Digital Objects (DOBs) Spore Protocol
:money_bag: Auto Revenue Splits Creator 70% / Platform 20% / Referrer 10% RGB++
:robot: AI Tool Marketplace AI tool ownership NFTs + Fiber payments Spore + Fiber
:classical_building: DAO Governance Token-weighted proposal voting CKB Native

What’s Already Built

Metric Value
Backend Microservices 18 (Fastify 4, TypeScript)
Frontend Pages 65 (React 18, Vite 5)
UI Components 58+
Prisma Models 30+ (1,176-line schema)
CLI Commands 30+ (Agent-Native)
CKB Protocol Integrations 7 (JoyID / Fiber / Spore / RGB++ / CCC / .bit / Nostr)
Current Version v2.8.0

IMPORTANT

Nexus is not a concept or whitepaper. It is a working product (v2.8.0) with complete frontend and backend code, a CI/CD pipeline, test suites, and Docker deployment configs.
This proposal requests funding for UI polish, bug fixes, comprehensive testing, security hardening, and mainnet deployment.


2. Problem Statement

The Content Creator Dilemma in Web3

Existing Solution Problem
YouTube / Bilibili Platform controls distribution and revenue; creators have no content ownership
Subscription (Netflix) Users pay for content they don’t watch; creator revenue is opaque
L1 On-Chain NFT Platforms High gas fees, slow confirmations, users must manage seed phrases
Existing CKB DApps Single-purpose tools lacking a comprehensive multimedia application

Nexus Value Proposition

  1. For Users: JoyID biometric login (zero seed phrases), per-second billing (watch 30 seconds, pay for 30 seconds)

  2. For Creators: RGB++ automated revenue splits, zero-code content NFT minting, AI creation tools

  3. For the CKB Ecosystem: The first comprehensive multimedia DApp showcasing real-world usage of Fiber / Spore / RGB++


3. Technical Architecture

3.1 System Overview

┌──────────────────────────────────────────────────────────┐

│ Client (React 18 + Vite 5) │

│ 65 Pages · 58+ Components │

└───────────────────────┬──────────────────────────────────┘

┌──────────────────────────────────────────────────────────┐

│ Identity / API Gateway (:8080) │

│ JWT · Route Proxy · Circuit Breaker · Rate Limit │

└──┬───┬───┬───┬───┬───┬───┬───┬───┬───┬───┬───┬────┬────┘

▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼

Payment Content Meta Royalty NFT Live Govern Achieve Engage

:8091 :8092 :8093 :8094 :8095 :8096 :8098 :8097 :8104

          + 9 more: AI-Gen, Bridge, Search, Transcode,

            Messaging, Moderation, Recommend, Collab

┌──────────────────────────────────────────────────────────┐

│ Infrastructure (Docker Compose) │

│ PostgreSQL 16 · Redis 7 · MinIO · MeiliSearch │

│ Consul · Prometheus · Grafana · Fiber Node │

└──────────────────────────────────────────────────────────┘

3.2 CKB Ecosystem Integration

Protocol Status Implementation
JoyID Passkey :white_check_mark: Integrated Biometric login + CKB transaction signature verification
Fiber Network :white_check_mark: Integrated Full RPC Client (455 lines): invoices, queries, payments, channels
Spore Protocol :white_check_mark: Integrated 7 NFT categories: minting + marketplace
RGB++ :white_check_mark: Integrated Automated revenue split contracts (Rust/Cargo)
CCC :white_check_mark: Integrated Unified wallet connector
.bit (d.id) :white_check_mark: Integrated Decentralized identity resolution

3.3 Payment System

User Action               Backend Processing            Blockchain Layer

───────────────────────────────────────────────────────────────────────

Watch video (per-sec) ──→ Stream Pay State Machine ──→ Fiber Invoice

Purchase content ──→ Points Deduction ──→ CKB L1

Tip a creator ──→ Tip Settlement Worker ──→ Fiber Payout

Mint NFT ──→ Spore Mint Pipeline ──→ CKB L1

Revenue distribution ──→ Universal Split Engine ──→ RGB++ Contract

Top up points ──→ CKB Purchase Intent ──→ CKB L1 Verify


4. Scope of This Proposal

:white_check_mark: Already Completed (Not in scope)

Module Status
18 backend microservices — core logic :white_check_mark:
65 frontend pages + 58 components :white_check_mark:
JoyID / Fiber / Spore / RGB++ — full integration :white_check_mark:
Docker Compose development environment :white_check_mark:
CI/CD 6-stage pipeline :white_check_mark:
Prometheus + Grafana monitoring :white_check_mark:
Agent-Native CLI (30+ commands) :white_check_mark:
AI Studio (article / music / video generation) :white_check_mark:

:wrench: Work Covered by This Proposal

Module Priority Description
UI Polish P0 Visual consistency across core pages, skeleton screens, responsive design, animation refinement, design token unification
Bug Fixes P0 Gateway routing 404/500 issues, payment edge cases, frontend state sync
Comprehensive Testing P0 E2E full-flow coverage, payment security tests, load testing, on-chain verification
Security Hardening P0 Key management, dependency audit, penetration testing, anti-replay, rate limiting
Mainnet Deployment P1 Fiber Hub node + channel liquidity + Spore mainnet minting + RGB++ mainnet settlement
Production Deployment P1 Docker production images, Nginx, SSL, log aggregation, backup strategy
Frontend Performance P1 Bundle splitting, virtual lists, LazyImage, React Query v5 upgrade
Documentation & Community P2 API docs, user guide, operations manual, CKB integration tutorial

5. Milestones & Timeline (12 Weeks)

Milestone 1 (Weeks 1–4): Bug Fixes + Security Hardening + UI Polish

Deliverable Details
Known Bug Fixes Gateway 404/500 routing issues, payment boundary logic, frontend state sync
Security Audit & Hardening Key management (encrypted storage), npm audit, penetration testing, payment anti-replay
UI Consistency Design token unification (colors / spacing / radii), skeleton screens, responsive adaptation
Core Page Experience Priority polish on ~20 high-traffic pages (Home / Login / VideoPlayer / PointsCenter / CreatorDashboard / NFTMarketplace, etc.); remaining pages iterated continuously

Acceptance Criteria: Zero Critical/High security vulnerabilities, all known bugs resolved, core page UI consistency achieved


Milestone 2 (Weeks 5–8): Testing + Performance + Mainnet

Deliverable Details
E2E Test Coverage 100% coverage of core payment paths: Register → Top-up → Watch → Pay → Tip → NFT → Withdraw
Load Testing k6 tests: concurrent payments, high-frequency tipping, bulk Fiber invoices
Frontend Performance Bundle splitting (video.js / three.js by route), virtual lists, caching strategy
Fiber Mainnet Deployment Hub node on mainnet + initial liquidity + multi-channel establishment
CKB L1 Transfer Verification End-to-end: build → sign → broadcast → confirm → credit
Spore + RGB++ Mainnet NFT mainnet minting verification + revenue split contract mainnet deployment

Acceptance Criteria: Core payment E2E 100% passing, k6 p95 ≤ 500ms, Fiber/Spore/RGB++ mainnet verifiable

NOTE

Mainnet deployment is contingent on the readiness of CKB Fiber Network and Spore Protocol mainnet. If mainnet protocols are not fully stable, a complete end-to-end testnet demonstration will be delivered, with mainnet migration completed as soon as protocols are ready.


Milestone 3 (Weeks 9–12): Production Deployment + Documentation + Operations

Deliverable Details
Production Deployment Docker production images + Nginx reverse proxy + SSL + log aggregation
Monitoring Expanded Grafana dashboards, alerting rules, business metrics
Operations Automation Backup scripts, database migrations, log rotation, emergency rollback procedures
Complete Documentation User guide, API docs (OpenAPI 3.0), operations manual, CKB integration tutorial
Open Source Community Contributing guide, issue templates, README improvements, technical blog posts
Ecosystem Outreach Demo videos, CKB community showcase, testnet + mainnet demo instances

Acceptance Criteria: Publicly accessible mainnet instance, complete documentation, monitoring and alerting operational


6. Budget Request

Requested Amount

Item Amount
Total $40,000 USD equivalent
Settlement 100% in CKB

Cost Breakdown

Category Budget (USD) Notes
UI Polish & Refinement $5,000 Visual consistency, responsive design, animations, design tokens
Bug Fixes $3,000 Known routing issues, payment edge cases, state sync
Security Hardening $5,000 Security audit + key management + penetration testing + anti-replay
Comprehensive Testing $4,000 E2E coverage + load testing + on-chain verification
Mainnet Deployment Engineering $6,000 Fiber / Spore / RGB++ mainnet deployment + chain verification
Performance Optimization $3,500 Frontend bundle + backend caching + database tuning
Production DevOps $3,500 Docker config + Nginx + SSL + monitoring + logging
Documentation & Community $2,000 API docs + user guide + ops manual + blog posts
Fiber Channel Liquidity $2,000 Mainnet channel initial CKB + UDT liquidity
Infrastructure (12 months) $3,400 VPS + DB + monitoring + backups ≈ $280/month
Contingency (~7%) $2,600 Fiber protocol upgrades, unforeseen bugs
Total $40,000

Payment Schedule

Milestone Percentage USD Equivalent
Milestone 1 Complete 25% $10,000
Milestone 2 Complete 40% $16,000
Milestone 3 Complete 35% $14,000
Total 100% $40,000

7. Why CKB Should Fund This Project

Contributions to the CKB Ecosystem

  1. First Comprehensive Multimedia DApp — Real-world application driving actual on-chain transaction volume for Fiber, Spore, and RGB++

  2. Zero-Barrier User Onboarding — JoyID biometric login is fully Web2-friendly, expanding CKB’s potential user base

  3. Open-Source Integration Code — Other projects can reference our Fiber / Spore / RGB++ integration as best practices

  4. Real Transaction Volume — Per-second billing + tipping + NFT marketplace generates genuine on-chain activity

Competitive Differentiation

Dimension Nexus Competitors
Content Types Video + Music + Articles + Live + AI Typically single-type
Payment Model Fiber L2 per-second billing L1 per-purchase or subscription
Authentication JoyID (no seed phrases) MetaMask (requires seed phrases)
Revenue Distribution RGB++ automated smart contracts Manual or centralized
Project Status v2.8.0 — already functional Mostly concept / early MVP
Backend Services 18 production-grade microservices Typically monolithic

8. Public Progress Updates

  • :memo: Weekly progress posts on the forum

  • :laptop: GitHub commits and release tags

  • :clapper_board: Demo video for each milestone delivery

  • :bar_chart: On-chain transaction data publicly transparent

  • :globe_with_meridians: Testnet + mainnet demo instances publicly accessible


9. Team & Contact

19 Likes

2 Likes

Hi @AIIA ,感谢发布提案。作为协调员,有个形式上的提醒:

如果你希望正式进入讨论阶段(Discussion Stage),帖子标题需要以 [DIS] 开头。

Hi AIIA, thanks for posting the proposal. As the coordinator, one notes on formatting:

If you intend to formally enter the Discussion Stage, the post title must start with [DIS].

1 Like

已修正,是不是可以推帮忙发一下这个提案

2 Likes

已同步社区。另外提醒一下,按照目前 v1.0 讨论阶段的规则,30 个赞是基于 [DIS] 帖子的第一楼来计算的。其他楼的赞不会计入通过条件。建议把中英文内容合并到第一楼,确保所有赞都能被有效计入。

Synchronized. And a quick reminder: under the current v1.0 Discussion Stage rules, the 30 likes are counted on the first post (floor 1) of the [DIS] thread. Other floor won’t count toward the passing threshold. I’d suggest merging both versions into the first post so that all likes are counted.

Need to be revised later

1 Like

订阅/付费/成人内容平台

  • OnlyFans:创作者拿 80%(平台抽成20%)。订阅、单次付费内容、打赏等几乎全靠这个分成。

  • Patreon:平台费约 5–12%(视计划),创作者拿 88–95%(扣除支付手续费后)。

  • Twitch:订阅收入创作者拿 50–70%(普通50%,谈判可更高);广告/打赏/Bits另算。

订阅/付费/成人内容平台

  • OnlyFans:创作者拿 80%(平台抽成20%)。订阅、单次付费内容、打赏等几乎全靠这个分成。

  • Patreon:平台费约 5–12%(视计划),创作者拿 88–95%(扣除支付手续费后)。

  • Twitch:订阅收入创作者拿 50–70%(普通50%,谈判可更高);广告/打赏/Bits另算。

总结对比($10订阅费场景)

项目 金额(美元) 说明
用户实际支付 $10 信用卡扣款,无平台额外费
平台抽成(OnlyFans) $2 固定20%,覆盖所有处理费
创作者税前到手 $8 平台支付给你(通常接近这个数)
可能银行/跨境费 $0–$1 视支付方式,多数低或无
创作者税后到手(UK估) ≈$6–$7.5 取决于你的税阶、扣除,自行申报

建议80%以上,不然没竞争力,类似的去中心化创作者平台有dfans

  1. dFans 的官方分成是 80%(创作者),20% 覆盖 referral 等(来源:平台 X 账号和 Medium)。部分早期/推广材料提 “up to 85%” 或 “更高”(如奖金、tips 无抽成旧版),但 2025-2026 年主流仍是 80/20,与 OnlyFans 一致。
  2. 平台主打 crypto 提现(即时、无最低额),适合想避开传统银行的创作者。但 UK 用户用 crypto 收入需合规报税(HMRC 视作自雇或杂项收入)。
  3. 与 OnlyFans 比,dFans 用户基数小(增长中),但无审查、更自由(包括 AI 内容),适合 niche/隐私需求高的创作者。

另外你这个平台肯定不允许nsfw吧,如何审核违禁内容呢,谁审核呢

1 Like

Revenue sharing isn’t the primary concern right now, but it will likely be implemented with tiered pricing. The platform’s goal isn’t profit; it’s simply to showcase what CKB can and offers, covering basic operating expenses. Content review will involve a combination of automated agent review and manual review (though this might not be the case at all).

To some extent, the first goal of this application is to showcase what CKB has and what it can do to the public; the second goal is to expand and improve it.

Current multimodal big data capabilities are sufficient to automate content moderation.

dFans 是‘给创作者发工资的工厂’,而我们项目是‘让创作者和推广者共建的资产化社区’。(平台冷启动是最难的点,如何把平台做大,蛋糕做大会是比短期的分成比例更需要优先考虑的事情)

With all due respect, a one-person showcase project (that clearly wasn’t even intended to be properly marketed) asking for $40,000

I’ve also seen you often say in the community that you want CKB to do well. But from the outside, what you’re doing doesn’t really look like you’re trying to help it succeed — it feels more like you’re here to punish it. :grinning_face_with_smiling_eyes:

1 Like

Partner, thank you for pointing out your concerns and doubts. Let me address your questions from the following angles: 1. This isn’t just a simple demo project. It’s not something you build and then do nothing. The ultimate goal is to get Nexus running. But you need to understand, this path isn’t easy and depends on many factors. My goal is definitely to make Nexus truly operational and usable worldwide. 2. I know you’re worried that I’m trying to scam funding from DAO. But I’ll be frank: how much money you ask for often depends on how much work you do. I’ve already sent you the GitHub link; you can see what’s been built if you’re interested. 3. One-person team issue: Dude, I came up with this idea and started building it, but if Nexus is truly running, I can’t handle everything alone. So, if you’d like, you can join in and play your role.

3 Likes

Or, to put it another way, you could completely fork this project, if you’re willing, and then propose a reasonable price and a future product development roadmap. I would then give you my personal “like.”

2 Likes

Brother, I know that no one who’s stuck with CKB has had an easy time. I’ve been with CKB for six years too. Six years ago, I was considered a CKB hater, but the most interesting thing is that I’ve held onto my CKB for six years. To be honest, I felt hopeless, but what could I do? So I started building my own product, trying to market and showcase CKB. This isn’t to say CKB is bad, it’s just that in this environment, bad money drives out good.

1 Like

On project scale — “one-person showcase”:

Anyone can clone the repo and verify these numbers:

  • 325 TypeScript source files, 80,811 lines of code

  • 18 backend microservices (16,975 LOC), 65 frontend pages + 90 components (51,125 LOC)

  • 55 Prisma database models (1,071-line schema)

  • 7 CKB protocol integrations (JoyID / Fiber / Spore / RGB++ / CCC / .bit / Nostr)

This is not a weekend hackathon. At industry-standard productivity (~50-100 LOC/day for production code), this represents 800-1,600 working days of effort — already delivered before requesting any funding.

On budget — “$40,000 is too much”:

$40,000 / 12 weeks = ~$3,333/week. A Web3 full-stack developer’s market rate is $2,000-$6,000/week depending on region. A single smart contract audit costs $5,000-$15,000/week. This budget covers security hardening, comprehensive testing (E2E + load testing), mainnet deployment, and documentation — not building from scratch.

On marketing:

Marketing is intentionally out of scope for this phase. $40K must prioritize product security and stability first. A broken product with marketing is worse than a solid product waiting for the right timing.

On “trying to help CKB succeed”:

The CKB ecosystem’s biggest gap today isn’t protocols — it’s real-world applications proving those protocols work. Nexus is currently the only project integrating Fiber streaming payments, Spore NFT minting, and RGB++ revenue splits into a single working product. Every protocol needs at least one reference application to demonstrate real-world value.

The code is fully open-source: https://github.com/alefnt/nexus-video-platform I welcome any technical review.

3 Likes

and joyid

40k$ are at the moment 12% of the community DAO-Fund.

I won’t comment on any specific proposals, but let’s take a moment to look back: what were the requested amounts for past proposals? What was actually built? How many users did they attract? And how much value did they truly add to CKB? Look, brother—I could simply hand this entire project directly over to the project team (provided they’re willing to accept it). The code is already open-source on GitHub, and the project itself is completely free. Peace & Love

1 Like

This is exactly what i did, i looked at past proposals. What makes u confident this project will be different?

1 Like