Spark Program | Corven — Cloud Development Platform for the CKB Ecosystem

Spark Program | Corven – Cloud Development Infrastructure for CKB

Tag: Spark-Program

1. Project Overview

Project Name

Corven

One-Sentence Summary

Corven is a browser-based cloud development platform that enables developers to build, test, and debug CKB smart contracts without installing local development tools.

Project Type

Developer Tool

2. Team Profile

Core Member

Jimleston Osoi — Founder & Full-Stack Developer

Responsible for system architecture, backend services, cloud infrastructure, frontend development, and DevOps.

Background

  • Full-stack software engineer
  • CKBuilder Program participant
  • Experience building NestJS microservices, cloud platforms, Docker-based systems, and React/Next.js applications
  • Experience developing Rust smart contracts and experimenting with the CKB toolchain and Fiber Network

Links

GitHub: https://github.com/lestonEth/corven-platform
LinkedIn: https://linked/in/jimlestonosoi
Discord: leston2640
Email: [email protected]
Telegram: @lest_ton

3. Project Background

Developing on CKB requires developers to install and configure multiple tools before writing their first smart contract. A typical setup includes Rust, Cargo, Docker, the RISC-V target, CKB tooling, and other platform-specific dependencies. Installation issues and environment inconsistencies create a significant barrier for new developers.

During my participation in the CKBuilder Program, I experienced these challenges firsthand. Considerable time was spent configuring development environments instead of building applications.

While cloud IDEs such as GitHub Codespaces and Gitpod simplify general software development, they are not designed around CKB workflows. They lack built-in support for CKB project templates, Rust contract compilation, testing, and future Fiber development.

Corven addresses this problem by providing a cloud-native development environment specifically designed for the CKB ecosystem.

4. Solution

Corven provisions an isolated cloud workspace for every developer, preconfigured with the complete CKB development toolchain.

Developers can:

  • Create CKB projects from templates
  • Edit code in a browser-based IDE
  • Compile Rust smart contracts
  • Run tests
  • Access an integrated terminal
  • Save workspaces automatically
  • Resume development from any device

Future versions will introduce Fiber node deployment, transaction simulation, integrated debugging, and AI-assisted development.

Unlike traditional cloud IDEs, Corven is designed around CKB development workflows rather than general software development.

5. Technical Approach

Technology Stack

Frontend - Next.js, TailwindCS, Monaco Editor
Backend - NestJS, PostgreSQL, Prisma, Redis
Infrastructure - Docker, MinIO, JWT Authentication, Redis Streams, Kubernetes (future)

Architecture

Corven follows a microservice architecture consisting of:

  • API Gateway
  • Authentication Service
  • Workspace Service
  • Runtime Service
  • Storage Service

When a developer creates a workspace, the request is authenticated, queued, and processed by the Runtime Service, which provisions an isolated Docker container with the required CKB toolchain. Workspace metadata is stored in PostgreSQL, while project files persist through mounted storage volumes.

This architecture enables secure multi-user isolation, scalable workspace provisioning, and persistent development sessions.

Technical Challenges

  • Secure multi-tenant container isolation
  • Fast workspace provisioning
  • Persistent developer sessions
  • Browser-based terminal streaming
  • Integration of the CKB toolchain into cloud workspaces

The platform supports English as its primary language.

6. To-Do List

Week 1 – Backend Foundation & Authentication

Budget: USD 600

The first week focuses on establishing the core backend infrastructure that all other platform components depend on. This includes finalizing the microservice architecture, implementing JWT-based authentication and user management, developing the Workspace Service responsible for workspace lifecycle management, and configuring PostgreSQL and Redis for persistent storage and caching. Communication between backend services will also be established to support future runtime orchestration.

Milestone: Developers can authenticate and create workspace records through a functional backend foundation.


Week 2 – Cloud Runtime & Workspace Provisioning

Budget: USD 600

The second week focuses on the cloud execution environment. The Runtime Service will be implemented to provision isolated Docker workspaces preconfigured with the CKB development toolchain. Persistent storage will be configured using Docker volumes, while WebSocket-based terminal support will provide real-time command execution. Workspace initialization from predefined project templates will also be completed.

Milestone: Developers can launch isolated cloud workspaces with persistent storage and an integrated terminal.


Week 3 – Browser IDE & CKB Development Workflow

Budget: USD 500

Development during the third week will focus on the browser-based development experience. Monaco Editor will be integrated alongside a file explorer, enabling developers to edit project files directly in the browser. The CKB toolchain will be integrated into workspace containers, allowing Rust smart contract compilation, test execution, and real-time build log streaming without requiring any local installation.

Milestone: Developers can create, edit, build, and test CKB smart contracts entirely from their browser.


Week 4 – Testing, Documentation & Public Release

Budget: USD 300

