[DIS] CKBoost Gamified Community Engagement Platform Proposal

JackyLHH · October 28, 2025, 12:40am

Just wanted to share the payment status for this proposal so everyone’s aware of the progress:

Initial Down Payment: 360,231 CKB — completed on August 8, 2025
Milestone 1 Payment: 1,928,641 CKB — completed on October 23, 2025

Alive24 · October 31, 2025, 9:46pm

Milestone 2 Report for CKBoost

Preface

Milestone 2 focuses on:

Implementations of advanced API based on Netlify Functions and Proxied validation that are core to new modules including identity verification, achievement, reward tracking, streak bonus;
Implementation of the tipping system with multi-signature peer approvals;

Overview

Work during this iteration centres on expanding the identity system beyond the initial wallet-only approach, introducing community-facing leaderboards, and building the multi-signature tipping rail that unlocks peer recognition. Significant progress landed across the dApp, smart contracts, and serverless functions, while several components remain in active development for the final stretch of the milestone.

Delivered Components

Identity & Verification

Telegram login, wallet binding, and server-side attestation via Netlify function (dapp/app/verify/page.tsx, dapp/netlify/functions/telegram-authenticate.ts)
Unified verification status hook with campaign gating helpers (dapp/lib/hooks/use-verification.ts)
Verification dashboard surfaces current bindings, pending actions, and manual review intake UI

Gamification & Profiles

Chain-backed leaderboard page with live Points UDT aggregation and per-user positioning (dapp/app/leaderboard/page.tsx, dapp/lib/services/leaderboard-service.ts)
Contributor dashboard summarizes submissions, campaign progress, token balances, and activity timeline (dapp/app/dashboard/page.tsx)
Navigation and layout updates expose leaderboard, tipping, and verification entry points across the dApp
Streak bonus implemented
Achievement implemented

Tipping Foundations

