Spark Program | CKB Wallet Behaviour Intelligence

Project Name

CKB Wallet Behaviour Intelligence

Team

Project Description

Problem

CKB provides transparent and rich on-chain data through its Cell-based architecture, but there is currently no open-source tooling that converts raw transaction data into actionable behavioral intelligence.

Developers can easily access transaction histories through explorers and APIs, but understanding how a wallet behaves still requires significant custom analysis and infrastructure.

Questions such as:

  • Is this wallet behaving like an individual user?
  • Does this wallet exhibit highly automated activity?
  • Is this wallet likely operating as an exchange-controlled wallet?
  • Does this wallet demonstrate unusual transaction behavior compared to typical network participants?

cannot currently be answered through a simple API or reusable ecosystem tool.

As the CKB ecosystem grows, analytics platforms, wallet providers, security tooling, explorers, and future infrastructure services can benefit from richer wallet context rather than relying solely on raw transaction records.

This project is not focused on detecting low-cost Sybil attacks. CKB’s Cell model and state occupation costs already increase the cost of mass wallet creation. Instead, the project focuses on behavioral analysis and wallet classification, providing ecosystem developers with reusable analytics infrastructure built specifically for CKB.

Solution

We propose a lightweight Wallet Analytics & Classification API for the CKB ecosystem.

The system will analyze wallet transaction histories using machine learning and behavioral feature extraction.

The initial version will focus on:

  • Transaction timing patterns
  • Transaction frequency patterns
  • Wallet interaction graph relationships
  • Cell usage and transaction flow characteristics

Using these features, the system will generate:

  • Human-like behavior score
  • Automated behavior score
  • Exchange-like behavior score
  • Confidence metrics

Developers will be able to submit a CKB wallet address through an API or web dashboard and receive a behavioral classification result.

The goal of this Spark Program project is to deliver a working prototype that demonstrates how behavioral analytics can enrich wallet intelligence across the CKB ecosystem.

Expected Deliverables

1. Open Source Repository

A public GitHub repository containing:

  • CKB data extraction pipeline
  • Feature engineering pipeline
  • Model training code
  • API implementation
  • Deployment instructions
  • Technical documentation

2. Wallet Classification API

A public REST API capable of:

  • Accepting a CKB wallet address
  • Returning wallet classification results
  • Returning confidence scores

3. Web Dashboard

A simple dashboard allowing users to:

  • Input wallet addresses
  • View classification results
  • View behavioral indicators and scores

4. Initial Wallet Dataset

A curated dataset containing approximately:

  • 500 human-like wallets
  • 500 automated and / or exchange-like wallets

5. Documentation

Documentation covering:

  • API usage
  • Deployment instructions
  • Model methodology
  • Evaluation results

6. Public Demonstration

  • Live demo deployment
  • Demonstration video
  • Project completion report

How To Verify

The project can be verified without requiring code review.

API Verification

Users can submit a CKB wallet address to the public API and receive:

  • Behavioral classification
  • Confidence scores

Dashboard Verification

Users can access the public dashboard and classify wallet addresses directly through the interface.

Repository Verification

Community members can:

  • Access the public GitHub repository
  • Review documentation
  • Reproduce model training and deployment

Demo Verification

Reviewers can:

  • Access the deployed demonstration
  • Test known wallet addresses
  • Verify expected outputs

Documentation Verification

Users can follow the provided setup guide and deploy the system locally.

Example integration: A Randomn wallet Provider

**

Required Funding

Developer Time

Phase Hours Description
Data extraction and feature engineering 30 hrs CKB-CCC integration, Explorer API integration, transaction ingestion pipeline, feature engineering
Model development and evaluation 30 hrs Dataset preparation, model training, model evaluation, classification pipeline
API and dashboard implementation 25 hrs REST API development, dashboard implementation, model serving integration
Testing, deployment and documentation 25 hrs QA testing, deployment, documentation, demo preparation and final reporting
Total Developer Time 110 hrs Approximately 6 weeks of development

Infrastructure & Deployment Costs

Item Unit Cost Quantity Subtotal (USD)
VPS hosting (API, dashboard, model inference server) $12/month 2 months $24
Database $20/month 2 months $40
Domain name for public API and demo ~$12/year 1 $12
Infrastructure & Deployment Subtotal $76

These costs support the public deployment of the Wallet Analytics & Classification API, dashboard hosting, model serving, dataset storage, monitoring, testing, and demonstration infrastructure required for the Spark Program deliverables.

Developer Compensation

Item Amount
Total grant requested $1,000
Infrastructure & deployment costs $76
Dataset preparation & validation $124
Remaining allocated to developer time $800

Effective Hourly Rate

Metric Value
Total developer hours 110 hrs
Developer budget $800
Effective hourly rate $7.27/hr

The requested funding supports approximately 110 hours of development work covering blockchain integration, wallet data extraction, feature engineering, machine learning implementation, API development, dashboard development, testing, deployment, documentation, and public demonstration delivery.

The effective rate of approximately $7.27/hour reflects the prototype-focused nature of the Spark Program and the goal of delivering a functional open-source proof of concept for the CKB ecosystem within a limited funding budget.

Estimated Completion Time

6 weeks total

  • 4 weeks active development
  • 2 weeks testing, documentation, and deployment

The project scope is intentionally limited to delivering a verifiable prototype suitable for ecosystem validation and future iteration.

Clear To-Do List

