{ "base_url": "https://talk.nervos.org", "generated_at": "2026-05-09T17:50:11.777146+00:00", "since": "2026-05-08T17:49:58.482666+00:00", "until": "2026-05-09T17:49:58.482666+00:00", "window_hours": 24, "topics": [ { "topic_id": 10143, "title": "Pre-RFC Discussion: Activating the Nervos DAO Treasury", "slug": "pre-rfc-discussion-activating-the-nervos-dao-treasury", "url": "https://talk.nervos.org/t/pre-rfc-discussion-activating-the-nervos-dao-treasury/10143", "created_at": "2026-03-31T03:10:02.859000+00:00", "last_posted_at": "2026-05-09T16:11:47.608000+00:00", "category_id": 31, "tags": [ "CKB" ], "posters": [ "Original Poster", "Frequent Poster", "Frequent Poster", "Frequent Poster", "Most Recent Poster" ], "recent_posts": [ { "post_id": 24174, "post_number": 15, "topic_id": 10143, "topic_title": "Pre-RFC Discussion: Activating the Nervos DAO Treasury", "topic_slug": "pre-rfc-discussion-activating-the-nervos-dao-treasury", "author": "matt_ckb", "created_at": "2026-05-09T01:44:00.913000+00:00", "updated_at": "2026-05-09T01:44:28.951000+00:00", "reply_to_post_number": 13, "url": "https://talk.nervos.org/t/pre-rfc-discussion-activating-the-nervos-dao-treasury/10143/15", "content_text": "1000026048858×268 89.7 KB\nfyi Ethereum Foundation aspires to what we are doing here.\nDecentralization doesn’t matter, until one day it becomes of the utmost importance, I hope you can understand this.", "content_html": "

\"1000026048\"
1000026048858×268 89.7 KB

\n

fyi Ethereum Foundation aspires to what we are doing here.

\n

Decentralization doesn’t matter, until one day it becomes of the utmost importance, I hope you can understand this.

", "like_count": 0, "quote_count": 0 }, { "post_id": 24178, "post_number": 16, "topic_id": 10143, "topic_title": "Pre-RFC Discussion: Activating the Nervos DAO Treasury", "topic_slug": "pre-rfc-discussion-activating-the-nervos-dao-treasury", "author": "fishell", "created_at": "2026-05-09T02:44:06.365000+00:00", "updated_at": "2026-05-09T02:44:06.365000+00:00", "reply_to_post_number": 13, "url": "https://talk.nervos.org/t/pre-rfc-discussion-activating-the-nervos-dao-treasury/10143/16", "content_text": "我同意。至少应该有不同的轨道同时进行，nervos dao treasury治理显然很重要，但它应该是远期目标，中短期需要有其他dao做事情，不应该干巴巴等着。如果没有其他dao的治理经验，nervos dao treasury治理也很难让人有信心。", "content_html": "

我同意。至少应该有不同的轨道同时进行，nervos dao treasury治理显然很重要，但它应该是远期目标，中短期需要有其他dao做事情，不应该干巴巴等着。如果没有其他dao的治理经验，nervos dao treasury治理也很难让人有信心。

", "like_count": 0, "quote_count": 0 }, { "post_id": 24202, "post_number": 17, "topic_id": 10143, "topic_title": "Pre-RFC Discussion: Activating the Nervos DAO Treasury", "topic_slug": "pre-rfc-discussion-activating-the-nervos-dao-treasury", "author": "jimi-winehouse", "created_at": "2026-05-09T16:11:47.608000+00:00", "updated_at": "2026-05-09T16:11:47.608000+00:00", "reply_to_post_number": 15, "url": "https://talk.nervos.org/t/pre-rfc-discussion-activating-the-nervos-dao-treasury/10143/17", "content_text": "I do understand this and it’s why I am here and not in some other forum. But I am also pragmatic and I believe this is premature optimization in this case because the worst case scenario is the foundation gets “captured” and someone makes money off of the emissions, this is even better on PoW vs PoS chain like Ethereum where holding the token allows you to participate in consensus. Decentralizing the treasury could be as easy as killing it/switch back to burn letting the ecosystem handle itself without emissions when it’s actually profiting from the chain and the incentives are aligned. I see the treasury more as a bootstrapping mechanism than something that should exist long term. We can save the smart solutions and decentralization for where it’s actually needed, which is clearly the case already and that’s what makes Nervos special, and just have a pragmatic solution which is to just go ahead and spend money on good projects instead of giving a measly 24k$ to ideas that can be easily funded for millions elsewhere (assuming they could be built there). Maybe there’s something I am missing but this seems just like a smart solution for a non existing problem. I’d rather have some more developed argument than “We are decentralized and Ethereum wants to be like us”. It should be more like “These ecosystems are 1000x bigger, we should be like them” and clearly overengineering a treasury isn’t it.", "content_html": "

I do understand this and it’s why I am here and not in some other forum. But I am also pragmatic and I believe this is premature optimization in this case because the worst case scenario is the foundation gets “captured” and someone makes money off of the emissions, this is even better on PoW vs PoS chain like Ethereum where holding the token allows you to participate in consensus. Decentralizing the treasury could be as easy as killing it/switch back to burn letting the ecosystem handle itself without emissions when it’s actually profiting from the chain and the incentives are aligned. I see the treasury more as a bootstrapping mechanism than something that should exist long term. We can save the smart solutions and decentralization for where it’s actually needed, which is clearly the case already and that’s what makes Nervos special, and just have a pragmatic solution which is to just go ahead and spend money on good projects instead of giving a measly 24k$ to ideas that can be easily funded for millions elsewhere (assuming they could be built there). Maybe there’s something I am missing but this seems just like a smart solution for a non existing problem. I’d rather have some more developed argument than “We are decentralized and Ethereum wants to be like us”. It should be more like “These ecosystems are 1000x bigger, we should be like them” and clearly overengineering a treasury isn’t it.

", "like_count": 0, "quote_count": 0 } ] }, { "topic_id": 10098, "title": "Spark Program | CKB-UGMP —— A Universal Spore/DOB Seamless Minting Infrastructure Prototype on CKB —— 基于 CKB 的通用 Spore/DOB 无感铸造基础设施原型", "slug": "spark-program-ckb-ugmp-a-universal-spore-dob-seamless-minting-infrastructure-prototype-on-ckb-ckb-spore-dob", "url": "https://talk.nervos.org/t/spark-program-ckb-ugmp-a-universal-spore-dob-seamless-minting-infrastructure-prototype-on-ckb-ckb-spore-dob/10098", "created_at": "2026-03-17T07:21:55.306000+00:00", "last_posted_at": "2026-05-09T14:28:03.574000+00:00", "category_id": 45, "tags": [ "In-Progress", "Spark-Program" ], "posters": [ "Original Poster, Most Recent Poster", "Frequent Poster", "Frequent Poster", "Frequent Poster" ], "recent_posts": [ { "post_id": 24187, "post_number": 17, "topic_id": 10098, "topic_title": "Spark Program | CKB-UGMP —— A Universal Spore/DOB Seamless Minting Infrastructure Prototype on CKB —— 基于 CKB 的通用 Spore/DOB 无感铸造基础设施原型", "topic_slug": "spark-program-ckb-ugmp-a-universal-spore-dob-seamless-minting-infrastructure-prototype-on-ckb-ckb-spore-dob", "author": "HNO3Miracle", "created_at": "2026-05-09T10:45:44.376000+00:00", "updated_at": "2026-05-09T10:45:44.376000+00:00", "reply_to_post_number": null, "url": "https://talk.nervos.org/t/spark-program-ckb-ugmp-a-universal-spore-dob-seamless-minting-infrastructure-prototype-on-ckb-ckb-spore-dob/10098/17", "content_text": "各位好，很高兴和各位分享这周的工作。\n本周完成\n本周把第 2 周生成的 dob_metadata 草案接入了 Spore 铸造交易路径。\n显式加入 @ckb-ccc/spore 依赖\n新增 lib/sporeMint.ts，封装 metadata 到 Spore data 的转换\n使用 createSpore 构造 Spore mint 交易\n接入 signer.sendTransaction(tx)，预留钱包签名和广播路径\n当前状态\n当前 DApp 已经具备一条可演示的 MVP 主链路：\n连接钱包\n选择图片\n上传到 IPFS / Pinata\n生成 dob_metadata 草案\n构造 Spore 交易路径\n在真实签名受阻时，通过 dry-run 保存进度\n真实链上 mint 路径已经接入代码，但由于 JoyID 在当前 Windows 环境下签名窗口行为不稳定，本周没有完成真实广播。\n问题\n由于 JoyID on Windows 的问题，目前我无法对交易进行签名 (?)。\n签名的时候 JoyID 默认选择 Windows 的 Passkey，但是 JoyID 又不支持 Windows 的 Passkey。\n目前我还在找调用 Google Password Manager 的办法。\n总之 JoyID 在 Windows 和我的 Android 设备上都算不上好用，是开发中遇到的一个问题。\n下周计划\n继续找解决 JoyID 问题的方法。\n增加本地资产展示入口\n后续在手机、Mac/Linux 或其他可用环境中补一次真实 testnet mint", "content_html": "

各位好，很高兴和各位分享这周的工作。

\n

本周完成

\n

本周把第 2 周生成的 dob_metadata 草案接入了 Spore 铸造交易路径。

\n\n

当前状态

\n

当前 DApp 已经具备一条可演示的 MVP 主链路：

\n\n

真实链上 mint 路径已经接入代码，但由于 JoyID 在当前 Windows 环境下签名窗口行为不稳定，本周没有完成真实广播。

\n

问题

\n

由于 JoyID on Windows 的问题，目前我无法对交易进行签名 (?)。

\n

签名的时候 JoyID 默认选择 Windows 的 Passkey，但是 JoyID 又不支持 Windows 的 Passkey。

\n

目前我还在找调用 Google Password Manager 的办法。

\n

总之 JoyID 在 Windows 和我的 Android 设备上都算不上好用，是开发中遇到的一个问题。

\n

下周计划

\n", "like_count": 0, "quote_count": 0 }, { "post_id": 24189, "post_number": 18, "topic_id": 10098, "topic_title": "Spark Program | CKB-UGMP —— A Universal Spore/DOB Seamless Minting Infrastructure Prototype on CKB —— 基于 CKB 的通用 Spore/DOB 无感铸造基础设施原型", "topic_slug": "spark-program-ckb-ugmp-a-universal-spore-dob-seamless-minting-infrastructure-prototype-on-ckb-ckb-spore-dob", "author": "xingtianchunyan", "created_at": "2026-05-09T11:54:06.168000+00:00", "updated_at": "2026-05-09T11:54:06.168000+00:00", "reply_to_post_number": 17, "url": "https://talk.nervos.org/t/spark-program-ckb-ugmp-a-universal-spore-dob-seamless-minting-infrastructure-prototype-on-ckb-ckb-spore-dob/10098/18", "content_text": "@HNO3Miracle 你好，感谢第 3 周进展更新！\n委员会这边有两个关键问题想确认一下，以便社区更早参与、也便于后续验收：\n体验版（可部署/可访问）预计什么时候上线？\n例如：提供一个可公开访问的测试环境（demo URL），让社区和委员会能实际走通 “连接钱包 → 上传 → 生成 metadata → 铸造（或模拟铸造）” 的端到端流程。\nGitHub 仓库预计什么时候开放（或从私有转公开）？\n我们建议尽早开放仓库与基础文档（README / 环境变量示例 / 关键流程说明），这样更有利于社区和委员会成员提前参与，也能降低后续集中验收时的沟通成本。\n你可以在下次周报里直接给出一个大致时间点/里程碑节点（不需要很精确），以及你准备先开放哪些最小内容（例如先开源前端与 mock，再逐步补链上交易层）。\n祝好\n行天\n代表 Spark Program 委员会", "content_html": "

@HNO3Miracle 你好，感谢第 3 周进展更新！

\n

委员会这边有两个关键问题想确认一下，以便社区更早参与、也便于后续验收：

\n
    \n
  1. \n

    体验版（可部署/可访问）预计什么时候上线？

    \n\n
    2. \n
  2. \n

    GitHub 仓库预计什么时候开放（或从私有转公开）？

    \n\n
    3. \n
\n

你可以在下次周报里直接给出一个大致时间点/里程碑节点（不需要很精确），以及你准备先开放哪些最小内容（例如先开源前端与 mock，再逐步补链上交易层）。

\n

祝好
\n行天
\n代表 Spark Program 委员会

", "like_count": 0, "quote_count": 0 }, { "post_id": 24200, "post_number": 19, "topic_id": 10098, "topic_title": "Spark Program | CKB-UGMP —— A Universal Spore/DOB Seamless Minting Infrastructure Prototype on CKB —— 基于 CKB 的通用 Spore/DOB 无感铸造基础设施原型", "topic_slug": "spark-program-ckb-ugmp-a-universal-spore-dob-seamless-minting-infrastructure-prototype-on-ckb-ckb-spore-dob", "author": "HNO3Miracle", "created_at": "2026-05-09T14:11:40.273000+00:00", "updated_at": "2026-05-09T14:11:40.273000+00:00", "reply_to_post_number": 18, "url": "https://talk.nervos.org/t/spark-program-ckb-ugmp-a-universal-spore-dob-seamless-minting-infrastructure-prototype-on-ckb-ckb-spore-dob/10098/19", "content_text": "@xingtianchunyan 晚上好，非常感谢委员会的关心\n体验版和仓库都可以在下周上线，可能一开始会比较粗糙并且是没有经过完备测试的（由于我提到的 JoyID 的问题）。\nMVP的上传和上链铸造部分将会先开放，展示部分将会在后面开放。\n另外请不要往我之前的钱包接收地址转资产，我无法保证未来对它的访问（又是 JoyID 的问题）。\n再次感谢委员会和社区的小伙伴一直以来的关心。没有你们就不会有这个项目。\n祝好\nHNO3Miracle", "content_html": "

@xingtianchunyan 晚上好，非常感谢委员会的关心
\n体验版和仓库都可以在下周上线，可能一开始会比较粗糙并且是没有经过完备测试的（由于我提到的 JoyID 的问题）。
\nMVP的上传和上链铸造部分将会先开放，展示部分将会在后面开放。
\n另外请不要往我之前的钱包接收地址转资产，我无法保证未来对它的访问（又是 JoyID 的问题）。

\n

再次感谢委员会和社区的小伙伴一直以来的关心。没有你们就不会有这个项目。

\n

祝好
\nHNO3Miracle

", "like_count": 0, "quote_count": 0 }, { "post_id": 24201, "post_number": 20, "topic_id": 10098, "topic_title": "Spark Program | CKB-UGMP —— A Universal Spore/DOB Seamless Minting Infrastructure Prototype on CKB —— 基于 CKB 的通用 Spore/DOB 无感铸造基础设施原型", "topic_slug": "spark-program-ckb-ugmp-a-universal-spore-dob-seamless-minting-infrastructure-prototype-on-ckb-ckb-spore-dob", "author": "HNO3Miracle", "created_at": "2026-05-09T14:28:03.574000+00:00", "updated_at": "2026-05-09T14:29:32.793000+00:00", "reply_to_post_number": null, "url": "https://talk.nervos.org/t/spark-program-ckb-ugmp-a-universal-spore-dob-seamless-minting-infrastructure-prototype-on-ckb-ckb-spore-dob/10098/20", "content_text": "一个非常草率的 demo 已经可以在这里看到了，希望获得更多的批评意见。\n连接钱包和上传到IPFS已经能用了。铸造目前不一定可用。而且最终铸造 json 也有待考量，目前肯定太大了。", "content_html": "

一个非常草率的 demo 已经可以在这里看到了，希望获得更多的批评意见。

\n

连接钱包和上传到IPFS已经能用了。铸造目前不一定可用。而且最终铸造 json 也有待考量，目前肯定太大了。

", "like_count": 0, "quote_count": 0 } ] }, { "topic_id": 10239, "title": "[DIS] Bitcoin Renegade CKB Media Campaign", "slug": "dis-bitcoin-renegade-ckb-media-campaign", "url": "https://talk.nervos.org/t/dis-bitcoin-renegade-ckb-media-campaign/10239", "created_at": "2026-05-09T04:51:41.673000+00:00", "last_posted_at": "2026-05-09T13:32:11.684000+00:00", "category_id": 65, "tags": [], "posters": [ "Original Poster, Most Recent Poster", "Frequent Poster", "Frequent Poster", "Frequent Poster", "Frequent Poster" ], "recent_posts": [ { "post_id": 24183, "post_number": 1, "topic_id": 10239, "topic_title": "[DIS] Bitcoin Renegade CKB Media Campaign", "topic_slug": "dis-bitcoin-renegade-ckb-media-campaign", "author": "Bitcoin_Renegade", "created_at": "2026-05-09T04:51:41.720000+00:00", "updated_at": "2026-05-09T05:14:21.740000+00:00", "reply_to_post_number": null, "url": "https://talk.nervos.org/t/dis-bitcoin-renegade-ckb-media-campaign/10239/1", "content_text": "Grant Proposal: 6-Month Community Media Campaign\nSubmitted by: Bitcoin Renegade\nProposal Overview\nMy name is Bitcoin Renegade, a crypto content creator, blockchain marketer, and long-time community advocate focused on educating audiences, driving adoption, and building strong communities within Web3.\nThrough my Bitcoin Renegade YouTube channel, I have consistently covered blockchain ecosystems through livestreams, educational content, interviews, and community engagement. My focus is creating authentic content that turns awareness into adoption and keeps communities engaged during key moments of ecosystem growth.\nI am seeking funding for a 6-month livestream media campaign** designed to increase ecosystem visibility, educate the community, and drive adoption through consistent livestream content and social media engagement.\nCampaign Deliverables\nOver six months I will deliver:\n*Livestream Content\n3 livestreams per month\n18 livestreams total\nDistributed on YouTube and X\nCoverage includes ecosystem updates, project spotlights, educational discussions, interviews, AMAs, ecosystem commentary, and community engagement\n*Social Media Promotion\nMinimum 2 supporting posts per month on X\n12+ posts total\nPromotional content, ecosystem highlights, and community engagement posts\nWhy do you want to do this? (Why?)\nI want to do this because strong ecosystems need strong media presence. Community education, awareness, and consistent conversation are major drivers of adoption in Web3. Even the best technology needs advocates who can communicate its value, explain developments, and keep the broader community engaged.\nMy goal is to create recurring livestream content that educates audiences, highlights ecosystem developments, and helps bring new users into the ecosystem while keeping current community members informed and excited about what is being built.\nThis campaign is about turning visibility into adoption and strengthening long-term ecosystem momentum.\nWhy are you the right person to do it? (Why you?)\nI am the right person because I already actively do this work and have years of experience building communities and producing blockchain-focused content.\nMy qualifications include:\nFounder of Bitcoin Renegade\nEstablished YouTube creator and livestream host\nBlockchain marketer and crypto investment strategist\nParticipant in the Community Catalyst Program for approximately 8 months\nLed conferences and community events that helped drive adoption to Nervos\nExperience hosting interviews, AMAs, livestreams, and ecosystem discussions\nStrong relationships across Web3 communities and project founders\nAbility to communicate technical blockchain developments in a way that is understandable and engaging\nI bring both media experience and ecosystem knowledge, which positions me well to effectively represent and amplify important developments.\nWhy do you want to do it now? (Why now?)\nNow is the ideal time because the ecosystem is entering an important growth phase.\nWith developments like Fiber Network, continued progress in RGB++, expanding Bitcoin Layer 2 infrastructure, cross-chain innovation, and growing builder activity, there is increasing momentum that deserves consistent coverage and public discussion.\nThis is exactly when strong media support matters most—during moments of ecosystem acceleration.\nConsistent livestreams and community engagement can help:\nIncrease awareness of new developments\nEducate users on new tools and infrastructure\nHighlight builders and innovation\nBring in fresh attention from outside audiences\nStrengthen community confidence during key growth periods\nMomentum is building now, and this is the time to amplify it.\nWhat is the budget you are applying for? Why is it reasonable? (Budget)\nFunding Request: $500 per month for 6 months\nTotal Request: $3,000\nThis is a modest and reasonable budget considering the amount of consistent content being delivered.\nFor $500 monthly, I will provide:\n3 livestream broadcasts\n2+ supporting posts on X\nTopic research and preparation\nScheduling and outreach for guests/interviews when applicable\nSocial promotion and community engagement\nConsistent ecosystem coverage over a six-month period\nAt 18 livestreams + 12+ X posts, this provides efficient value compared to traditional marketing campaigns while offering direct community engagement and authentic ecosystem exposure.\nHow do you plan to do the work? (How?)\nThe work will be carried out through a consistent monthly content schedule over six months.\nEach month I will:\nHost 3 livestream broadcasts focused on ecosystem news, product updates, interviews, educational topics, and community discussions\nPublish at least 2 supporting posts on X to promote broadcasts, highlight important developments, and engage the wider community\nResearch ecosystem developments and prepare discussion topics for each stream\nInvite guests, builders, or community members when relevant to create valuable discussion\nEngage directly with the community through livestream chat, comments, and social media discussion\nMaintain consistent visibility around major ecosystem milestones, launches, and updates\nThis approach keeps content authentic, timely, and community-centered while creating a reliable media presence over the full six-month campaign.\nFinal Statement\nI have already invested years into building community, educating audiences, and supporting ecosystem growth. This grant would allow me to dedicate structured time and consistent energy toward amplifying one of the most exciting growth periods in the ecosystem.\nMy goal is simple: increase awareness, strengthen community, and help drive adoption through consistent media presence.\nSubmitted by: Bitcoin Renegade\nRequested Funding: $3,000\nBitcoin Renegade CKB Media Campaign Powerpoint", "content_html": "

Grant Proposal: 6-Month Community Media Campaign
\nSubmitted by: Bitcoin Renegade

\n

Proposal Overview
\nMy name is Bitcoin Renegade, a crypto content creator, blockchain marketer, and long-time community advocate focused on educating audiences, driving adoption, and building strong communities within Web3.

\n

Through my Bitcoin Renegade YouTube channel, I have consistently covered blockchain ecosystems through livestreams, educational content, interviews, and community engagement. My focus is creating authentic content that turns awareness into adoption and keeps communities engaged during key moments of ecosystem growth.

\n

I am seeking funding for a 6-month livestream media campaign** designed to increase ecosystem visibility, educate the community, and drive adoption through consistent livestream content and social media engagement.

\n

Campaign Deliverables
\nOver six months I will deliver:

\n

*Livestream Content

\n\n

*Social Media Promotion

\n\n

Why do you want to do this? (Why?)
\nI want to do this because strong ecosystems need strong media presence. Community education, awareness, and consistent conversation are major drivers of adoption in Web3. Even the best technology needs advocates who can communicate its value, explain developments, and keep the broader community engaged.

\n

My goal is to create recurring livestream content that educates audiences, highlights ecosystem developments, and helps bring new users into the ecosystem while keeping current community members informed and excited about what is being built.

\n

This campaign is about turning visibility into adoption and strengthening long-term ecosystem momentum.

\n

Why are you the right person to do it? (Why you?)
\nI am the right person because I already actively do this work and have years of experience building communities and producing blockchain-focused content.

\n

My qualifications include:

\n\n

I bring both media experience and ecosystem knowledge, which positions me well to effectively represent and amplify important developments.

\n

Why do you want to do it now? (Why now?)
\nNow is the ideal time because the ecosystem is entering an important growth phase.

\n

With developments like Fiber Network, continued progress in RGB++, expanding Bitcoin Layer 2 infrastructure, cross-chain innovation, and growing builder activity, there is increasing momentum that deserves consistent coverage and public discussion.

\n

This is exactly when strong media support matters most—during moments of ecosystem acceleration.

\n

Consistent livestreams and community engagement can help:

\n\n

Momentum is building now, and this is the time to amplify it.

\n

What is the budget you are applying for? Why is it reasonable? (Budget)
\nFunding Request: $500 per month for 6 months
\nTotal Request: $3,000

\n

This is a modest and reasonable budget considering the amount of consistent content being delivered.

\n

For $500 monthly, I will provide:

\n\n

At 18 livestreams + 12+ X posts, this provides efficient value compared to traditional marketing campaigns while offering direct community engagement and authentic ecosystem exposure.

\n

How do you plan to do the work? (How?)
\nThe work will be carried out through a consistent monthly content schedule over six months.

\n

Each month I will:

\n\n

This approach keeps content authentic, timely, and community-centered while creating a reliable media presence over the full six-month campaign.

\n

Final Statement
\nI have already invested years into building community, educating audiences, and supporting ecosystem growth. This grant would allow me to dedicate structured time and consistent energy toward amplifying one of the most exciting growth periods in the ecosystem.

\n

My goal is simple: increase awareness, strengthen community, and help drive adoption through consistent media presence.

\n

Submitted by: Bitcoin Renegade
\nRequested Funding: $3,000

\n
\n

Bitcoin Renegade CKB Media Campaign Powerpoint

", "like_count": 0, "quote_count": 0 }, { "post_id": 24184, "post_number": 2, "topic_id": 10239, "topic_title": "[DIS] Bitcoin Renegade CKB Media Campaign", "topic_slug": "dis-bitcoin-renegade-ckb-media-campaign", "author": "d3fus7.bit", "created_at": "2026-05-09T05:30:41.593000+00:00", "updated_at": "2026-05-09T05:30:41.593000+00:00", "reply_to_post_number": null, "url": "https://talk.nervos.org/t/dis-bitcoin-renegade-ckb-media-campaign/10239/2", "content_text": "I do not support. You just don’t have enough audience, sorry..", "content_html": "

I do not support. You just don’t have enough audience, sorry..

", "like_count": 0, "quote_count": 0 }, { "post_id": 24185, "post_number": 3, "topic_id": 10239, "topic_title": "[DIS] Bitcoin Renegade CKB Media Campaign", "topic_slug": "dis-bitcoin-renegade-ckb-media-campaign", "author": "wyltek", "created_at": "2026-05-09T06:25:04.301000+00:00", "updated_at": "2026-05-09T06:25:04.301000+00:00", "reply_to_post_number": null, "url": "https://talk.nervos.org/t/dis-bitcoin-renegade-ckb-media-campaign/10239/3", "content_text": "Contrary to the above I do support this. I’ll take a content creator that cares about Nervos over an overpaid talking head every time. We’ve also had overpaid talking heads represent Nervos before and it went horribly and I’m sure it cost more than 3 grand. TBH there not a single high follower crypto influencer who’s worth paying 5 figure sums to. And none of them would give you what bitcoin renegade is offering for the price. Anyone willing to don costumes at conferences under the Nervos banner is alright by me.", "content_html": "

Contrary to the above I do support this. I’ll take a content creator that cares about Nervos over an overpaid talking head every time. We’ve also had overpaid talking heads represent Nervos before and it went horribly and I’m sure it cost more than 3 grand. TBH there not a single high follower crypto influencer who’s worth paying 5 figure sums to. And none of them would give you what bitcoin renegade is offering for the price. Anyone willing to don costumes at conferences under the Nervos banner is alright by me.

", "like_count": 0, "quote_count": 0 }, { "post_id": 24188, "post_number": 4, "topic_id": 10239, "topic_title": "[DIS] Bitcoin Renegade CKB Media Campaign", "topic_slug": "dis-bitcoin-renegade-ckb-media-campaign", "author": "baclaire", "created_at": "2026-05-09T11:26:53.797000+00:00", "updated_at": "2026-05-09T11:26:53.797000+00:00", "reply_to_post_number": null, "url": "https://talk.nervos.org/t/dis-bitcoin-renegade-ckb-media-campaign/10239/4", "content_text": "Bitcoin_Renegade:\nConsistent ecosystem\nHow many viewers per live stream,how many subscribers in your Channel?", "content_html": "\n

How many viewers per live stream,how many subscribers in your Channel?

", "like_count": 0, "quote_count": 1 }, { "post_id": 24193, "post_number": 5, "topic_id": 10239, "topic_title": "[DIS] Bitcoin Renegade CKB Media Campaign", "topic_slug": "dis-bitcoin-renegade-ckb-media-campaign", "author": "ebdalezyz_aljhny", "created_at": "2026-05-09T12:38:11.834000+00:00", "updated_at": "2026-05-09T12:38:11.834000+00:00", "reply_to_post_number": null, "url": "https://talk.nervos.org/t/dis-bitcoin-renegade-ckb-media-campaign/10239/5", "content_text": "The marketing concept is excellent, but success depends on having a professional marketer.\nThe goal of marketing is to reach the target audience and achieve strong viewership and engagement metrics.\nThe X platform already provides promoted posts and audience targeting tools, which can absolutely be utilized.\nRegarding the proposal, it would be beneficial if the applicant included a report showing:\nCurrent follower count across social platforms\nAverage views and engagement metrics\nPrevious campaign performance\nIn my opinion, if the proposal gets approved, the payments should also be tied to measurable performance.\nFor example:\nThe initial $500 payment for the first month could require reaching a minimum view threshold or engagement target. If those targets are not achieved, the remaining monthly payments could be paused or reconsidered.\nThe marketing steps themselves are good and well-structured, but ultimately they should produce meaningful results.\nBest regards.", "content_html": "

The marketing concept is excellent, but success depends on having a professional marketer.

\n

The goal of marketing is to reach the target audience and achieve strong viewership and engagement metrics.

\n

The X platform already provides promoted posts and audience targeting tools, which can absolutely be utilized.

\n

Regarding the proposal, it would be beneficial if the applicant included a report showing:

\n\n

In my opinion, if the proposal gets approved, the payments should also be tied to measurable performance.

\n

For example:
\nThe initial $500 payment for the first month could require reaching a minimum view threshold or engagement target. If those targets are not achieved, the remaining monthly payments could be paused or reconsidered.

\n

The marketing steps themselves are good and well-structured, but ultimately they should produce meaningful results.

\n

Best regards.

", "like_count": 0, "quote_count": 0 }, { "post_id": 24194, "post_number": 6, "topic_id": 10239, "topic_title": "[DIS] Bitcoin Renegade CKB Media Campaign", "topic_slug": "dis-bitcoin-renegade-ckb-media-campaign", "author": "Bitcoin_Renegade", "created_at": "2026-05-09T12:38:36.472000+00:00", "updated_at": "2026-05-09T12:38:36.472000+00:00", "reply_to_post_number": null, "url": "https://talk.nervos.org/t/dis-bitcoin-renegade-ckb-media-campaign/10239/6", "content_text": "Here are my channels for context too https://x.com/bitcoinr3negade\nYouTube\nBitcoin Renegade\n1st off I Love and Fear God(Jesus) and we talk about Everything Cryptocurrency and give you the best News on how to make profits with your Crypto. How to gain more crypto and at what time. We also are all about the community and helping those less...", "content_html": "

Here are my channels for context too https://x.com/bitcoinr3negade

\n\n", "like_count": 0, "quote_count": 0 }, { "post_id": 24195, "post_number": 7, "topic_id": 10239, "topic_title": "[DIS] Bitcoin Renegade CKB Media Campaign", "topic_slug": "dis-bitcoin-renegade-ckb-media-campaign", "author": "Bitcoin_Renegade", "created_at": "2026-05-09T12:40:59.872000+00:00", "updated_at": "2026-05-09T12:54:43.481000+00:00", "reply_to_post_number": 4, "url": "https://talk.nervos.org/t/dis-bitcoin-renegade-ckb-media-campaign/10239/7", "content_text": "In a bear market my YouTube videos get from 200 to 500 views but my X account has a nice reach lately and gets about 400 to 1k views but we always have alot of likes to view ratios. New viewers from my community outside of CKB get to hear about the amazing steps forward with Nervos and build an amazing CKB community over the next 6 months to contribute on a high level", "content_html": "

In a bear market my YouTube videos get from 200 to 500 views but my X account has a nice reach lately and gets about 400 to 1k views but we always have alot of likes to view ratios. New viewers from my community outside of CKB get to hear about the amazing steps forward with Nervos and build an amazing CKB community over the next 6 months to contribute on a high level

", "like_count": 0, "quote_count": 0 }, { "post_id": 24196, "post_number": 8, "topic_id": 10239, "topic_title": "[DIS] Bitcoin Renegade CKB Media Campaign", "topic_slug": "dis-bitcoin-renegade-ckb-media-campaign", "author": "Bitcoin_Renegade", "created_at": "2026-05-09T12:53:56.989000+00:00", "updated_at": "2026-05-09T12:53:56.989000+00:00", "reply_to_post_number": 3, "url": "https://talk.nervos.org/t/dis-bitcoin-renegade-ckb-media-campaign/10239/8", "content_text": "Ty I hope to do the community proud", "content_html": "

Ty I hope to do the community proud

", "like_count": 0, "quote_count": 0 }, { "post_id": 24197, "post_number": 9, "topic_id": 10239, "topic_title": "[DIS] Bitcoin Renegade CKB Media Campaign", "topic_slug": "dis-bitcoin-renegade-ckb-media-campaign", "author": "ebdalezyz_aljhny", "created_at": "2026-05-09T12:56:58.115000+00:00", "updated_at": "2026-05-09T12:56:58.115000+00:00", "reply_to_post_number": null, "url": "https://talk.nervos.org/t/dis-bitcoin-renegade-ckb-media-campaign/10239/9", "content_text": "On the X platform, a $500 promotional budget can potentially generate anywhere between 40,000 to 120,000 views approximately.\nIt would be helpful to know what level of reach and engagement you expect to achieve within this budget range.\nTikTok also has strong algorithms that can generate very large view counts as well.\nThe real value of any marketing campaign is reaching the largest possible number of targeted users while achieving meaningful engagement and viewership metrics.\nOne more note: I personally appreciate what you are doing for CKB and your genuine passion for the project. However, when we use the term “campaign,” the expectation is naturally much larger than reaching 200 or 1,000 views, as you mentioned your account currently achieves.\nWe are discussing these points to help achieve the best possible outcome. The concept of marketing itself is excellent and absolutely necessary, but even more important is ensuring that the method used is effective and impactful.\nBest regards.", "content_html": "

On the X platform, a $500 promotional budget can potentially generate anywhere between 40,000 to 120,000 views approximately.

\n

It would be helpful to know what level of reach and engagement you expect to achieve within this budget range.

\n

TikTok also has strong algorithms that can generate very large view counts as well.

\n

The real value of any marketing campaign is reaching the largest possible number of targeted users while achieving meaningful engagement and viewership metrics.

\n

One more note: I personally appreciate what you are doing for CKB and your genuine passion for the project. However, when we use the term “campaign,” the expectation is naturally much larger than reaching 200 or 1,000 views, as you mentioned your account currently achieves.

\n

We are discussing these points to help achieve the best possible outcome. The concept of marketing itself is excellent and absolutely necessary, but even more important is ensuring that the method used is effective and impactful.

\n

Best regards.

", "like_count": 0, "quote_count": 0 }, { "post_id": 24198, "post_number": 10, "topic_id": 10239, "topic_title": "[DIS] Bitcoin Renegade CKB Media Campaign", "topic_slug": "dis-bitcoin-renegade-ckb-media-campaign", "author": "Bitcoin_Renegade", "created_at": "2026-05-09T12:59:12.621000+00:00", "updated_at": "2026-05-09T12:59:12.621000+00:00", "reply_to_post_number": 5, "url": "https://talk.nervos.org/t/dis-bitcoin-renegade-ckb-media-campaign/10239/10", "content_text": "YouTube: 4,706\nX: 3,303\nI was thinking of milestones as well but since it is a smaller amount I was just asking for the payment in one lump sum. I was in the Community Catalyst program and its more than just viewership its building a loyal amazing community and repping for Nervos in person and online. I plan to bring value, fun and technology to as many people as will listen. I hope to make you all proud!", "content_html": "

YouTube: 4,706

\n

X: 3,303

\n

I was thinking of milestones as well but since it is a smaller amount I was just asking for the payment in one lump sum. I was in the Community Catalyst program and its more than just viewership its building a loyal amazing community and repping for Nervos in person and online. I plan to bring value, fun and technology to as many people as will listen. I hope to make you all proud!

", "like_count": 0, "quote_count": 0 }, { "post_id": 24199, "post_number": 11, "topic_id": 10239, "topic_title": "[DIS] Bitcoin Renegade CKB Media Campaign", "topic_slug": "dis-bitcoin-renegade-ckb-media-campaign", "author": "Bitcoin_Renegade", "created_at": "2026-05-09T13:32:11.684000+00:00", "updated_at": "2026-05-09T13:32:11.684000+00:00", "reply_to_post_number": 3, "url": "https://talk.nervos.org/t/dis-bitcoin-renegade-ckb-media-campaign/10239/11", "content_text": "Why thank you I hope to represent Nervos community well!", "content_html": "

Why thank you I hope to represent Nervos community well!

", "like_count": 0, "quote_count": 0 } ] }, { "topic_id": 10231, "title": "Spark Program | Tiko Creator Commerce Expansion + Private Beta Validation", "slug": "spark-program-tiko-creator-commerce-expansion-private-beta-validation", "url": "https://talk.nervos.org/t/spark-program-tiko-creator-commerce-expansion-private-beta-validation/10231", "created_at": "2026-05-06T07:46:28.834000+00:00", "last_posted_at": "2026-05-09T12:09:31.620000+00:00", "category_id": 49, "tags": [ "Pending", "Spark-Program" ], "posters": [ "Original Poster", "Most Recent Poster" ], "recent_posts": [ { "post_id": 24192, "post_number": 2, "topic_id": 10231, "topic_title": "Spark Program | Tiko Creator Commerce Expansion + Private Beta Validation", "topic_slug": "spark-program-tiko-creator-commerce-expansion-private-beta-validation", "author": "xingtianchunyan", "created_at": "2026-05-09T12:09:31.620000+00:00", "updated_at": "2026-05-09T12:09:31.620000+00:00", "reply_to_post_number": null, "url": "https://talk.nervos.org/t/spark-program-tiko-creator-commerce-expansion-private-beta-validation/10231/2", "content_text": "@DWSQUIRES 你好，感谢提交 TiKo 的提案。\n委员会讨论后决定：该项目当前状态定为Pending。原因不是否定方向，而是现阶段提案存在两个关键问题，需要你补齐后才能进入正式评审：\n范围过大\n你把 creator commerce 扩展拆成了 7 类能力，但以 Spark 的资助定位来看，这个范围会显著拉高交付与验收风险。\n委员会建议你将“商业功能”抽象为更清晰的开发交付边界，并优先收敛为 7 类中的前3类（即：Digital drops、Memberships/passes、Limited editions/collectibles）作为本期 Spark 支持范围。\n提案细节不清晰（尤其是 How to Verify）\n在你缩范围后，请同步把 How to Verify 补充到可复现的验收级别，至少写清：\n评审者如何进入测试环境；\n每个里程碑/功能的验证步骤与通过/失败标准；\n证据发布位置（repo、demo、录屏、交易链接、截图、文档等）；\nprivate beta 的验证闭环（测试对象来源、任务设计、关键指标、反馈采集与最终报告形式）。\n下一步要求：请你基于上述两点 缩小范围、补充验证细节，并相应重新调整预算需求。\n更新后在本帖@我，回复“已更新”，并说明修改了哪些章节/新增了哪些链接或附件，我们会在信息齐备后继续正式评审流程。\n祝好\n行天\n代表 Spark Program 委员会", "content_html": "

@DWSQUIRES 你好，感谢提交 TiKo 的提案。

\n

委员会讨论后决定：该项目当前状态定为Pending。原因不是否定方向，而是现阶段提案存在两个关键问题，需要你补齐后才能进入正式评审：

\n
    \n
  1. \n

    范围过大
    \n你把 creator commerce 扩展拆成了 7 类能力，但以 Spark 的资助定位来看，这个范围会显著拉高交付与验收风险。
    \n委员会建议你将“商业功能”抽象为更清晰的开发交付边界，并优先收敛为 7 类中的前3类（即：Digital drops、Memberships/passes、Limited editions/collectibles）作为本期 Spark 支持范围。

    \n
    2. \n
  2. \n

    提案细节不清晰（尤其是 How to Verify）
    \n在你缩范围后，请同步把 How to Verify 补充到可复现的验收级别，至少写清：

    \n
    3. \n
\n\n

下一步要求：请你基于上述两点 缩小范围、补充验证细节，并相应重新调整预算需求。

\n

更新后在本帖@我，回复“已更新”，并说明修改了哪些章节/新增了哪些链接或附件，我们会在信息齐备后继续正式评审流程。

\n

祝好
\n行天
\n代表 Spark Program 委员会

", "like_count": 0, "quote_count": 0 } ] }, { "topic_id": 10131, "title": "Spark Program | CKB Developer Onboarding Guide", "slug": "spark-program-ckb-developer-onboarding-guide", "url": "https://talk.nervos.org/t/spark-program-ckb-developer-onboarding-guide/10131", "created_at": "2026-03-26T08:49:26.745000+00:00", "last_posted_at": "2026-05-09T12:05:47.583000+00:00", "category_id": 49, "tags": [ "In-Progress", "Spark-Program" ], "posters": [ "Original Poster", "Frequent Poster", "Most Recent Poster" ], "recent_posts": [ { "post_id": 24191, "post_number": 17, "topic_id": 10131, "topic_title": "Spark Program | CKB Developer Onboarding Guide", "topic_slug": "spark-program-ckb-developer-onboarding-guide", "author": "xingtianchunyan", "created_at": "2026-05-09T12:05:47.583000+00:00", "updated_at": "2026-05-09T12:05:47.583000+00:00", "reply_to_post_number": 16, "url": "https://talk.nervos.org/t/spark-program-ckb-developer-onboarding-guide/10131/17", "content_text": "@Mateja3m 你好，感谢你持续更新进展。\n委员会根据当前已呈现内容进行审阅后认为：目前的交付物质量不满足中期拨付的验收预期，因此本次中期资金申请暂时不予批准。\n主要原因（请你优先处理这些问题，而不是继续扩写篇幅）：\n存在较多“无意义/低信息密度”的内容：过多的内容对新用户并不会有更多实际帮助，反而增加阅读负担。\n结构不够清晰：缺少明确的“最短路径（quick start）→ 分支路径 → 常见问题回跳”的信息架构，新用户难以按步骤完成并判断是否做对。\n对新用户不够友好：关键步骤缺少明确的通过/失败标准与可复现证据；部分内容更像工作记录而非面向读者的可操作指南。\n为便于你快速改到可验收状态，建议你至少补齐/重做以下三件事（写清楚并可复核）：\n重建目录与导航：把内容收敛成“新手最短可成功路径”，并明确每一节的读者前置条件、预期结果、失败时去哪里排查。\n删减无效内容、提升信息密度：每个段落都应能回答“读者下一步怎么做、怎么判断成功”。\n补足 How to Verify：把验证写成“照着做即可”的 checklist（环境、步骤、预期输出、证据位置），并确保读者能低成本复现。\n你完成上述结构性修订后，可以在本帖回复 @ 我并说明“哪些章节已重构、删了哪些内容、验证证据放在哪里”，委员会会再进行复审。\n祝好\n行天\n代表 Spark Program 委员会", "content_html": "

@Mateja3m 你好，感谢你持续更新进展。

\n

委员会根据当前已呈现内容进行审阅后认为：目前的交付物质量不满足中期拨付的验收预期，因此本次中期资金申请暂时不予批准。

\n

主要原因（请你优先处理这些问题，而不是继续扩写篇幅）：

\n
    \n
  1. 存在较多“无意义/低信息密度”的内容：过多的内容对新用户并不会有更多实际帮助，反而增加阅读负担。
    2. \n
  2. 结构不够清晰：缺少明确的“最短路径（quick start）→ 分支路径 → 常见问题回跳”的信息架构，新用户难以按步骤完成并判断是否做对。
    3. \n
  3. 对新用户不够友好：关键步骤缺少明确的通过/失败标准与可复现证据；部分内容更像工作记录而非面向读者的可操作指南。
    4. \n
\n

为便于你快速改到可验收状态，建议你至少补齐/重做以下三件事（写清楚并可复核）：

\n\n

你完成上述结构性修订后，可以在本帖回复 @ 我并说明“哪些章节已重构、删了哪些内容、验证证据放在哪里”，委员会会再进行复审。

\n

祝好
\n行天
\n代表 Spark Program 委员会

", "like_count": 0, "quote_count": 0 } ] }, { "topic_id": 9995, "title": "Spark Program | Nervos Brain - A Global Developer Onboarding Engine and Cross-Language Hub Powered by Agentic RAG", "slug": "spark-program-nervos-brain-a-global-developer-onboarding-engine-and-cross-language-hub-powered-by-agentic-rag", "url": "https://talk.nervos.org/t/spark-program-nervos-brain-a-global-developer-onboarding-engine-and-cross-language-hub-powered-by-agentic-rag/9995", "created_at": "2026-02-25T09:58:43.726000+00:00", "last_posted_at": "2026-05-09T12:01:25.544000+00:00", "category_id": 49, "tags": [ "In-Progress", "Spark-Program" ], "posters": [ "Original Poster", "Frequent Poster", "Frequent Poster", "Most Recent Poster" ], "recent_posts": [ { "post_id": 24190, "post_number": 36, "topic_id": 9995, "topic_title": "Spark Program | Nervos Brain - A Global Developer Onboarding Engine and Cross-Language Hub Powered by Agentic RAG", "topic_slug": "spark-program-nervos-brain-a-global-developer-onboarding-engine-and-cross-language-hub-powered-by-agentic-rag", "author": "xingtianchunyan", "created_at": "2026-05-09T12:01:25.544000+00:00", "updated_at": "2026-05-09T12:01:25.544000+00:00", "reply_to_post_number": 35, "url": "https://talk.nervos.org/t/spark-program-nervos-brain-a-global-developer-onboarding-engine-and-cross-language-hub-powered-by-agentic-rag/9995/36", "content_text": "@IrisNeko 你好，感谢你提交第 8 周周报与中期拨付申请。\n委员会已完成体验与讨论，并一致认可目前 Nervos Brain 的整体质量与可用性（尤其是你把 Telegram 群内测做成了“可复现问题 → 修复 → 回归测试”的工程闭环）。\n第二期预算已拨付：\n交易哈希：0x7481daa872c9d775b741a1061a1512f87c8cc62b55c4930040da2a928e5c064f\n同时有两点建议，供你后续规划参考：\n运营资金路径建议：我们也认为这个项目具备对社区长期产生帮助的潜力；若后续进入更偏“正式运营 / 持续服务”的阶段，建议将运营性资金需求转向 **Community Fund DAO 申请，以匹配其长期支持定位。\n模型选择建议：后续迭代请慎重选择模型与组合策略，尽量在经济性（成本/延迟）与准确率/稳定性之间取得更稳的平衡，并在周报中持续公开关键指标与取舍依据，便于社区理解与复核。\n期待你继续推进后续交付，也欢迎持续把关键 bad case 与评测集沉淀出来，形成对生态可复用的参考资产。\n祝好\n行天\n代表 Spark Program 委员会", "content_html": "

@IrisNeko 你好，感谢你提交第 8 周周报与中期拨付申请。

\n

委员会已完成体验与讨论，并一致认可目前 Nervos Brain 的整体质量与可用性（尤其是你把 Telegram 群内测做成了“可复现问题 → 修复 → 回归测试”的工程闭环）。

\n

第二期预算已拨付：

\n

交易哈希：0x7481daa872c9d775b741a1061a1512f87c8cc62b55c4930040da2a928e5c064f

\n

同时有两点建议，供你后续规划参考：

\n
    \n
  1. \n

    运营资金路径建议：我们也认为这个项目具备对社区长期产生帮助的潜力；若后续进入更偏“正式运营 / 持续服务”的阶段，建议将运营性资金需求转向 **Community Fund DAO 申请，以匹配其长期支持定位。

    \n
    2. \n
  2. \n

    模型选择建议：后续迭代请慎重选择模型与组合策略，尽量在经济性（成本/延迟）与准确率/稳定性之间取得更稳的平衡，并在周报中持续公开关键指标与取舍依据，便于社区理解与复核。

    \n
    3. \n
\n

期待你继续推进后续交付，也欢迎持续把关键 bad case 与评测集沉淀出来，形成对生态可复用的参考资产。

\n

祝好
\n行天
\n代表 Spark Program 委员会

", "like_count": 0, "quote_count": 0 } ] }, { "topic_id": 10193, "title": "CellScript - A DSL for Cell-Based Contracts", "slug": "cellscript-a-dsl-for-cell-based-contracts", "url": "https://talk.nervos.org/t/cellscript-a-dsl-for-cell-based-contracts/10193", "created_at": "2026-04-21T04:43:38.654000+00:00", "last_posted_at": "2026-05-09T09:24:07.094000+00:00", "category_id": 49, "tags": [ "CKB-VM", "CellScript", "DSL" ], "posters": [ "Original Poster, Most Recent Poster", "Frequent Poster", "Frequent Poster", "Frequent Poster", "Frequent Poster" ], "recent_posts": [ { "post_id": 24186, "post_number": 23, "topic_id": 10193, "topic_title": "CellScript - A DSL for Cell-Based Contracts", "topic_slug": "cellscript-a-dsl-for-cell-based-contracts", "author": "ArthurZhang", "created_at": "2026-05-09T09:24:07.094000+00:00", "updated_at": "2026-05-09T09:45:16.177000+00:00", "reply_to_post_number": null, "url": "https://talk.nervos.org/t/cellscript-a-dsl-for-cell-based-contracts/10193/23", "content_text": "CellScript 0.14 Release Notes\nCellScript 0.14 is the CKB semantic-completeness milestone. It exposes more of\nCKB’s concrete transaction surface in source syntax, metadata, constraints, and\ntooling while keeping authorization boundaries explicit.\n0.14 adds/completes the following features:\nSpawn/IPC verifier composition\ntyped CKB Source\nWitnessArgs views\nfixed-width lock_args binding\nexplicit sighash digest surface\nTYPE_ID and outputs_data evidence\ndeclarative since/time and capacity surfaces\na formal CKB target-profile ABI contract.\nHighlights\nCKB Source, Witness, And Lock Args\n0.14 makes CKB data sources visible instead of hiding them behind ordinary\nparameters:\nsource::input, source::output, source::cell_dep, source::header_dep,\nsource::group_input, and source::group_output;\nwitness::raw, witness::lock, witness::input_type, and\nwitness::output_type;\nlock_args T for fixed-width typed decoding of the executing Script.args;\nenv::sighash_all(source) for an explicit CKB sighash digest surface.\nImportant boundary: lock_args Address, witness Address, and\nenv::sighash_all(...) do not create signer authority by themselves. Signature\nverification remains explicit future work. There is no hidden signer derivation\nfrom an Address value or parameter name.\nSpawn/IPC Verifier Composition\n0.14 adds bounded verifier reuse through CKB VM v2-shaped Spawn/IPC helpers:\nspawn\nwait\nprocess_id\npipe\npipe_write\npipe_read\ninherited_fd\nclose\nSpawn targets must be static string literals or String constants. Metadata\nrecords runtime-required CellDep or DepGroup obligations for the child verifier.\nThe type checker rejects statically visible file-descriptor use-after-close,\ndouble-close, and unclosed fd paths for pipe() and inherited_fd(...).\nTarget Profile Contract\nThe CKB target profile now reports a structured ABI contract in metadata,\nconstraints, and cellc explain-profile ckb:\nwitness ABI;\nlock args ABI;\nSource encoding;\nSpawn/IPC ABI;\nsince/time ABI;\nCellDep and script reference ABI;\noutputs / outputs_data ABI;\ncapacity floor ABI;\nTYPE_ID ABI;\nCKB tx version.\nMetadata validation rejects mismatched profile ABI fields so release evidence\ncannot silently drift from compiler policy.\noutputs / outputs_data Boundary\nCKB transactions keep Cell output metadata and Cell data in parallel arrays:\noutputs[i] = capacity, lock, type\noutputs_data[i] = data bytes for the same output Cell\n0.14 records each CellScript-created output’s index-aligned\noutputs[i] -> outputs_data[i] binding and validates that those bindings are\npresent and consistent.\nTYPE_ID And Script References\n0.14 exposes TYPE_ID output plans and script reference evidence for CKB audit\ntooling. constraints.ckb.script_references aggregates:\nTYPE_ID script references;\nSpawn/IPC CellDep or DepGroup targets;\nread_ref CellDep references.\nThis keeps code_hash, hash_type, and args visible instead of treating a\nsource-level name as authority.\nDedicated accepted/rejected CKB transaction fixture matrices for TYPE_ID\ncontinue paths, ScriptGroup shapes, and outputs_data negative cases remain\npart of the later standard compatibility-suite track. 0.14’s release boundary\nis metadata, tamper-validation, strict compilation, and production evidence for\nthe bundled examples.\nDeclarative Since/Time And Capacity Surfaces\n0.14 adds profile-visible CKB policy helpers:\nrequire_maturity\nrequire_time\nrequire_epoch_after\nrequire_epoch_relative\nwith_capacity_floor(shannons)\noccupied_capacity(\"TypeName\")\nwith_capacity_floor(...) declares a type-level output-capacity floor. It is\nnot full capacity evidence: builders still must fund outputs, measure occupied\ncapacity, measure consensus transaction size, and keep acceptance reports.\nDynamic BLAKE2b Policy\nDynamic fixed-hash Blake2b is now part of the CKB profile surface:\nlet digest = hash_blake2b(input_hash)\nhash_blake2b(input: Hash) -> Hash lowers to an executable RISC-V\nBlake2b-256 helper using CKB’s ckb-default-hash personalization. The runtime\naccess is metadata-visible as CKB_BLAKE2B, and production acceptance covers it\nthrough the real timelock.cell lock_id_commitment lock with valid and\ninvalid local CKB lock-spend transactions. Arbitrary byte-slice or resource\nserialization hashing is still out of scope until its ABI is specified.\nExamples And Tooling\n0.14 adds language examples for:\nSpawn/IPC delegate verification;\nmulti-step Spawn/IPC pipelines;\nwitness/source views;\nTYPE_ID creation;\ncapacity/time policy;\ncanonical style using protected, lock_args, witness, require,\nfield shorthand, and [].\nLSP and the VS Code extension now cover the 0.14 surface with completions,\nsnippets, and highlighting for lock_args, CKB Source views, WitnessArgs\nhelpers, ckb::*, and env::sighash_all.\nVerification\nTargeted 0.14 gate:\ncargo fmt --all\ncargo check --locked -p cellscript\ncargo test --locked -p cellscript --test v0_14 -- --test-threads=1\ncargo test --locked -p cellscript --test examples -- --test-threads=1\ncargo test --locked -p cellscript --test cli cellc_explain_profile_reports_ckb_v0_14_contract -- --test-threads=1\ncargo test --locked -p cellscript --lib lsp -- --test-threads=1\n./scripts/cellscript_0_14_scope_audit.sh\ncd editors/vscode-cellscript && npm run validate\ngit diff --check\nRoadmap example gate:\ncargo run --locked -p cellscript -- explain-profile ckb --json\ncargo run --locked -p cellscript -- constraints examples/language/v0_14_witness_source.cell --target-profile ckb\ncargo run --locked -p cellscript -- examples/language/v0_14_delegate_verify.cell --target-profile ckb\ncargo run --locked -p cellscript -- examples/language/v0_14_multi_step_pipeline.cell --target-profile ckb\ncargo run --locked -p cellscript -- examples/language/v0_14_witness_source.cell --target-profile ckb\ncargo run --locked -p cellscript -- examples/language/v0_14_ckb_type_id_create.cell --target-profile ckb\ncargo run --locked -p cellscript -- examples/language/v0_14_capacity_time.cell --target-profile ckb\ncargo run --locked -p cellscript -- examples/language/canonical_style.cell --target-profile ckb\nNext Stage\nWith 0.14, CellScript is moving out of pure language exploration and into a near dev-preview testing track. The compiler now has enough CKB-native surface area to make the next question concrete: can developers not only write contracts, but inspect, prove, build, debug, and ship them with predictable evidence?\n0.15: Scoped Invariants & Covenant ProofPlan\nThe 0.15 track is about making covenant logic explicit. Instead of hiding protocol behavior behind compiler recognizers, CellScript will model the real CKB questions directly:\nwhen does this verifier run?\nwhich cells does it cover?\nwhat transaction views does it read?\nwhat is checked on-chain?\nwhat remains a builder assumption?\nThe headline features are scoped aggregate invariants, first-class lock/type trigger semantics, explicit cell identity and TYPE_ID policies, policy-specific destruction, and a new ProofPlan layer that turns source-level intent into auditable obligations before IR and codegen. Protocol helpers like transfer, claim, settle,pools, and covenants should become inspectable stdlib proof macros rather than opaque compiler magic.\nThe goal is simple: make every serious contract property explainable before it is trusted.\n0.16: Formal Semantics, Compatibility, and Production Tooling\nThe 0.16 track takes the 0.15 proof model and hardens it into quisi-production-grade assurance. It focuses on formal operational semantics, ProofPlan soundness checks, standard CKB compatibility suites, builder assumption schemas, transaction validation, deployment governance, and audit/debug tooling.\nThis is where the dev-preview story becomes much more interesting: cellc validate-tx, transaction solving, reproducible deploy plans, proof diffs, cycle profiling, tx tracing, audit bundles, and compatibility fixtures for standard CKB patterns such as sUDT, xUDT, ACP, Cheque, Omnilock-style locks, NervosDAO-style since/epoch flows, and TYPE_ID.\nThe ambition is not just ‘compile to CKB’. The ambition is a contract workflow where source code, ProofPlan, emitted RISC-V, metadata, builder assumptions, transaction fixtures, and audit evidence all line up.", "content_html": "

CellScript 0.14 Release Notes

\n

CellScript 0.14 is the CKB semantic-completeness milestone. It exposes more of
\nCKB’s concrete transaction surface in source syntax, metadata, constraints, and
\ntooling while keeping authorization boundaries explicit.

\n

0.14 adds/completes the following features:

\n\n

Highlights

\n

CKB Source, Witness, And Lock Args

\n

0.14 makes CKB data sources visible instead of hiding them behind ordinary
\nparameters:

\n\n

Important boundary: lock_args Address, witness Address, and
\nenv::sighash_all(...) do not create signer authority by themselves. Signature
\nverification remains explicit future work. There is no hidden signer derivation
\nfrom an Address value or parameter name.

\n

Spawn/IPC Verifier Composition

\n

0.14 adds bounded verifier reuse through CKB VM v2-shaped Spawn/IPC helpers:

\n\n

Spawn targets must be static string literals or String constants. Metadata
\nrecords runtime-required CellDep or DepGroup obligations for the child verifier.
\nThe type checker rejects statically visible file-descriptor use-after-close,
\ndouble-close, and unclosed fd paths for pipe() and inherited_fd(...).

\n

Target Profile Contract

\n

The CKB target profile now reports a structured ABI contract in metadata,
\nconstraints, and cellc explain-profile ckb:

\n\n

Metadata validation rejects mismatched profile ABI fields so release evidence
\ncannot silently drift from compiler policy.

\n

outputs / outputs_data Boundary

\n

CKB transactions keep Cell output metadata and Cell data in parallel arrays:

\n
outputs[i]      = capacity, lock, type\noutputs_data[i] = data bytes for the same output Cell\n
\n

0.14 records each CellScript-created output’s index-aligned
\noutputs[i] -> outputs_data[i] binding and validates that those bindings are
\npresent and consistent.

\n

TYPE_ID And Script References

\n

0.14 exposes TYPE_ID output plans and script reference evidence for CKB audit
\ntooling. constraints.ckb.script_references aggregates:

\n\n

This keeps code_hash, hash_type, and args visible instead of treating a
\nsource-level name as authority.

\n

Dedicated accepted/rejected CKB transaction fixture matrices for TYPE_ID
\ncontinue paths, ScriptGroup shapes, and outputs_data negative cases remain
\npart of the later standard compatibility-suite track. 0.14’s release boundary
\nis metadata, tamper-validation, strict compilation, and production evidence for
\nthe bundled examples.

\n

Declarative Since/Time And Capacity Surfaces

\n

0.14 adds profile-visible CKB policy helpers:

\n\n

with_capacity_floor(...) declares a type-level output-capacity floor. It is
\nnot full capacity evidence: builders still must fund outputs, measure occupied
\ncapacity, measure consensus transaction size, and keep acceptance reports.

\n

Dynamic BLAKE2b Policy

\n

Dynamic fixed-hash Blake2b is now part of the CKB profile surface:

\n
let digest = hash_blake2b(input_hash)\n
\n

hash_blake2b(input: Hash) -> Hash lowers to an executable RISC-V
\nBlake2b-256 helper using CKB’s ckb-default-hash personalization. The runtime
\naccess is metadata-visible as CKB_BLAKE2B, and production acceptance covers it
\nthrough the real timelock.cell lock_id_commitment lock with valid and
\ninvalid local CKB lock-spend transactions. Arbitrary byte-slice or resource
\nserialization hashing is still out of scope until its ABI is specified.

\n

Examples And Tooling

\n

0.14 adds language examples for:

\n\n

LSP and the VS Code extension now cover the 0.14 surface with completions,
\nsnippets, and highlighting for lock_args, CKB Source views, WitnessArgs
\nhelpers, ckb::*, and env::sighash_all.

\n

Verification

\n

Targeted 0.14 gate:

\n
cargo fmt --all\ncargo check --locked -p cellscript\ncargo test --locked -p cellscript --test v0_14 -- --test-threads=1\ncargo test --locked -p cellscript --test examples -- --test-threads=1\ncargo test --locked -p cellscript --test cli cellc_explain_profile_reports_ckb_v0_14_contract -- --test-threads=1\ncargo test --locked -p cellscript --lib lsp -- --test-threads=1\n./scripts/cellscript_0_14_scope_audit.sh\ncd editors/vscode-cellscript && npm run validate\ngit diff --check\n
\n

Roadmap example gate:

\n
cargo run --locked -p cellscript -- explain-profile ckb --json\ncargo run --locked -p cellscript -- constraints examples/language/v0_14_witness_source.cell --target-profile ckb\ncargo run --locked -p cellscript -- examples/language/v0_14_delegate_verify.cell --target-profile ckb\ncargo run --locked -p cellscript -- examples/language/v0_14_multi_step_pipeline.cell --target-profile ckb\ncargo run --locked -p cellscript -- examples/language/v0_14_witness_source.cell --target-profile ckb\ncargo run --locked -p cellscript -- examples/language/v0_14_ckb_type_id_create.cell --target-profile ckb\ncargo run --locked -p cellscript -- examples/language/v0_14_capacity_time.cell --target-profile ckb\ncargo run --locked -p cellscript -- examples/language/canonical_style.cell --target-profile ckb\n
\n

Next Stage

\n

With 0.14, CellScript is moving out of pure language exploration and into a near dev-preview testing track. The compiler now has enough CKB-native surface area to make the next question concrete: can developers not only write contracts, but inspect, prove, build, debug, and ship them with predictable evidence?

\n

0.15: Scoped Invariants & Covenant ProofPlan

\n

The 0.15 track is about making covenant logic explicit. Instead of hiding protocol behavior behind compiler recognizers, CellScript will model the real CKB questions directly:

\n
\n
    \n
  1. when does this verifier run?
    2. \n
  2. which cells does it cover?
    3. \n
  3. what transaction views does it read?
    4. \n
  4. what is checked on-chain?
    5. \n
  5. what remains a builder assumption?
    6. \n
\n
\n

The headline features are scoped aggregate invariants, first-class lock/type trigger semantics, explicit cell identity and TYPE_ID policies, policy-specific destruction, and a new ProofPlan layer that turns source-level intent into auditable obligations before IR and codegen. Protocol helpers like transfer, claim, settle,pools, and covenants should become inspectable stdlib proof macros rather than opaque compiler magic.

\n

The goal is simple: make every serious contract property explainable before it is trusted.

\n

0.16: Formal Semantics, Compatibility, and Production Tooling

\n

The 0.16 track takes the 0.15 proof model and hardens it into quisi-production-grade assurance. It focuses on formal operational semantics, ProofPlan soundness checks, standard CKB compatibility suites, builder assumption schemas, transaction validation, deployment governance, and audit/debug tooling.

\n

This is where the dev-preview story becomes much more interesting: cellc validate-tx, transaction solving, reproducible deploy plans, proof diffs, cycle profiling, tx tracing, audit bundles, and compatibility fixtures for standard CKB patterns such as sUDT, xUDT, ACP, Cheque, Omnilock-style locks, NervosDAO-style since/epoch flows, and TYPE_ID.

\n

The ambition is not just ‘compile to CKB’. The ambition is a contract workflow where source code, ProofPlan, emitted RISC-V, metadata, builder assumptions, transaction fixtures, and audit evidence all line up.

", "like_count": 0, "quote_count": 0 } ] }, { "topic_id": 10229, "title": "A Paid AI Agent Calling Experiment via Fiber", "slug": "a-paid-ai-agent-calling-experiment-via-fiber", "url": "https://talk.nervos.org/t/a-paid-ai-agent-calling-experiment-via-fiber/10229", "created_at": "2026-05-06T04:13:14.026000+00:00", "last_posted_at": "2026-05-09T04:25:11.346000+00:00", "category_id": 64, "tags": [], "posters": [ "Original Poster", "Frequent Poster", "Frequent Poster", "Frequent Poster", "Most Recent Poster" ], "recent_posts": [ { "post_id": 24172, "post_number": 8, "topic_id": 10229, "topic_title": "A Paid AI Agent Calling Experiment via Fiber", "topic_slug": "a-paid-ai-agent-calling-experiment-via-fiber", "author": "keith", "created_at": "2026-05-08T19:05:54.242000+00:00", "updated_at": "2026-05-08T19:05:54.242000+00:00", "reply_to_post_number": null, "url": "https://talk.nervos.org/t/a-paid-ai-agent-calling-experiment-via-fiber/10229/8", "content_text": "我的 hackathon 项目业务和这个一样, 1-tok 是 agent runtime market, carrier 是 agent orchestrator. 会将任务派发给独立容器里的 sub agents.\nClient 在 1-Tok 充值额度, 并发布任务, Provider 在 1-Tok 选择合适的可执行任务并给出报价, 被选中后按照 Milestone 和阶段性 Token 消耗计费.\n对于 Client 来说, 可以按次获取 Agent 资源, 不只是 SOTA 模型, 还有更好的 Agentic Setup 和硬件\n对于 Provider 来说, 闲置的 Token 和资源可以回血\nimage1920×1687 193 KB", "content_html": "

我的 hackathon 项目业务和这个一样, 1-tok 是 agent runtime market, carrier 是 agent orchestrator. 会将任务派发给独立容器里的 sub agents.

\n

Client 在 1-Tok 充值额度, 并发布任务, Provider 在 1-Tok 选择合适的可执行任务并给出报价, 被选中后按照 Milestone 和阶段性 Token 消耗计费.

\n

对于 Client 来说, 可以按次获取 Agent 资源, 不只是 SOTA 模型, 还有更好的 Agentic Setup 和硬件
\n对于 Provider 来说, 闲置的 Token 和资源可以回血

\n

\"image\"
image1920×1687 193 KB

", "like_count": 0, "quote_count": 0 }, { "post_id": 24176, "post_number": 9, "topic_id": 10229, "topic_title": "A Paid AI Agent Calling Experiment via Fiber", "topic_slug": "a-paid-ai-agent-calling-experiment-via-fiber", "author": "fishell", "created_at": "2026-05-09T02:38:40.818000+00:00", "updated_at": "2026-05-09T02:38:40.818000+00:00", "reply_to_post_number": 7, "url": "https://talk.nervos.org/t/a-paid-ai-agent-calling-experiment-via-fiber/10229/9", "content_text": "很有意思，我感觉这个东西的最强场景可能是一个魔改模型平台，例如 HauhauCS， 这样的模型不会有官方服务，一般用户不会跑或者没显卡，用fiber payment比用法币更合适。\nmanus+fiber+魔改本地模型大本营", "content_html": "

很有意思，我感觉这个东西的最强场景可能是一个魔改模型平台，例如 HauhauCS， 这样的模型不会有官方服务，一般用户不会跑或者没显卡，用fiber payment比用法币更合适。

\n

manus+fiber+魔改本地模型大本营 \":grin:\"

", "like_count": 0, "quote_count": 0 }, { "post_id": 24181, "post_number": 10, "topic_id": 10229, "topic_title": "A Paid AI Agent Calling Experiment via Fiber", "topic_slug": "a-paid-ai-agent-calling-experiment-via-fiber", "author": "RetricSu", "created_at": "2026-05-09T04:02:55.881000+00:00", "updated_at": "2026-05-09T04:02:55.881000+00:00", "reply_to_post_number": 9, "url": "https://talk.nervos.org/t/a-paid-ai-agent-calling-experiment-via-fiber/10229/10", "content_text": "没有审查的 AI…这个我之前倒是没想到，确实不会有官方服务，只能靠众包", "content_html": "

没有审查的 AI…这个我之前倒是没想到，确实不会有官方服务，只能靠众包

", "like_count": 0, "quote_count": 0 }, { "post_id": 24182, "post_number": 11, "topic_id": 10229, "topic_title": "A Paid AI Agent Calling Experiment via Fiber", "topic_slug": "a-paid-ai-agent-calling-experiment-via-fiber", "author": "ArthurZhang", "created_at": "2026-05-09T04:25:11.346000+00:00", "updated_at": "2026-05-09T04:25:11.346000+00:00", "reply_to_post_number": null, "url": "https://talk.nervos.org/t/a-paid-ai-agent-calling-experiment-via-fiber/10229/11", "content_text": "我的直觉也是，对无审查模型不审查的话可能滑入一个脏活外包小天堂。", "content_html": "

我的直觉也是，对无审查模型不审查的话可能滑入一个脏活外包小天堂。

", "like_count": 0, "quote_count": 0 } ] }, { "topic_id": 10238, "title": "[RFC] CellScript 的包管理：一个 Go 语言风格的、基于 GitHub 的 CKB 合约包管理注册表", "slug": "rfc-cellscript-go-github-ckb", "url": "https://talk.nervos.org/t/rfc-cellscript-go-github-ckb/10238", "created_at": "2026-05-08T03:31:06.806000+00:00", "last_posted_at": "2026-05-09T03:46:52.370000+00:00", "category_id": 45, "tags": [ "CKB", "CKB-VM", "CellScript" ], "posters": [ "Original Poster, Most Recent Poster", "Frequent Poster" ], "recent_posts": [ { "post_id": 24179, "post_number": 2, "topic_id": 10238, "topic_title": "[RFC] CellScript 的包管理：一个 Go 语言风格的、基于 GitHub 的 CKB 合约包管理注册表", "topic_slug": "rfc-cellscript-go-github-ckb", "author": "janx", "created_at": "2026-05-09T03:13:30.547000+00:00", "updated_at": "2026-05-09T03:13:30.547000+00:00", "reply_to_post_number": null, "url": "https://talk.nervos.org/t/rfc-cellscript-go-github-ckb/10238/2", "content_text": "toml 中有 package.namespace 是否意味着, 其实也可以管理其他的 cellscript 之外的软件包?\n比如 @xxuejie 和我有一个未完成的工作 ckb-bootstrapper, 试图实现只依赖 ckb 自身就能 reproducible build 出正确的 ckb binary. 很好奇你的看法？是否可以把 ckb 本身作为一个需要 e2e reproducible 的包在这个框架下管理？\nArthurZhang:\n为什么用链下部署记录，而不用链上？ CKB 的容量成本使得大多数全量的链上源码包存储不具吸引力。在链上存储版本元数据、模式清单和 ABI 索引会成倍增加成本，却没有共识层面的收益。这些是开发者产物，不是运行时状态。链上应该记录紧凑的部署事实（CellDep、OutPoint、data_hash），而不是取代整个源码分发系统。\n很合理。不过成本也要相对收益来衡量，不同代码的价值也不同。我觉得最终会有一些代码元数据是需要保存在链上的——链上做索引，链下做存储。", "content_html": "

toml 中有 package.namespace 是否意味着, 其实也可以管理其他的 cellscript 之外的软件包?

\n

比如 @xxuejie 和我有一个未完成的工作 ckb-bootstrapper, 试图实现只依赖 ckb 自身就能 reproducible build 出正确的 ckb binary. 很好奇你的看法？是否可以把 ckb 本身作为一个需要 e2e reproducible 的包在这个框架下管理？

\n\n

很合理。不过成本也要相对收益来衡量，不同代码的价值也不同。我觉得最终会有一些代码元数据是需要保存在链上的——链上做索引，链下做存储。

", "like_count": 0, "quote_count": 1 }, { "post_id": 24180, "post_number": 3, "topic_id": 10238, "topic_title": "[RFC] CellScript 的包管理：一个 Go 语言风格的、基于 GitHub 的 CKB 合约包管理注册表", "topic_slug": "rfc-cellscript-go-github-ckb", "author": "ArthurZhang", "created_at": "2026-05-09T03:46:52.370000+00:00", "updated_at": "2026-05-09T08:53:23.082000+00:00", "reply_to_post_number": 2, "url": "https://talk.nervos.org/t/rfc-cellscript-go-github-ckb/10238/3", "content_text": "Hi Jan，\n这个问题很有意思。\n我的理解是：目前的架构上确实已经留下了这个空间，但第一阶段我会先把 scope 收在 CellScript packages 上。\npackage.namespace 确实不必永远只服务 CellScript 包。更抽象地说，它是在给一个 package / artifact 一个稳定命名空间，然后用 source_hash → build/artifact_hash → deployment/artifact identity 把名字和真实的编译产物绑定起来。\n对 CellScript 合约来说，这第三层是 CKB deployed Cell：OutPoint / code_hash / data_hash / CellDep。\n对 CKB 本身或 ckb-bootstrapper 来说，它也可以被建模成同一套 identity framework 下的 package-like verifiable artifact。它的 identity chain 可能是：\nsource identity\n→ reproducible build recipe identity\n→ release binary / bootstrap artifact identity\n当然，这可能需要一个不同的 artifact profile，而不是直接混进第一阶段的 CellScript registry scope.\n我也同意你对链上 metadata 的判断：成本要视乎收益，而且不同代码的价值不同。\n比较干净的边界如你说可能是：\non-chain: compact commitment + discovery/index facts\noff-chain: full source, manifests, build logs, schemas, proofs, and larger metadata\n这样 CKB 不需要变成 package database，但高价值 artifact 仍然可以获得 CKB-native 的 verifiable identity。\n按照个想法发展，我原来的 Phase 2 主要是 CellScript 合约部署索引，你说的、更通用的 artifact commitment/index layer方向中，Phase2可以是其中一个子集。\n也欢迎其他更详细的边界设计建议。", "content_html": "

Hi Jan，

\n

这个问题很有意思。

\n

我的理解是：目前的架构上确实已经留下了这个空间，但第一阶段我会先把 scope 收在 CellScript packages 上。

\n

package.namespace 确实不必永远只服务 CellScript 包。更抽象地说，它是在给一个 package / artifact 一个稳定命名空间，然后用 source_hash → build/artifact_hash → deployment/artifact identity 把名字和真实的编译产物绑定起来。

\n

对 CellScript 合约来说，这第三层是 CKB deployed Cell：OutPoint / code_hash / data_hash / CellDep。

\n

对 CKB 本身或 ckb-bootstrapper 来说，它也可以被建模成同一套 identity framework 下的 package-like verifiable artifact。它的 identity chain 可能是：

\n

source identity
\n → reproducible build recipe identity
\n → release binary / bootstrap artifact identity

\n

当然，这可能需要一个不同的 artifact profile，而不是直接混进第一阶段的 CellScript registry scope.

\n

我也同意你对链上 metadata 的判断：成本要视乎收益，而且不同代码的价值不同。

\n

比较干净的边界如你说可能是：

\n\n

这样 CKB 不需要变成 package database，但高价值 artifact 仍然可以获得 CKB-native 的 verifiable identity。

\n

按照个想法发展，我原来的 Phase 2 主要是 CellScript 合约部署索引，你说的、更通用的 artifact commitment/index layer方向中，Phase2可以是其中一个子集。

\n

也欢迎其他更详细的边界设计建议。

", "like_count": 0, "quote_count": 0 } ] }, { "topic_id": 10232, "title": "当 84% 的开发者都在用 AI Coding，CKB 开发者体验的下一步怎么走？（附完整调研与路线图）", "slug": "84-ai-coding-ckb", "url": "https://talk.nervos.org/t/84-ai-coding-ckb/10232", "created_at": "2026-05-06T13:07:08.610000+00:00", "last_posted_at": "2026-05-09T02:06:27.323000+00:00", "category_id": 32, "tags": [], "posters": [ "Original Poster", "Most Recent Poster" ], "recent_posts": [ { "post_id": 24175, "post_number": 2, "topic_id": 10232, "topic_title": "当 84% 的开发者都在用 AI Coding，CKB 开发者体验的下一步怎么走？（附完整调研与路线图）", "topic_slug": "84-ai-coding-ckb", "author": "jm9k", "created_at": "2026-05-09T02:06:27.323000+00:00", "updated_at": "2026-05-09T02:06:27.323000+00:00", "reply_to_post_number": null, "url": "https://talk.nervos.org/t/84-ai-coding-ckb/10232/2", "content_text": "Hi @yixiu.ckbfans.bit, thanks for taking the initiative to put this together. AI adoption is only going to increase over time, so it is important that our offerings continue to improve.\nContext7\nMy personal experience is that Context7 is a good idea with mediocre results at best. This is seen not just in CKB development but in any development. Documentation quality on the platform varies wildly since there is no curation control, and stale or low-quality content gets surfaced as easily as anything good. Our docs should be improved regardless, and better docs would lead to better Context7 results. However, Context7 itself is a tool I would recommend against using because of its unpredictable results.\nllms.txt\nllms.txt is an emerging standard, but most tools bypass it entirely unless specifically directed to access it. Its impact and benefit are not as great as we would hope. Google has rejected the proposal. We should still adopt it, along with any similar standards mentioned in the report, since they are easy enough to support. However, in the grand scheme of what will make AI successful for CKB development, this is ultimately a minor issue.\nAsk AI for documentation\nThis has been raised several times with no good excuse for it not existing. This is absolutely needed.\nAI config templates\nYes, we should make every effort to make CKB development more AI consumable. However, this alone must go hand-in-hand with documentation and tooling improvements as a whole.\nInsufficient reference examples\nThis is the single largest deficiency in the ecosystem. One example: there is no production-grade DEX implementation anywhere. Everyone who wants to build one starts from scratch. The same pattern repeats for other core primitives. The barrier to entry is significantly higher than it should be, and that is highly discouraging to incoming developers.\nCKB AI (Sonami)\nThis is my initial effort, which has shown promising improvements, but a larger ecosystem-wide collaborative effort would be very welcome and is exactly what is needed to make CKB truly AI native.\nI saw no reference to ckb-ai.ckbdev.com in the report, which is the intended entry point. This is unsurprising because CKB AI has been primarily geared toward the CKBuilders and has never been pushed publicly.\nCKB AI is still pre-1.0, so the develop branch is unstable, but simultaneously the only recommended version. Windsurf is not officially supported, but I have tested it and have never seen any compatibility issues using the newest version.\nOn the proposed TypeScript rewrite\nRust has been the most admired language on Stack Overflow’s developer survey for 10 years running, and it continues to grow. Rust consistently leads to better applications. Switching the MCP server to TypeScript trades long-term quality for a short-term contributor-barrier gain. The benefit of the language used for the MCP server itself is negligible. The factors noted above are substantially more important to the total success of the effort.", "content_html": "

Hi @yixiu.ckbfans.bit, thanks for taking the initiative to put this together. AI adoption is only going to increase over time, so it is important that our offerings continue to improve.

\n
\n

Context7

\n
\n

My personal experience is that Context7 is a good idea with mediocre results at best. This is seen not just in CKB development but in any development. Documentation quality on the platform varies wildly since there is no curation control, and stale or low-quality content gets surfaced as easily as anything good. Our docs should be improved regardless, and better docs would lead to better Context7 results. However, Context7 itself is a tool I would recommend against using because of its unpredictable results.

\n
\n

llms.txt

\n
\n

llms.txt is an emerging standard, but most tools bypass it entirely unless specifically directed to access it. Its impact and benefit are not as great as we would hope. Google has rejected the proposal. We should still adopt it, along with any similar standards mentioned in the report, since they are easy enough to support. However, in the grand scheme of what will make AI successful for CKB development, this is ultimately a minor issue.

\n
\n

Ask AI for documentation

\n
\n

This has been raised several times with no good excuse for it not existing. This is absolutely needed.

\n
\n

AI config templates

\n
\n

Yes, we should make every effort to make CKB development more AI consumable. However, this alone must go hand-in-hand with documentation and tooling improvements as a whole.

\n
\n

Insufficient reference examples

\n
\n

This is the single largest deficiency in the ecosystem. One example: there is no production-grade DEX implementation anywhere. Everyone who wants to build one starts from scratch. The same pattern repeats for other core primitives. The barrier to entry is significantly higher than it should be, and that is highly discouraging to incoming developers.

\n
\n

CKB AI (Sonami)

\n
\n

This is my initial effort, which has shown promising improvements, but a larger ecosystem-wide collaborative effort would be very welcome and is exactly what is needed to make CKB truly AI native.

\n

I saw no reference to ckb-ai.ckbdev.com in the report, which is the intended entry point. This is unsurprising because CKB AI has been primarily geared toward the CKBuilders and has never been pushed publicly.

\n

CKB AI is still pre-1.0, so the develop branch is unstable, but simultaneously the only recommended version. Windsurf is not officially supported, but I have tested it and have never seen any compatibility issues using the newest version.

\n
\n

On the proposed TypeScript rewrite

\n
\n

Rust has been the most admired language on Stack Overflow’s developer survey for 10 years running, and it continues to grow. Rust consistently leads to better applications. Switching the MCP server to TypeScript trades long-term quality for a short-term contributor-barrier gain. The benefit of the language used for the MCP server itself is negligible. The factors noted above are substantially more important to the total success of the effort.

", "like_count": 0, "quote_count": 0 } ] }, { "topic_id": 9845, "title": "[DIS] Fiber Link: A CKB Fiber-based Pay Layer (Tipping & Micropayments) for Communities", "slug": "dis-fiber-link-a-ckb-fiber-based-pay-layer-tipping-micropayments-for-communities", "url": "https://talk.nervos.org/t/dis-fiber-link-a-ckb-fiber-based-pay-layer-tipping-micropayments-for-communities/9845", "created_at": "2026-01-18T12:17:10.427000+00:00", "last_posted_at": "2026-05-08T20:00:34.408000+00:00", "category_id": 65, "tags": [], "posters": [ "Original Poster, Most Recent Poster", "Frequent Poster", "Frequent Poster", "Frequent Poster", "Frequent Poster" ], "recent_posts": [ { "post_id": 24173, "post_number": 35, "topic_id": 9845, "topic_title": "[DIS] Fiber Link: A CKB Fiber-based Pay Layer (Tipping & Micropayments) for Communities", "topic_slug": "dis-fiber-link-a-ckb-fiber-based-pay-layer-tipping-micropayments-for-communities", "author": "keith", "created_at": "2026-05-08T20:00:34.408000+00:00", "updated_at": "2026-05-09T03:24:30.992000+00:00", "reply_to_post_number": null, "url": "https://talk.nervos.org/t/dis-fiber-link-a-ckb-fiber-based-pay-layer-tipping-micropayments-for-communities/9845/35", "content_text": "Fiber Link Product Delivery Report\n1. Project Overview\nFiber 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.\nThe 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.\nMain entry point:\nProduct overview: fiber-link/README.md at main · Keith-CY/fiber-link · GitHub\n2. Delivery Scope\nThis delivery covers the following core areas:\nDiscourse Tip experience, including video demo\nBackend service deployment documentation\nDiscourse plugin installation and configuration documentation\nArchitecture and Security Documentation\nMilestone 3 acceptance and delivery evidence index\n3. User-Facing Product Capabilities\nFiber Link currently supports the following core product loop:\nYouTube: https://youtu.be/xdPp42APukw\n4. Deployment and Service Documentation\n4.1 Backend Stack Deployment\nFiber Link Stack Deployment: fiber-link/docs/runbooks/fiber-link-stack-deployment.md at main · Keith-CY/fiber-link · GitHub\nThis document covers:\nPostgres\nRedis\nFiber node / FNN\nFiber Link RPC service\nFiber Link worker\nhealth checks\nsmoke verification\nbasic deployment flow\n4.2 Compose Service Reference\nCompose Reference: fiber-link/docs/runbooks/compose-reference.md at main · Keith-CY/fiber-link · GitHub\nThis document helps operators understand the Docker Compose service structure, service names, ports, runtime behavior, and local smoke test flow.\n4.3 Mainnet / Production-Like Deployment Checklist\nMainnet Deployment Checklist: fiber-link/docs/runbooks/mainnet-deployment-checklist.md at main · Keith-CY/fiber-link · GitHub\nThis document supports pre- and post-launch checks, including:\npreflight checks\nrollback\npost-deploy verification\nproduction readiness\n4.4 Monitoring and Operations\nCompose Ops Monitoring: fiber-link/docs/runbooks/compose-ops-monitoring.md at main · Keith-CY/fiber-link · GitHub\nThis document is used to verify runtime status and monitoring after deployment.\n5. Discourse Plugin Installation and Configuration Documentation\nDiscourse administrators can use the following documentation to install, enable, configure, and verify the Fiber Link plugin.\n5.1 Discourse Plugin Admin\nfiber-link/docs/runbooks/discourse-plugin-admin.md at main · Keith-CY/fiber-link · GitHub\nThis document covers:\nFiber Link plugin installation\nDiscourse admin settings\nbackend service URL configuration\napp ID / app secret configuration\nTip action verification\ncreator dashboard verification\nplugin-to-backend connectivity checks\n5.2 Admin Installation\nfiber-link/docs/admin-installation.md at main · Keith-CY/fiber-link · GitHub\nThis document provides a shorter installation and verification guide for administrators who need a quick execution path.\n6. Architecture and Security Documentation\nFiber 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.\nCore documents:\nCurrent Architecture\nfiber-link/docs/current-architecture.md at main · Keith-CY/fiber-link · GitHub\nSecurity Assumptions\nfiber-link/docs/runbooks/security-assumptions.md at main · Keith-CY/fiber-link · GitHub\nThreat Model\nfiber-link/docs/05-threat-model.md at main · Keith-CY/fiber-link · GitHub\nSecurity Controls Evidence Map\nfiber-link/docs/runbooks/security-controls-evidence-map.md at main · Keith-CY/fiber-link · GitHub\nThese documents explain:\nrelationships between system components\nhosted custody / hosted hub assumptions\nassets that operators must protect\nrisk boundaries\nsecurity controls and evidence mapping\n7. Milestone 3 Acceptance and Evidence\n7.1 Acceptance Tracker\nfiber-link/docs/acceptance/README.md at main · Keith-CY/fiber-link · GitHub\nUsed to review the milestone and checkpoint overview.\n7.2 Milestone 3 Acceptance Index\nfiber-link/docs/acceptance/milestone-3/index.md at main · Keith-CY/fiber-link · GitHub\nUsed to review Milestone 3 acceptance items, including:\ncreator withdrawal workflow\nadmin controls\nproduction hardening\nmainnet deployment checklist\nfinal acceptance criteria\n7.3 Milestone 3 Evidence Index\nfiber-link/docs/runbooks/acceptance-evidence/milestone-3/index.md at main · Keith-CY/fiber-link · GitHub\nUsed to review the delivery evidence index for Milestone 3.\n8. Recommended Reading Path for Reviewers\nIf reviewers have limited time, the following six links are recommended:\nProduct overview\nfiber-link/README.md at main · Keith-CY/fiber-link · GitHub\nGetting started\nfiber-link/docs/getting-started.md at main · Keith-CY/fiber-link · GitHub\nCurrent status\nfiber-link/docs/current-status.md at main · Keith-CY/fiber-link · GitHub\nBackend deployment\nfiber-link/docs/runbooks/fiber-link-stack-deployment.md at main · Keith-CY/fiber-link · GitHub\nDiscourse plugin installation / admin guide\nfiber-link/docs/runbooks/discourse-plugin-admin.md at main · Keith-CY/fiber-link · GitHub\nMilestone 3 acceptance\nfiber-link/docs/acceptance/milestone-3/index.md at main · Keith-CY/fiber-link · GitHub\n9. Delivery Artifacts\nSeafile\nM3 Delivery\nShare link for M3 Delivery.\nFiber Link 产品交付报告\n1. 项目概览\nFiber Link 是一个面向社区场景的支付与打赏基础设施，当前优先支持 Discourse 社区。它允许社区用户直接在帖子或回复中发起 Tip，并提供从支付请求生成、支付、结算，到创作者收入展示与提现的完整流程。\n本次交付的重点，是将 Fiber Link 从“工程上可运行的实现”，整理为“产品级、可评审、可验证、可部署”的状态。除了提供 Live Demo 和 Milestone 3 验收证据 外，也补充完善了面向 reviewer、部署者、Discourse 管理员以及服务运营者的主线产品文档。\n主入口：\n产品概览: fiber-link/README.md at main · Keith-CY/fiber-link · GitHub\n2. 本次交付范围\n本次交付主要覆盖以下核心内容：\nDiscourse Tip 使用体验与视频演示\nBackend service 部署文档\nDiscourse 插件安装与配置文档\n架构与安全文档\nMilestone 3 验收与交付证据索引\n3. 用户可见产品能力\nFiber Link 当前支持的核心产品闭环：\nYouTube: https://youtu.be/xdPp42APukw\n4. 部署与服务文档\n4.1 Backend Stack 部署\nFiber Link Stack Deployment: fiber-link/docs/runbooks/fiber-link-stack-deployment.md at main · Keith-CY/fiber-link · GitHub\n该文档覆盖：\nPostgres\nRedis\nFiber node / FNN\nFiber Link RPC service\nFiber Link worker\nhealth check\nsmoke verification\n基础部署流程\n4.2 Compose 服务参考\nCompose Reference: fiber-link/docs/runbooks/compose-reference.md at main · Keith-CY/fiber-link · GitHub\n该文档用于帮助运营者理解 Docker Compose 的服务结构、服务名称、端口、运行方式以及本地 smoke 测试流程。\n4.3 主网 / 类生产环境部署检查\nMainnet Deployment Checklist: fiber-link/docs/runbooks/mainnet-deployment-checklist.md at main · Keith-CY/fiber-link · GitHub\n该文档用于上线前后的检查，包括：\npreflight checks\nrollback\npost-deploy verification\nproduction readiness\n4.4 监控与运维\nCompose Ops Monitoring: fiber-link/docs/runbooks/compose-ops-monitoring.md at main · Keith-CY/fiber-link · GitHub\n该文档用于部署后的运行状态检查与监控确认。\n5. Discourse 插件安装与配置文档\nDiscourse 管理员可以通过以下文档完成 Fiber Link 插件的安装、启用、配置与验证。\n5.1 Discourse Plugin Admin\nfiber-link/docs/runbooks/discourse-plugin-admin.md at main · Keith-CY/fiber-link · GitHub\n该文档覆盖：\nFiber Link 插件安装\nDiscourse 管理员设置\nbackend service URL 配置\napp ID / app secret 配置\nTip 功能验证\ncreator dashboard 验证\nplugin 与 backend 的连接检查\n5.2 Admin Installation\nfiber-link/docs/admin-installation.md at main · Keith-CY/fiber-link · GitHub\n该文档提供更简洁的安装与验证说明，适合管理员快速执行。\n6. 架构与安全文档\nFiber Link 当前采用基于 hosted hub 与内部 ledger 的 MVP 模型，因此其安全边界与运营假设需要被明确记录。\n核心文档包括：\nCurrent Architecture\nfiber-link/docs/current-architecture.md at main · Keith-CY/fiber-link · GitHub\nSecurity Assumptions\nfiber-link/docs/runbooks/security-assumptions.md at main · Keith-CY/fiber-link · GitHub\nThreat Model\nfiber-link/docs/05-threat-model.md at main · Keith-CY/fiber-link · GitHub\nSecurity Controls Evidence Map\nfiber-link/docs/runbooks/security-controls-evidence-map.md at main · Keith-CY/fiber-link · GitHub\n这些文档说明了：\n系统组件之间的关系\nhosted custody / hosted hub 的假设\n运营者需要保护的资产\n风险边界\n安全控制与证据映射\n7. Milestone 3 验收与证据\n7.1 Acceptance Tracker\nfiber-link/docs/acceptance/README.md at main · Keith-CY/fiber-link · GitHub\n用于查看 milestone 与 checkpoint 总览。\n7.2 Milestone 3 Acceptance Index\nfiber-link/docs/acceptance/milestone-3/index.md at main · Keith-CY/fiber-link · GitHub\n用于查看 Milestone 3 的验收项，包括：\ncreator withdrawal workflow\nadmin controls\nproduction hardening\nmainnet deployment checklist\nfinal acceptance criteria\n7.3 Milestone 3 Evidence Index\nfiber-link/docs/runbooks/acceptance-evidence/milestone-3/index.md at main · Keith-CY/fiber-link · GitHub\n用于查看 Milestone 3 的交付证据索引。\n8. Reviewer 推荐阅读路径\n如果 reviewer 时间有限，建议优先阅读以下 6 个链接：\nProduct overview\nfiber-link/README.md at main · Keith-CY/fiber-link · GitHub\nGetting started\nfiber-link/docs/getting-started.md at main · Keith-CY/fiber-link · GitHub\nCurrent status\nfiber-link/docs/current-status.md at main · Keith-CY/fiber-link · GitHub\nBackend deployment\nfiber-link/docs/runbooks/fiber-link-stack-deployment.md at main · Keith-CY/fiber-link · GitHub\nDiscourse plugin installation / admin guide\nfiber-link/docs/runbooks/discourse-plugin-admin.md at main · Keith-CY/fiber-link · GitHub\nMilestone 3 acceptance\nfiber-link/docs/acceptance/milestone-3/index.md at main · Keith-CY/fiber-link · GitHub\n9. 交付物\nSeafile\nM3 Delivery\nShare link for M3 Delivery.", "content_html": "

Fiber Link Product Delivery Report

\n

1. Project Overview

\n

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.

\n

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.

\n

Main entry point:

\n\n
\n

2. Delivery Scope

\n

This delivery covers the following core areas:

\n\n
\n

3. User-Facing Product Capabilities

\n

Fiber Link currently supports the following core product loop:

\n
\n \n \n \n
\n

\nYouTube: https://youtu.be/xdPp42APukw

\n
\n

4. Deployment and Service Documentation

\n

4.1 Backend Stack Deployment

\n\n

This document covers:

\n\n

4.2 Compose Service Reference

\n\n

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

\n

4.3 Mainnet / Production-Like Deployment Checklist

\n\n

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

\n\n

4.4 Monitoring and Operations

\n\n

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

\n
\n

5. Discourse Plugin Installation and Configuration Documentation

\n

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

\n

5.1 Discourse Plugin Admin

\n\n

This document covers:

\n\n

5.2 Admin Installation

\n\n

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

\n
\n

6. Architecture and Security Documentation

\n

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.

\n

Core documents:

\n
    \n
  1. \n

    Current Architecture

    \n\n
    2. \n
  2. \n

    Security Assumptions

    \n\n
    3. \n
  3. \n

    Threat Model

    \n\n
    4. \n
  4. \n

    Security Controls Evidence Map

    \n\n
    5. \n
\n

These documents explain:

\n\n
\n

7. Milestone 3 Acceptance and Evidence

\n

7.1 Acceptance Tracker

\n\n

Used to review the milestone and checkpoint overview.

\n

7.2 Milestone 3 Acceptance Index

\n\n

Used to review Milestone 3 acceptance items, including:

\n\n

7.3 Milestone 3 Evidence Index

\n\n

Used to review the delivery evidence index for Milestone 3.

\n
\n

8. Recommended Reading Path for Reviewers

\n

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

\n
    \n
  1. \n

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

    \n
    2. \n
  2. \n

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

    \n
    3. \n
  3. \n

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

    \n
    4. \n
  4. \n

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

    \n
    5. \n
  5. \n

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

    \n
    6. \n
  6. \n

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

    \n
    7. \n
\n
\n

9. Delivery Artifacts

\n\n\n
\n

Fiber Link 产品交付报告

\n

1. 项目概览

\n

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

\n

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

\n

主入口：

\n\n
\n

2. 本次交付范围

\n

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

\n\n
\n

3. 用户可见产品能力

\n

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

\n
\n \n \n \n
\n

\nYouTube: https://youtu.be/xdPp42APukw

\n
\n

4. 部署与服务文档

\n

4.1 Backend Stack 部署

\n\n

该文档覆盖：

\n\n

4.2 Compose 服务参考

\n\n

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

\n

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

\n\n

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

\n\n

4.4 监控与运维

\n\n

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

\n
\n

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

\n

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

\n

5.1 Discourse Plugin Admin

\n\n

该文档覆盖：

\n\n

5.2 Admin Installation

\n\n

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

\n
\n

6. 架构与安全文档

\n

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

\n

核心文档包括：

\n
    \n
  1. \n

    Current Architecture

    \n\n
    2. \n
  2. \n

    Security Assumptions

    \n\n
    3. \n
  3. \n

    Threat Model

    \n\n
    4. \n
  4. \n

    Security Controls Evidence Map

    \n\n
    5. \n
\n

这些文档说明了：

\n\n
\n

7. Milestone 3 验收与证据

\n

7.1 Acceptance Tracker

\n\n

用于查看 milestone 与 checkpoint 总览。

\n

7.2 Milestone 3 Acceptance Index

\n\n

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

\n\n

7.3 Milestone 3 Evidence Index

\n\n

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

\n
\n

8. Reviewer 推荐阅读路径

\n

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

\n
    \n
  1. \n

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

    \n
    2. \n
  2. \n

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

    \n
    3. \n
  3. \n

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

    \n
    4. \n
  4. \n

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

    \n
    5. \n
  5. \n

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

    \n
    6. \n
  6. \n

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

    \n
    7. \n
\n
\n

9. 交付物

\n\n", "like_count": 0, "quote_count": 0 } ] } ] }