ckboost-tipping-type contract skeleton with business rules for supporter whitelists and approval thresholds (contracts/contracts/ckboost-tipping-type/src/recipes.rs)
SSRI-enabled tipping service/provider capable of proposing or updating tips, fetching approved proposals, and reading funding pools (dapp/lib/services/tipping-service.ts, dapp/lib/providers/tipping-provider.tsx)
Community tipping pages with proposal form, Nostr-backed long descriptions, and detailed proposal cards (dapp/app/tipping/*, dapp/components/tipping-card.tsx)

Admin & Infrastructure

Protocol administration components expose tipping configuration, script hashes, and pending changes (dapp/components/admin/protocol/*)
Deployment documentation for Telegram identity infrastructure (dapp/DEPLOYMENT.md)
Updated deploy-contracts.sh to recognize tipping contracts alongside existing script bundle

Postponed Items

Generic identification data structure is available for DID/KYC.
Multiplier as not meaningful after bonus streak is implemented

Appendix: Deliverables for M2

Expand verification methods: integrate Telegram admin review, prepare DID/KYC hooks for later.
- Update: Telegram binding is now automatic. DID/KYC is ready for further implementation.
Design simple leaderboards and user profiles with progress tracking.
- Update: Implemented.
Add streak bonuses, difficulty multipliers, and badge milestone features.
- Update: Streak bonus and badge milestone features are now implemented. Difficulty multipliers are postponed.
Develop the tipping system with multi-signature peer approvals.
- Update: Implemented.
Improve user profiles: public achievements, contribution logs.
- Update: Implemented.
Build out admin dashboard for better submission management and analytics.
- Update: Implemented.

Footnotes

Milestone site has been promoted to M2 from M1.
All follow ups and planned features that are not scheduled are posted as issues in GitHub · Where software is built with appropriate taggings and notes.
Testing guidelines are similar to the previous one for M1; refer to this report for M2 coverage.
M3 would start as M2 gets feedback and reviews.

neon.bit · November 25, 2025, 12:01pm

Thanks @Alive24 for your continued work on this. I have conducted testing and feedback for M2 features and would advise it is ready for M3. @terrytai

I have also requested that the CKB milestone payment be adjusted to reflect the USD value in a separate thread.

zz_tovarishch · December 19, 2025, 8:34am

Dear community, a quick update, CKBoost’s M2 funds have been paid by the DAO Treasury: https://explorer.nervos.org/transaction/0x07aef49a7290a534a901bb1e1bb701c141976cb4a7843cd3c4772e88ed12dfcb

Details: 4635652.81*0.3 = 1,390,695.843 CKB

Additionally, according to Transitional Policy Statement (Community Fund DAO v1.1), Terry subsidized the funds: https://explorer.nervos.org/transaction/0x028bbd907370ff4f703fc794adf1d6542bea995381c7e3245d964779fa9a5ced

Details: 6000 - (1,390,695.843 * 0.002315) = 2,780.539123455
2,781 / 0.002315 = 1,201,295.8963282937

亲爱的社区成员，快速更新一下，CKBoost 的 M2 资金已由 DAO 金库支付：https://explorer.nervos.org/transaction/0x07aef49a7290a534a901bb1e1bb701c141976cb4a7843cd3c4772e88ed12dfcb

详情：4635652.81 * 0.3 = 1,390,695.843 CKB

此外，根据 Transitional Policy Statement (Community Fund DAO v1.1) 的信息，Terry 提供了资金补贴：https://explorer.nervos.org/transaction/0x028bbd907370ff4f703fc794adf1d6542bea995381c7e3245d964779fa9a5ced

详情：6000 - (1,390,695.843 * 0.002315) = 2,780.539123455
2,781 / 0.002315 = 1,201,295.8963282937

Alive24 · February 5, 2026, 4:15pm

Milestone 3 Report for CKBoost

Milestone 3 focused on shipping the remaining core implementation work, followed by a structured testing campaign to validate real-world flows and polish the product based on feedback. At this stage, the main code deliverables are completed; the remaining work is primarily around organizing end-to-end real campaign testing and iterative improvements based on test results which would be organized by Neon very soon.

In addition beyond milestone 3, we also implemented a major UI update thanks to the awesome design from Ahrom.

Delivered in Milestone 3

New Implementation

Staff management module
Social interactions module
1. Nostr based commenting, liking, tipping
2. Indexing and rendering for social interactions anchored to event
3. Verification and management.
Major UI Updates

UX Improvement

Global transaction tracker
Explorer integration

Module Enhancement and Fixes

Cover image
Proxy Admin Workflow for Telegram verification, streak bonus, achievements.
Event expiration
Caching and loading

Documentation & Research

Nextra integration
Research on Submission/Verification
- X Integration
- Timestamp based validation with Netlify function
- Oracle-based onchain/offchain validation with Netlify function
- Nervos Talk integration
Research on new features for next proposals

Outstanding Items

Real test campaign and reward distribution
Real verification flow test
Improvements and bug fixes based on real test feedback.

The main milestone site has been promoted to M3 at https://ckboost.netlify.app/.

The previous site is available at https://milestone-2-preview--ckboost.netlify.app/ but many features that rely on on-chain data and domain configuration won’t work.

zz_tovarishch · March 17, 2026, 3:29am

Hi @Alive24,

Thanks for submitting the M3 report. I brought it to the DAO Committee, and there are a few details would like to clarify before moving forward with the M3 payment and project closure.

The M3 scope within the proposal included deploying real test campaigns, testing reward distribution and verification flows with real users, and publishing findings from those tests. The current report notes that the main code deliverables are complete, but describes the real campaign testing as upcoming work rather than completed work.

We’re aware the platform is being used in the AI hackathon, which sounds like it could serve as the test M3 was aiming for. If that’s the case, it would be very helpful to have a brief supplementary report covering how the platform performed during the hackathon (or any other live usage), what was tested, and what the results and takeaways were.

This isn’t about questioning the quality of what’s been built, just want to make sure the milestone record is complete and aligns with the original scope, so the project can close out cleanly.

感谢您提交 M3 报告。我已将其提交给 DAO 委员会，在推进 M3 付款和项目收尾工作之前，有一些细节需要澄清。

M3 的提案范围包括部署真实测试活动、使用真实用户测试奖励分配和验证流程，以及发布这些测试结果。目前的报告指出主要代码交付已完成，但将真实活动测试描述为即将开展的工作，而非已完成的工作。

我们了解到该平台正在 AI 黑客松中使用，这听起来正好可以作为 M3 的测试。如果是这样，那么最好能有一份简短的补充报告，介绍该平台在黑客松（或其他任何实际使用）期间的表现、测试了哪些内容以及结果和收获。

这并非质疑已开发产品的质量，只是想确保里程碑记录完整且与最初范围一致，以便项目能够顺利收尾。

neon.bit · March 17, 2026, 9:13am

Just to chime in, yes the ongoing hackathon is utilising CKBoost to facilitate platform testing and feedback. It’s helped identify a few bugs so far which have been fixed.

I will gather platform-specific testing data, and feedback from participants after the hackathon and produce a report to mark the conclusion of M3. My understanding is that Alive’s latest post is a status update but not confirmation of completion.

zz_tovarishch · March 17, 2026, 9:26am

Thanks for the clarification, Neon. Good to know the hackathon is serving as the real campaign testing ground for M3.

Waiting for your post-hackathon report once it’s ready.

neon.bit · April 12, 2026, 7:06pm

CKBoost Post-Hackathon Testing & Feedback Report

CKBoost served as the live campaign management platform for the CKB AI Agent Hackathon, providing real testing data across both the campaign manager and user flows. This report highlights which issues were identified and fixed, which need to be addressed prior to completion, and enhancements that may be considered for future development. Also included is summarised feedback of using the platform by hackathon participants.

Overall perception

As a campaign manager, I found the process of creating campaigns relatively straightforward. All of the necessary fields were present, and a variety of options allowed me to customise the campaign appropriately. Setting and changing start/end dates for a campaign was smooth and immediately reflected on the campaign card. Extending or reopening a campaign required no additional steps. As creating a campaign can take some time, the campaign input page had a useful save feature which meant that I could return to the page at a later time and continue from where I left off.

Some of the UI around campaign and platform admin dashboards was a little confusing, but isn’t insurmountable and should be simple to improve. The main UX issue I found was around the costs associated with approving quests, especially multiple quests at once. This is mentioned in more detail below.

As a user, I found navigating the website quite easy. The initial page sync is quite long, and each page needs its own time to sync. Outside of this, I could explore and participate in campaigns, with an easy to follow user flow. Points were issued reliably, as were UDT/CKB. Tipping works as expected, although for future development it would be good to tip someone by their X or telegram handle which they could then claim on CKBoost. Telegram verification was surprisingly smooth, with a bot handling messages sent to my telegram account to confirm identity. I think user profile management and display could be improved, with did:ckb integration a logical step moving forward.

Users who participated in the hackathon were also asked to share their feedback.

Based on 10 respondents, overall reception to CKBoost was positive. Participants consistently praised the platform’s clean UI and ease of navigation, with one describing it as “clear and easy to use” and another highlighting that “simplicity stood out” as its most important quality. The gamified feel of the quest structure was also noted favourably, with the design described as looking “gamified” in a good way. Onboarding was flagged as straightforward by multiple participants, and the general flow of moving through quests was described as clear with no major issues encountered.

The most commonly reported friction points were slow page load times, issues with file uploads, and quest progress resetting on page refresh. A few users also noted that submission form inputs felt over-engineered for the information being collected, and that the leaderboard only showed the top 10 limited visibility for most participants. Detailed breakdowns of each of these are captured in the suggestions below.

Bugs Identified & Resolved

The following issues were identified and closed during the testing and campaign period:

Resolved before/during the campaign (no formal github issue)

Quests not editable after creation. Quests could not be modified, added, or deleted once set. Resolved prior to campaign launch.
Markdown not rendering correctly in long description. Formatting written in the campaign description editor was not being fully reflected when published. Resolved prior to campaign launch.
Campaign commencement flow unclear. The path from campaign page to first quest was not intuitive. An additional button directing users straight to Quest 1 was added to address this.
Campaign page intermittently failing to display long descriptions. When navigating directly to a campaign link, the long description would occasionally not appear on load. Resolved during the campaign period.
Exporting quest data. Manually parsing through quest submissions on the campaign management side was flagged as time consuming. A feature was added to export quest submissions in XLS format.

Resolved via GitHub issues

#41 Social interaction verification unreliable (tag-based search). Searching by tag to verify social interactions (e.g. posts, reposts) was not reliably picking up submissions. Resolved by switching to a replaceable event approach that directly stores the Nostr event ID for social interactions.
#43 UI: Markdown formatting not fully rendering on publish. Campaign descriptions with formatted content (headers, bullet points, line breaks, text sizes) were only partially rendering after publishing, with bold being preserved but other styles lost. Resolved.
#40 Expired event handling. Issues arising from expired campaign events were identified and resolved.

Issues needing resolution for M3

#48 Reducing platform transaction costs. Some actions such as adding/removing quests and approving submissions incurred higher-than-expected CKB fees, while other operations had inconsistently low fees. Fee predictability and overall cost-to-interact must be addressed before mainnet.
#49 Documentation searching error. The onboarding documentation currently does not display and the search bar returns an error. As this is part of the M3 deliverables, this needs resolution.
Bug reports and “todo” items to clean up if addressed. Most of these are open issues from November 2025 and need to be formally concluded.

Enhancements for Next Development Round

Based on my testing and feedback from users, the following have been logged and remain open for future development. They are not strictly required for M3.

Page load time. The initial sync takes 5-10 seconds to ensure the latest on-chain campaign data is visible. Several users flagged that this can feel like too long to wait. I would recommend exploring whether this wait can be reduced to improve UX.
Submission form UX. The rich text/Markdown editor used for submission inputs (e.g. for a Telegram username or file upload) was flagged as unnecessarily complex. Simple text inputs and a standard file picker would better suit these fields.
Pre-population of quest fields. Quest submission fields were auto-populating with data from previous quests, requiring users to manually clear them before entering new information. Other users reported quest details not saving on refresh, so more consistent behaviours around quest saving would be beneficial.
Leaderboard pagination. The leaderboard currently displays only the top 10. Users suggested expanding this to at least 30–50 to give more participants visibility of their standing.
Image upload limitations. From my testing, it appeared as though images above ~80kb were rejected by Nostr relayers or caused a long delay for confirmation. Other users reported a similar problem. A size warning or compression step would help. Alternatively, using a different method to handle larger files may be necessary
Better identity integration. Tying wallet/address identity to quest submissions and the explorer was unclear on the campaign management side. Better profile display and identity context within the platform is needed. Additionally, better profile management and customisation options would give the site a more personalised feel.
Export refinement. The export function exists but outputs need to be presented in a more user-friendly format.

A list of other potential feature additions is recorded on issue #31.

Conclusion

CKBoost has made significant progress since its last milestone, and its successful deployment as the campaign management platform for the CKB AI Agent Hackathon represents a meaningful checkpoint. The platform held up well under live conditions, with numerous bugs identified and resolved through the testing process. This is a huge credit to @Alive24 and his work on the platform. This is a credible platform to organise campaigns, drive engagement, and disburse rewards. I will now be looking into utilising this for monthly progress reporting of CKBuilders and strategies for social media campaigns.

Prior to final M3 completion and progression to mainnet, some work is needed around 1) transaction cost optimisation, 2) onboarding documentation and search functionality, and 3) concluding any outstanding github issues.