Hi @SalmanDev,
Thank you for the rapid revisions and supplementary explanations to the fiber-checkout proposal! Your detailed responses regarding team background, validation plans, project completion and maintenance, and deployment architecture and security — along with adjusting the budget to 1000 USD — gave us a clearer understanding of the project and showed your enthusiasm. The gap in Fiber front-end payment tooling is indeed something the ecosystem urgently needs, and we greatly appreciate your experience as a full-stack blockchain developer and your precise command of @nervosnetwork/fiber-js.
The fiber-checkout project is a “dependency library” or “component library”—a developer-facing tool rather than something end users can use directly. If other developers later build on this package (for e-commerce, tipping, subscriptions, etc.), they will heavily depend on the project’s long-term maintenance. This differs somewhat from the Spark Program’s focus on completing an MVP and initial validation within 1–2 months.
We have decided to place the proposal in Pending status for now. This is not a rejection, but an invitation for you to further refine the proposal so it more closely aligns with the Spark Program’s goals of low barrier to entry, fast pace, and small but realistic prototype validation.
To that end, we suggest you add the following two key pieces of information (please add or expand the corresponding sections in the revised proposal):
- Long-term maintenance plan after 6 months
You have already committed to provide free patches and handle breaking changes for 6 months after the grant ends, which is great. Please further clarify the arrangements for after those 6 months — this will allow the committee and the community to assess the project’s sustainability.For example:
- Apply to the Community Fund DAO for a follow-up proposal.
- Clearer details of the deliverables
The “validation plan” section is already very specific (npm install, one-click testnet testing, coverage, live demo, etc.), but the concrete deliverables remain high-level. Please provide a detailed description of the exact status of each deliverable based on the current list. For example(it’s enough to explain the reasonableness and necessity of the deliverables):
- npm package (supported React version range, exported API list, TypeScript type coverage, etc.)
- Testnet live demo page (core interaction flows, hosting platform, long-term availability considerations, etc.)
These details will help the committee more accurately assess the project’s completeness and its practical value to the CKB ecosystem.
Please reply to the revised proposal under the same Nervos Talk thread (we recommend providing updated versions in both Chinese and English). Once the materials are complete, we will revisit the proposal at the next review meeting (as soon as within 1 week) and provide a final decision. We look forward to your further refinements! Thank you for your continued dedication and patience toward the CKB ecosystem!
Best,
xingtian
On behalf of the Spark Program Committee
Hi @SalmanDev,
感谢您对 fiber-checkout 提案的快速修订和补充说明!您在团队背景、验证方案、结项维护计划以及部署架构与安全性方面的详细回应和将预算调整至1000 USDI,让我们对项目有了更清晰的认识并看到了您的热忱。Fiber 前端支付工具的空白确实是生态亟需填补的点,我们非常欣赏您作为全栈区块链开发者的经验以及对 @nervosnetwork/fiber-js 的精准把控。
fiber-checkout 项目是“依赖库”或“组件库”,是面向开发者的工具,而非一般用户直接拿来可用的工具。如果后续其他开发者基于此包进行二次开发(如电商、打赏、订阅等应用),将高度依赖该项目的长期维护能力。这与星火计划聚焦“1-2 个月内完成 MVP + 初始验证”的定位存在一定差距。
我们决定将提案暂时置于 Pending 状态。这不是拒绝,而是邀请您进一步优化提案,以便更精准地契合星火计划“低门槛、快节奏、小而真实原型验证”的宗旨。
为此,我们建议您补充以下两点关键信息(请在修订版提案中新增或扩展对应章节):
-
6个月之后的长期维护计划
目前您已承诺 grant 结束后 6 个月免费打补丁并处理 breaking change,这非常好。请进一步说明 6个月之后 的安排,这能让委员会和社区看到项目的可持续性。比如:- 到 Community fund dao 申请进一步的提案。
-
交付物的更清晰详情
“验证方案”部分已非常具体(npm install、一键 testnet 测试、coverage、live demo 等),但具体交付内容仍显概括。请在当前的交付物列表的基础上详细说明交付物的具体状况。 比如(能说明交付物的合理性和必要性即可):- npm 软件包(React 版本范围、导出的 API 列表、TypeScript 类型覆盖等)
- 测试网在线演示页面(核心交互流程、托管平台、长期可用性考虑等)
这些细节将帮助委员会更准确评估项目的完整性和对 CKB 生态的实际价值。
请您在 Nervos Talk 同一主题帖下回复修订版提案(建议同时提供中英文更新)。一旦补充完整,我们将在下次评审会议(最快 1 周内)重新讨论并给出最终决定。期待您的进一步完善!感谢您对 CKB 生态的持续投入与耐心!
祝好,
行天
代表星火计划委员会
cc: @zz_tovarishch , @Hanssen , @yixiu.ckbfans.bit