1. Project Name
Tiko Creator Commerce Expansion + Private Beta Validation
2. Team / Individual Profile
Project: Tiko
Type: Ticketing and creator commerce platform built on CKB
Lead: Indie Developer
Contact: Discord - @getigeti21
I have already built the live ticketing foundation of Tiko, including event
listing, checkout, CKB testnet payment confirmation, ticket issuance, QR-based
access, operator check-in, and Spore-backed ownership. The current product is
already testable and demonstrates the core event commerce flow working end to
end on CKB testnet.
GitHub: GitHub - Tiko-T/Tiko · GitHub
Live website: https://tiko-pied.vercel.app/
Current test access
- Email: [email protected]
- Password: 7V8ogwFc845anR1SqX2HLcZ3xojx0CRT
How to test the live product
- Open the live website.
- Sign in with the test credentials above.
- Browse the available event listing.
- Open the event details page and proceed to checkout.
- Complete the wallet-based payment flow on CKB testnet.
Use the internal token faucet for test tokens. - Submit the payment transaction hash.
- Verify ticket issuance, QR-based access, and post-purchase ownership flow.
I am applying for Spark support to build the next stage of Tiko: expanding it
from a working ticketing product into a broader creator commerce offering, and
then running a short private beta to validate that expanded product with real
users.
3. Project Description
Problem
Most event and creator platforms are fragmented.
A creator may use:
- one tool for events
- one tool for digital products
- one tool for memberships
- one tool for fan rewards
- another tool for authenticity or collectible ownership
This creates a broken experience for both creators and fans. Ticketing is
disconnected from post-purchase engagement, digital commerce is disconnected
from community access, and blockchain ownership often exists separately from
usable product workflows.
Solution
Tiko combines ticketing and creator commerce into one product.
The existing product already handles event ticketing. For this Spark cycle,
the scope is intentionally narrowed to the first 3 creator-commerce
capabilities that are the best fit for a 1-2 month validation cycle:
- Digital drops
Creator-led downloadable or unlockable products such as artwork, media,
templates, and exclusive files. - Memberships and passes
Fan-club style access products, VIP passes, and community memberships. - Limited editions and collectibles
Editioned creator items and event collectibles with Spore-backed ownership
and provenance.
Existing Product State
Already working:
- event listing and publishing
- ticket checkout flow
- CKB testnet payment confirmation
- order tracking
- ticket issuance
- QR access and operator check-in
- Spore-backed ownership after purchase
What This Grant Will Build
This Spark cycle will implement 3 creator-commerce components:
A. Digital Drops
Creators can list and sell digital products that buyers unlock after payment
confirmation.
B. Memberships and Passes
Creators can issue access-based products such as VIP memberships, fan passes,
and community access products.
C. Limited Editions and Collectibles
Creators can issue limited digital collectibles tied to products, campaigns,
or attendance, with Spore-backed ownership and provenance.
This scope is intentionally limited to validate the strongest creator-commerce
expansion paths first before moving to broader categories such as bundles, fan
rewards, and physical merch authenticity.
4. Why This Fits Spark
This project is a strong Spark fit because:
- it extends a working prototype rather than starting from zero
- it can produce a meaningful prototype expansion within 1-2 months
- it combines technical development and early user validation
- it clearly aligns with Web5 thinking: familiar Web2 UX with Web3 ownership
where useful
5. Expected Deliverables
By the end of the grant period, I will provide:
Product Deliverables
- creator-commerce expansion inside Tiko for:
- digital drops
- memberships / passes
- limited editions / collectibles
- updated creator-facing listing and management flows for those 3 product
types - updated buyer-facing discovery and purchase flows for those 3 product types
- beta-ready private test environment
Technical Deliverables
- public open-source code repository updates
- deployment instructions
- concise product and technical documentation
- live or recorded product demo
- walkthrough of the 3 new creator-commerce flows
User Validation Deliverables
- structured private beta with early users
- user feedback summary
- product learning report
- recommendations for next-stage iteration
6. Estimated Completion Time
1.2 months
Planned execution window: 5 weeks
7. Clear To-Do List
Week 1
- finalize narrowed creator-commerce scope
- define delivery boundaries for:
- digital drops
- memberships / passes
- limited editions / collectibles
- prepare creator-facing product setup structure
Week 2
- implement creator-facing listing flows for the 3 product types
- implement buyer-facing discovery and purchase entry points
- connect checkout and order handling to the 3 product types
Week 3
- implement fulfillment logic for digital drops
- implement access logic for memberships / passes
- implement collectible issuance flow for limited editions
Week 4
- connect the 3 product types into buyer library / ownership views
- internal QA and end-to-end testing on CKB testnet
- prepare private beta environment
- onboard early testers and selected creators
Week 5
- run private beta
- collect structured feedback
- summarize user insights, friction points, and adoption signals
- publish completion report, demo, repo updates, and learnings
8. User Testing Plan
This project includes a real early-validation phase, not just feature
delivery.
Private Beta Goals
- validate whether creators understand the combined ticketing + creator-
commerce offering - validate whether buyers understand and adopt the first 3 creator-commerce
product types - identify which of the 3 categories has the strongest practical demand
- identify where blockchain-backed ownership improves perceived trust or value
Planned Beta Scope
- 3-5 early creators / operators
- 20-30 users
- structured feedback collection through direct testing and product
observation - track usage across listing, purchase, fulfillment, and post-purchase access
What I Want to Learn
- which of the 3 categories is most commercially attractive
- what creators want to sell alongside tickets first
- whether buyers understand and value ownership-backed creator products
- where the current product flow is too complex
- what should become the next priority after Spark
9. Required Funding
Requested amount: $1,450
Suggested funding composition
- 50% USDI
- 50% CKB equivalent
10. Funding Breakdown
Development and product implementation — $850
- creator-facing flows for 3 product types
- buyer-facing flows for 3 product types
- fulfillment logic
- collectible issuance flow
- deployment and environment iteration
Beta testing and user validation — $400
- user recruitment support
- beta coordination
- creator onboarding for testers
- feedback collection and synthesis
- demo preparation and reporting
Infrastructure and operational costs — $200
- test deployment operations
- storage and service costs
- environment maintenance during beta
- small contingency for minor iteration during testing
11. Relevance to the CKB Ecosystem
This project is directly relevant to the CKB ecosystem because it uses CKB and
Spore in a product-shaped way that real users can understand.
Practical ecosystem relevance
- demonstrates a real end-user ticketing and commerce flow on CKB
- expands CKB usage beyond payments into ownership, authenticity, and creator
product flows - shows how Web2-style UX and Web3 ownership can coexist
- creates a practical reference product for creator commerce on Nervos
Why CKB matters here
CKB is not being used as decoration. It provides:
- ownership-backed product fulfillment
- Spore-based provenance for creator items
- a foundation for collectible, access, and creator-commerce flows that make
sense for creators and fans
This is aligned with the ecosystem goal of building practical Web5 products
that connect real user workflows with blockchain-backed value.
12. Alignment With Web5 Philosophy
This proposal strongly aligns with the Web5 direction described by Spark:
Organic combination of Web2 and Web3
Buyers browse and purchase through a familiar web flow, while blockchain is
used where it adds ownership and trust.
User-centric and human-oriented
The focus is not on protocol complexity but on creator products, audience
relationships, and useful buying experiences.
Small but real
The scope is intentionally sized for a 5-week cycle and tied to concrete
prototype and beta outcomes.
Prototype plus feedback loop
The proposal includes both implementation and real user validation.
13. Open Source Commitment
Yes.
All work delivered under this Spark proposal will remain open source and will
be published through the existing repository.
14. Completion Outputs
At completion I will provide:
- updated open-source repository
- product demo
- short implementation summary
- private beta report
- key user feedback findings
- comparison of planned scope vs actual completed scope
- recommendations for next-stage iteration
- verification evidence package:
- demo links
- screenshots
- transaction links
- screen recordings
- test documentation
15. What Success Looks Like
This Spark project will be successful if, by the end of the cycle:
- Tiko supports creator-commerce flows beyond tickets for the first 3
categories - digital drops, memberships / passes, and limited editions / collectibles
exist as usable prototype capabilities - creators can understand the narrower creator-commerce offering
- buyers can successfully purchase and use at least one of the 3 new product
categories - early beta feedback reveals which of the 3 categories has strongest market
pull - the CKB ecosystem gains a concrete creator-commerce reference product beyond
ticketing
16. Closing Summary
Tiko already proves that ticketing on CKB can work in a real, user-facing way.
This grant will help prove the next step: that ticketing can become the
foundation for a broader creator-commerce platform, beginning with a tightly
scoped first expansion into:
- digital drops
- memberships / passes
- limited editions / collectibles
17. How to Verify
Test Environment Access
GitHub: GitHub - Tiko-T/Tiko · GitHub
Live website: https://tiko-pied.vercel.app/
Current test access
- Email: [email protected]
- Password: 7V8ogwFc845anR1SqX2HLcZ3xojx0CRT
Existing Ticketing Verification
Reviewers can already verify the current foundation by:
- Opening the live website
- Signing in with the credentials above
- Browsing an available event
- Proceeding to checkout
- Completing testnet payment
- Submitting the transaction hash
- Verifying ticket issuance, QR-based access, and ownership flow
This confirms the product foundation already exists before this Spark cycle
begins.
Verification Scope for This Spark Cycle
Reviewers will verify the 3 narrowed creator-commerce capabilities:
- Digital drops
- Memberships / passes
- Limited editions / collectibles
Verification Steps and Pass / Fail Criteria
A. Digital Drops
Verification steps
- Creator lists a digital drop
- Buyer opens the product page
- Buyer completes purchase
- Buyer receives access to the purchased digital item
Pass criteria
- listing is visible in the storefront
- checkout completes successfully
- buyer can access the purchased digital drop after confirmation
B. Memberships / Passes
Verification steps
- Creator lists a membership or pass
- Buyer purchases the membership product
- Buyer receives the membership/pass access outcome
- Membership appears in buyer-facing account or library flow
Pass criteria
- membership product can be listed and purchased
- buyer receives access after successful confirmation
- buyer can see the membership in the product experience
C. Limited Editions / Collectibles
Verification steps
- Creator lists a limited-edition collectible product
- Buyer completes purchase
- Product triggers collectible issuance
- Ownership-backed result is visible in the buyer flow
Pass criteria
- collectible product can be purchased
- collectible issuance flow completes
- ownership result is visible and linked to the purchase
Evidence Publication
Evidence will be published through:
- GitHub repository updates
- product demo or walkthrough video
- screenshots of creator and buyer flows
- screen recordings for end-to-end verification
- transaction links / hashes where relevant
- completion documentation and summary report
Private Beta Verification Loop
Source of test participants
- 3-5 early creators / operators
- 20-30 test users
Task design
Testers will be asked to:
- create or review product listings in the 3 new categories
- complete purchases
- verify access / ownership outcomes
- report friction points and clarity issues
Key metrics
- successful listing completion rate
- successful purchase completion rate
- successful fulfillment / access completion rate
- qualitative clarity of the product offering
- perceived usefulness of ownership-backed features
Feedback collection
Feedback will be collected through:
- direct structured tester feedback
- guided walkthrough sessions
- short written summaries
- product usage observation
Final report format
The completion report will include:
- what was built
- what was tested
- what worked
- what failed or caused confusion
- which of the 3 categories showed strongest demand
- recommended next-stage priorities