The final week will focus on platform stabilization and public release. End-to-end testing, performance optimization, and bug fixing will be completed to ensure a reliable user experience. Comprehensive documentation covering platform usage and developer onboarding will be published, followed by deployment of a publicly accessible demo and a demonstration video showcasing the platform’s capabilities.

Milestone: A publicly accessible MVP of Corven is available, enabling developers to build and test CKB applications entirely through the browser without local environment setup.

7. Required Funding

Total Requested

USD 2,000

Corven combines frontend development, backend microservices, cloud infrastructure, container orchestration, and CKB-specific tooling. The requested funding supports implementation of a production-ready MVP rather than a standalone web application.

Category Activities Amount (USD)
Backend Services Develop API Gateway, Authentication Service, Workspace Service, Runtime Service, database integration, and service communication. 700
Frontend & Browser IDE Build the browser interface, Monaco Editor integration, file explorer, workspace management UI, and terminal interface. 500
Cloud Infrastructure Docker workspace provisioning, persistent storage, runtime orchestration, deployment environment, and infrastructure configuration. 350
Documentation & Developer Guides User documentation, setup guides, API documentation, tutorials, and architecture documentation. 150
Testing & Public Deployment End-to-end testing, performance optimization, bug fixing, public demo deployment, and demonstration video. 300
Total Requested 2,000

8. Deliverables & How to Verify

Deliverables

At the end of the funding period, Corven will be delivered as an open-source cloud development platform for the CKB ecosystem. Deliverables include a public GitHub repository, a browser-based IDE with Monaco Editor, Docker-based cloud workspaces, CKB project templates, an integrated terminal, documentation, a public demo, and a demonstration video.

How to Verify

The committee can verify the project by accessing the public demo through a web browser. A successful verification consists of creating a workspace, generating a CKB project, editing code, compiling a Rust smart contract, running tests, and confirming that the workspace persists across sessions. All verification steps can be completed without reviewing the source code or installing local dependencies.

9. Current State vs. Funded Work

Current State

Corven has an existing prototype with the core backend architecture in place, including the API Gateway, Authentication Service, Workspace Service, Runtime Service, Docker integration, and database connectivity. Initial research on integrating the CKB development toolchain has also been completed.

Funded Work

The Spark Program funding will transform the prototype into a production-ready platform by delivering a complete browser-based IDE, persistent cloud workspaces, integrated CKB development tools, project templates, documentation, and a publicly accessible demo for the CKB community.

10. CKB Alignment

Corven is built specifically to improve the developer experience within the CKB ecosystem by eliminating the complexity of local environment setup. The platform provides preconfigured cloud workspaces with the CKB development toolchain, enabling developers to create, compile, test, and debug Rust smart contracts directly from a browser.

The initial release focuses on CKB smart contract development, project templates, and integrated build workflows. Future releases will expand support for Fiber development through one-click node provisioning, transaction simulation, and developer debugging tools. By lowering onboarding barriers and reducing setup time, Corven aims to make building on CKB faster, more accessible, and more productive for both new and experienced developers.

2 Likes

Hi @lestonEth, thanks for submitting the Corven — Cloud Development Platform for the CKB Ecosystem proposal.
Before we move to committee review, I’d like to share some personal pre-review feedback (not a committee decision) to help strengthen your proposal:

1. Format & Completeness (checked against the official proposal template):

  • Required Funding & Funding Breakdown: Missing the required sub-headings “A. Required Funding” and “B. Funding Breakdown”. The explanation for exceeding $1,000 is too brief; a detailed justification is needed.

  • Deliverables + How to Verify: Deliverables listed without specific acceptance criteria. Verification steps lack expected outputs, environment requirements, and cost control notes.

2. Funding Standards:

  • Project type: Pure technical (Developer Tool). Requested $2,000 exceeds the standard cap of $1,000. The brief justification is insufficient. Recommendation: reduce to $1,000 or below with a scaled scope, or provide a detailed argument for a special/high-difficulty tier (requires full committee consensus). Also, the weekly budget ($600/$600/$500/$300) does not match the category breakdown ($700/$500/$350/$150/$300), causing confusion.

3. Content Logic:

  • The 4-week timeline for a solo developer to reach production-ready MVP is optimistic; testing and documentation may be compromised.

  • Verification steps need more detail: expected outputs (e.g., compilation success message), browser requirements, login needs.

  • Open-source license not specified (required by Spark Program).

Suggestions:

  1. Adjust the budget to $1,000 or less and trim scope accordingly, or add a thorough justification for a higher amount.
  2. Revise §8 with clear acceptance criteria for each deliverable and concrete verification steps (expected outputs, environment).
  3. Align the weekly budget with the category breakdown or explain the relationship.
  4. Extend the timeline to 6-8 weeks or reduce scope to ensure quality.
  5. Specify an open-source license (e.g., MIT).

Please revise and reply in this thread. Looking forward to the updated version!

Best,
xingtian