Week 1

  • Integrate CKB-CCC
  • Integrate Explorer API
  • Build transaction ingestion pipeline

Week 2

  • Implement feature extraction pipeline
  • Create wallet labeling workflow
  • Build initial dataset

Week 3

  • Complete labeled dataset
  • Train classification model
  • Evaluate model performance

Week 4

  • Develop REST API
  • Develop web dashboard
  • Integrate model inference service

Week 5

  • Conduct testing
  • Improve classification quality
  • Collect initial feedback

Week 6

  • Deploy public demo
  • Publish documentation
  • Release open-source repository
  • Publish completion report

Relevance to the CKB Ecosystem

Meeting Actual Needs in the CKB Ecosystem

The project provides a reusable wallet analytics layer that can benefit:

  • Wallet providers
  • Blockchain explorers
  • Analytics platforms
  • Security monitoring tools
  • Future infrastructure services

Today, teams that require wallet behavior analysis must build their own infrastructure and classification logic from scratch.

This project provides an open-source foundation that can be reused and extended by ecosystem participants, reducing duplicated effort while encouraging experimentation with behavioral analytics on CKB.

The project also contributes an initial labeled wallet dataset and wallet classification API that can serve as a starting point for future ecosystem tooling.

Utilizing CKB’s Technical Architecture

The project leverages CKB’s transparent transaction model and Cell-based architecture to extract behavioral signals that are difficult to obtain from simple account balances alone.

Using transaction flows, Cell consumption patterns, transaction timing, and wallet interaction relationships, the system demonstrates how machine learning can be applied to CKB-specific data structures to generate useful wallet insights.

This showcases a practical analytics use case built directly on top of CKB’s unique architecture and provides a foundation for future wallet intelligence and ecosystem analytics tools.

4 Likes

Hi @mulinya,欢迎你在 Spark Program 提案!

以下是我在提交委员会审核前的一些个人看法,供你参考,不代表委员会立场。
通读提案后,我梳理了以下几点可能影响委员会评审的问题,建议你在正式评审前做针对性调整:

1. 提案结构顺序混乱,可读性较差。

当前提案的章节顺序:概述 → 已完成工作(里程碑+预算) → 问题陈述 → 解决方案 → 工作流程 → 技术实现 → 界面设计 → 预算 → 团队

这明显不符合 Spark Program 申请模板的标准格式,请务必将相关内容整理后置于同一章节。

2. 缺少独立的“交付物”和“如何验证”章节。

目前提案没有独立且完整的 Deliverables(交付物) 和 How to Verify(验证方式)章节;社区和委员会成员目前都很难直观了解该项目的交付物有哪些,以及无从了解如何直接有效地以非代码审查的方式验证你的工作。

建议:综合前两个问题,按照 Spark Program Mini-Grant 模板 重新组织章节。

3. 预算额度 $1,500 超出纯技术类项目 $1,000 标准上限。

根据 Spark Program 资助方案,常规项目资助上限为 $1,000,特殊项目经委员会审议后可提高至 $2,000。目前你的提案申请 $1,500,但没有说明为什么这个纯技术类项目需要突破 $1,000 的标准线。

建议:将预算调整至 $1,000 以内;

4. 提案未回应"CKB 上是否存在女巫攻击问题"这一核心前提。

提案在"问题陈述"部分假设了"空投平台难以过滤女巫钱包"和"DEX 难以识别人类与机器人"等场景。但需要指出的是:CKB 是一条以记录重要数据为目的的链,任何个体在使用 CKB 保存重要数据时都需支付对应的 Cell 占用成本(State Rent)。这与那些依赖低成本的账户模型的公链有本质区别——在 CKB 上,"批量创建低成本钱包"本身就需要持续支付存储成本,天然提高了女巫攻击的门槛。除非"女巫钱包"有破坏 Fiber Network 中交易链路的能力,否则在 CKB 生态中,"区分人类与非人类钱包"这一需求的真实性和紧迫性似乎有待论证。

建议:在问题陈述中明确说明,为什么 CKB 生态需要这个工具——你的目标用户是谁(钱包开发商?DEX?审计团队?),他们在什么具体场景下面临"无法识别人类 vs 机器人"的痛点?这个痛点是否值得通过外部工具来解决,而非通过现有数据即可简单判断?

以上就是我梳理的几个关键问题,供你参考。在你调整后我会提请委员会尽快进入正式评审,相信修改后的提案会让评审过程顺畅很多。

期待你的更新版本。
祝好,
行天

2 Likes

Hi @xingtianchunyan,

Thank you again for the detailed feedback and guidance.

I have now reorganized and resubmitted the proposal according to the Spark Program Mini-Grant template. In the updated version, I have:

  • Restructured the entire proposal to follow the correct Spark format
  • Added clearer and more testable “How to Verify” sections
  • Adjusted the budget to strictly comply with the $1,000 cap, with a transparent breakdown between infrastructure, dataset preparation, and developer time
  • Refined the Problem Statement and CKB relevance section to better reflect real ecosystem needs and clearly define target users and use cases within CKB
  • Removed ambiguity around Sybil framing and focused the scope on wallet behavior analytics and classification

The revised proposal is intentionally scoped as a lightweight, verifiable prototype that can be delivered within the 6-week timeline, with clear outputs including an API, dashboard, dataset, and open-source repository.

Please let me know if there are any remaining gaps before formal committee review. I’m happy to refine further if needed.

Best regards,
Fadhil

3 Likes