Hello Nervos Community 
I’d like to introduce DripFund – a creator-first, on-chain donation platform for Nervos CKB. The MVP is live on testnet and evolving into a multi-creator funding layer.
DripFund allows anyone to create a personal donation page, receive CKB directly into their wallet, and permanently store supporter messages in CKB cell data.
A working MVP for single-recipient donations is already live on testnet: https://dripfund.vercel.app, and I’m currently expanding it into a multi-creator platform with username-based pages and creator profiles.
I’m sharing this early to gather ecosystem feedback before taking it to the next level.
The Problem: Creator Support on CKB is Still Fragmented
Today, if a creator or open-source developer in the CKB ecosystem wants to receive support, the options are limited:
-
Web2 platforms (custodial, off-chain, fee-heavy)
-
Raw wallet addresses (no context, no supporter wall, no messages)
-
No creator-focused funding tool is native to CKB
-
No simple shareable donation pages
There is no lightweight, non-custodial, on-chain donation layer designed specifically for:
-
CKB builders
-
open-source contributors
-
educators
-
community creators
DripFund aims to fill this gap.
What DripFund Does
At its core, DripFund lets anyone create a donation page and receive CKB with on-chain supporter messages.
Supporter flow
-
Visit the creator page
-
Connect wallet
-
Enter name + message
-
Choose amount
-
Sign transaction
-
Message stored on-chain + funds go directly to the creator’s wallet
Creator flow (next phase)
-
Connect wallet
-
Choose username
-
Get page like:
dripfund.org/username (planned)
-
Share link
-
Receive support transparently on-chain
Why CKB is a Great Fit for This
DripFund is intentionally designed around CKB’s strengths.
1. Cell data = permanent supporter messages
Each donation creates a cell where:
-
lock script → creator address
-
capacity → donated CKB
-
data → compact encoded JSON message
Example stored on-chain:
{"n":"alice","m":"keep building!"}
This gives:
-
permanent supporter messages
-
transparent donation history
-
verifiable funding trail
2. UTXO / Cell model fits donation receipts well
Each donation is:
-
discrete
-
ownable
-
queryable
-
indexable
This maps naturally to:
one donation → one cell → one message → one supporter record
3. CCC SDK makes wallet + txn UX realistic
Using CCC:
-
Wallet Connect is smooth
-
Txn building is manageable
-
JoyID / Nexus compatible
-
Frontend ↔ Wallet flow is practical for real users
Current Status - MVP is live on testnet
I’ve built and deployed a working MVP (single-recipient version). Please feel free to visit and test the platform:
Current features
-
CCC wallet connect
-
Donation txn builder (backend-assisted)
-
Send CKB to the recipient
-
Store donor name + message in cell data
-
Compact JSON → hex encoding
-
Donation history indexing
-
Supporter wall UI
-
Testnet deployment
GitHub Repository
https://github.com/adisuyash/ckb-notes/tree/main/buy-me-a-coffee
Related Screenshots (MVP on Testnet)
If you’d like to try the full flow, feel free to send a small testnet donation and leave a message – it helps validate real transactions and UX end-to-end. Feedback (and fun messages) are very welcome.
Planned Next Phase – Multi-Creator Platform
The next milestone is turning this into a real creator platform.
Planned features
-
Multi-creator support
-
Username → wallet mapping
-
Creator profile pages
-
Supporter wall per creator
-
Donation tiers + custom amounts
-
Leaderboard & stats
-
Embeddable donation widget
-
Mainnet deployment
-
Open-source core modules
Identity Design Choice (and Why)
I explored:
-
.bit names
-
did:ckb
-
naming protocols
But for onboarding simplicity, I’m choosing:
username → wallet mapping (app-level)
for MVP.
Reasons:
-
zero extra cost for users
-
zero protocol dependency
-
faster onboarding
-
better UX
Later:
-
did:ckb, optional
-
.bit, optional
-
domain linking, optional
Would appreciate feedback on whether this aligns with CKB best practice.
Technical Stack
| Layer | Tech |
|---|---|
| Frontend | React + TypeScript + Vite |
| Wallet | CCC SDK |
| Backend | Node + Express |
| Chain | Nervos CKB |
| Indexing | Off-chain indexer |
| UI | TailwindCSS |
| Deployment | Vercel |
Open Questions - I’d Love Feedback On
I’m sharing this early to stay aligned with ecosystem best practices, as I’m still in the learning phase.
Concept & positioning
-
Does a creator-first donation platform make sense as a social app on CKB?
-
Should this be positioned as creator tooling vs general crowdfunding?
-
Any other suggestions? Please let me know
Architecture
Current design:
-
username → wallet mapping (off-chain)
-
donation metadata on-chain
-
indexing layer off-chain
-
backend-assisted txn building
Questions:
-
Good hybrid model for CKB apps?
-
Should the txn building move entirely to the client side?
On-chain data design
-
Using compact JSON in cell data for messages
-
Is there a better pattern for donation metadata?
Scaling
-
Best indexing strategy for many creator addresses?
-
Better discovery patterns for donation cells?
Please feel free to share any blogs, articles, or video tutorials that could help me learn more and continue improving this.
What This Could Become for CKB
If successful, DripFund could become:
-
default creator support layer on CKB
-
funding tool for open-source builders
-
donation layer for community projects
-
onboarding bridge for new users
-
showcase of CKB social apps
It’s not DeFi – it’s creator economy infrastructure built natively on CKB.
Closing
I started DripFund as a “Buy Me A Coffee” style project while participating in the CKB Builders program, and my goal is to grow it into a solid, creator-focused application. I’d really value technical and product feedback from the community before expanding it further and moving toward a funding proposal.
Please feel free to be direct and critical – whether it’s architecture, positioning, UX or protocol usage – all feedback is welcome.
Thanks for reading 
Excited to keep learning and building