Spark Program Proposal: Corven cloud-native IDE

Corven: A Browser-Based IDE for Building on CKB and Fiber Network

Proposal Update — Revised Budget, Committee Feedback and Approval-Dependent Timeline

Corven requests $520 to add Fiber Network tooling to its working browser-based CKB IDE and test it with Web3 developer clubs across Kenya. The first community session was conducted remotely because travel funding was unavailable, so no travel or venue costs are claimed for it. The remaining two sessions are planned as physical events in Nairobi and Thika, and the budget has been reduced to cover only the essential logistics for those two sessions.

To accommodate the committee’s review and approval process, Week 1 records the initial engagement already undertaken, while Weeks 2–5 are scheduled relative to the date the proposal is approved. The remaining implementation work will begin after approval, with the final deliverables due by the end of Week 5.

Project Name

Corven: a browser-based IDE for building on CKB and Fiber Network.

Team / Individual Profile

  • Name: Jimleston Osoi, Software Engineer
  • Background: Backend developer and data engineer with 5+ years of experience in Node.js, TypeScript, React, PostgreSQL, Redis and AWS. Blockchain experience in Solidity and Go on EVM chains, plus prior work in the Nervos CKB ecosystem through the CKBuilder Program.
  • GitHub: lestonEth
  • Website: https://corvanide.space/
  • Contact: Telegram @lest_ton

Project Description

Problem. Building on CKB, and on Fiber Network in particular, means setting up a local toolchain, running a devnet and nodes, and configuring channels before writing a single line of application code. For new developers, especially students in African Web3 clubs with limited hardware and unreliable internet, this setup is a significant barrier to entry. Many give up before they ever build.

Solution. Corven is a cloud-native IDE that runs entirely in the browser. Developers open a link and get a ready workspace with a terminal, a private CKB devnet and contract templates, with no local setup. This phase adds Fiber Network to that workspace: running Fiber nodes, opening channels and sending payments from the browser, so new developers can try Fiber in minutes.

Progress so far — CKB foundation

  • NestJS microservice backend covering API gateway, authentication, workspace, runtime, file and terminal services, using PostgreSQL and Redis.
  • Sign-in with a CKB wallet signature, JWT with refresh-token rotation, and Redis-backed rate limiting.
  • Workspaces that open in seconds from pre-built templates, with scheduling across multiple servers and a shared Rust build cache.
  • In-browser editor, terminal, and build and test panels; idle workspaces stop automatically to reduce hosting costs.
  • A private CKB devnet for every workspace, started on demand.
  • Contract templates with tests: Hello World, a fungible token (sUDT) and a time lock.
  • One-click deployment to the devnet, or testnet deployment using the developer’s own wallet, with upgradeable Type ID deployments.
  • Transaction debugger with cycle counts and plain-language contract errors.
  • Devnet accounts, a cell explorer, a transaction builder and Molecule bindings.
  • Built-in browser to preview dApp frontends running in the workspace.

Fiber work in progress: A Fiber playground that runs three Fiber nodes (fnn v0.9.1) on the workspace devnet. In local tests, the nodes open channels, route a payment through a middle node and close cooperatively. Packaging this into the IDE with a visual interface is the first build task of this phase.

Why now. The CKB foundation works. Fiber is the missing piece for our target users, and testing with real developers will show what they need from it. This phase ships the Fiber tooling and tests it in hands-on sessions with Web3 clubs in Kenya.

Website Status and Operational Readiness

The committee could not access the previously listed website. The public deployment had been taken offline to avoid hosting costs while the proposal was pending, and the project has since moved to a new domain: https://corvanide.space/.

The project is operational: the full CKB foundation, including workspaces, devnet, contract templates, transaction debugger and cell explorer, runs locally and has been demonstrated to testers.

To resolve this before re-review, we will, no later than three days after resubmission and subject to available resources:

  • Bring up a stable public instance at https://corvanide.space/ with uptime monitoring.
  • Publish a short status update confirming the deployment URL and the checks completed.

Expected Deliverables

By the end of Week 5, measured from the approval-dependent implementation schedule, the following outputs will be produced and published. Each deliverable is measurable and verifiable.

# Deliverable Measurable output Publication location
1 Fiber playground in Corven A working browser-based Fiber playground with three Fiber nodes (fnn v0.9.1) per workspace, supporting channel opening, invoice creation and payment, and a multi-hop payment routed through a middle node. Verified by a recorded end-to-end test. Live Corven IDE at https://corvanide.space/
2 Fiber starter templates Two to three runnable Fiber starter templates, each with a README, that a new developer can open and run in the browser in under five minutes. Corven template gallery and public repository
3 Getting-started guide One written guide of at least 1,000 words covering workspace setup, starting Fiber nodes, opening a channel, sending a payment and deploying a template. Public repository, linked from Corven
4 Open-source code repository Public repository under an MIT or Apache-2.0 license containing the Fiber tooling, templates and guide produced in this phase. GitHub
5 Stable public deployment A public Corven instance that remains online throughout the project period and passes a load test of 15–20 concurrent workspaces. https://corvanide.space/
6 Three community testing sessions Three sessions associated with the Kisumu, Nairobi and Thika developer communities, with at least 40 participants in total. The first session was held remotely alongside the Umoja Verse Kisumu event; the remaining two sessions are planned in person. Session records and attendance data in the testing report
7 User testing report One report containing participant numbers per session, key feedback themes, bugs found and fixes shipped. Nervos Talk and public repository
8 Demo video One 3–5 minute video showing the Fiber playground in use and improvements made after each testing session. YouTube or IPFS, linked on Nervos Talk
9 Final completion report One report with a transparent, line-item funding usage breakdown against the $520 budget, plus a summary of deliverables 1–8 and their status. Nervos Talk

Verification: Each deliverable will be linked in the final completion report so the committee can independently confirm that it was produced. Deliverables 1–5 are functional artifacts that can be tested directly; deliverables 6–9 are documented evidence of testing and spending.

Testing Plan

The first session was conducted remotely because there were insufficient funds for travel to Kisumu. It was coordinated alongside the Kisumu event organized by Umoja Verse so the engagement could proceed rather than be postponed. No costs are claimed for this session.

The remaining two sessions are planned as physical sessions in Nairobi and Thika, funded by the reduced session logistics budget below. If funding or venue arrangements require another change, the committee will be informed and the delivery format agreed before the sessions.

Planned format for the remaining physical sessions

Each session will last approximately three hours.

Time Activity
0:00–0:20 Introduction to CKB and Fiber, including what participants will build
0:20–0:40 Guided signup: participants open Corven in the browser, create a workspace and start a devnet
0:40–1:30 Hands-on Lab A (CKB): Compile and deploy a contract template, then inspect the transaction in the debugger
1:30–2:15 Hands-on Lab B (Fiber): Start Fiber nodes, open a channel, create an invoice and send a payment, progressing to multi-hop payments as the implementation becomes available
2:15–2:45 Structured feedback collection through a survey and short group discussion
2:45–3:00 Wrap-up, next steps and guidance on continuing to use Corven

Feedback collection

  • Pre-session baseline survey: A five-question Google Form covering experience level, previous CKB/Fiber exposure, device and connection type.
  • Post-session survey: A ten-question Google Form combining 1–5 rating scales and open-text responses. Topics include:
    • Time to first working workspace.
    • Time to first Fiber payment.
    • Ease of use of the Fiber playground.
    • Clarity of the getting-started guide.
    • Biggest blocker encountered.
    • One feature the participant would add.
    • Whether the participant would use Corven again.
    • Whether the participant would recommend it to a club member.
  • Bug log: Facilitators record reproduction steps, expected versus actual behavior, and severity.
  • Attendance log: Record participant names or handles, club, device type, and whether Labs A and B were completed.
  • Optional interviews: Three to five participants per session, with interviews lasting approximately five minutes each.

Evidence and reporting

  • Raw survey exports in CSV format and the bug log will be published in the public repository alongside the testing report.
  • The testing report will include participant counts per session, lab completion rates, aggregated survey scores, a prioritized bug list with fix status, and participant quotations where consent has been provided.
  • Screenshots and short clips from each session will be included in the demo video.

Targets

  • More than 40 participants across the three sessions.
  • At least 70% of attendees completing Lab A.
  • At least 50% of attendees completing Lab B.
  • At least 80% of attendees submitting the post-session survey.

Completion rates will use session attendees as the denominator, and the report will show both counts and percentages.

Acceptance Criteria and Evidence Commitments

We acknowledge that if the final report, test data and community feedback do not meet the committee’s requirements, the project may not be approved for completion. To make the results verifiable, we commit to the following:

  1. Publish raw evidence, not just summaries:
    • Anonymized post-session survey exports in CSV format.
    • Bug log in CSV or Markdown.
    • Attendance logs anonymized to initials or handles.
    • Pre-session baseline survey exports in CSV format.
  2. Traceability: All claims in the final report will link to a specific evidence file or source.
  3. Deployment availability: The public deployment will remain online for at least 30 days after the final report so the committee can independently test the deliverables.
  4. Real demonstration: The demo video will show unedited, real-time use of the Fiber playground rather than a scripted mockup.
  5. Honest reporting: If targets are not met, such as fewer than 40 participants or incomplete labs, we will report the shortfall and explain the cause rather than change the numbers after the fact.
  6. Weekly updates: We will publish weekly progress updates on Nervos Talk during the revised implementation period so the committee can track progress and raise concerns early.

Required Funding

Total requested: $520, equivalent in CKB.

Item Purpose Amount (USD)
Cloud hosting and deployment Servers to run IDE workspaces, devnets and Fiber nodes during the project period $220
Infrastructure Managed PostgreSQL, Redis, storage, domain and SSL, and testnet node $140
Session logistics (Nairobi and Thika) Travel, participant mobile data and printed materials for the two remaining in-person sessions. See the breakdown below. $160
Total $520

Session logistics breakdown

Session Line item Amount (USD)
Session 1 (Kisumu, remote) No travel or venue costs were incurred, so none are claimed $0
Session 2 (Nairobi) Local transport for facilitators and equipment $15
Mobile data support for participants (about 15 attendees) $30
Printed getting-started guides and lab handouts $20
Nairobi subtotal $65
Session 3 (Thika, MKU) Nairobi–Thika round-trip transport for two facilitators $40
Local transfers in Thika $5
Mobile data support for participants (about 15 attendees) $30
Printed getting-started guides and lab handouts $20
Thika subtotal $95
Session logistics total $160

Actual spending for each session will be reported line by line in the final completion report, with receipts where available. Any unspent funds will be reported as unspent rather than reallocated without the committee’s approval.

Estimated Completion Time

Week 1 retains the dates of the initial engagement already undertaken. Weeks 2–5 will be scheduled relative to the date the proposal is approved:

  • Week 1: Initial engagement already undertaken, retaining its original dates.
  • Week 2: First week after approval.
  • Week 3: Second week after approval.
  • Week 4: Third week after approval.
  • Week 5: Fourth week after approval.

Activities originally planned immediately after the first session have been moved into the first week after approval, with subsequent technical implementation, community testing and reporting activities shifted accordingly. The remaining implementation schedule will follow the actual approval date rather than a fixed calendar deadline.

Revised To-do List

Week 1 (12–18 October): First session and initial engagement

  • Session 1 — Kisumu: Community engagement conducted remotely alongside the Umoja Verse Kisumu event because travel funding was unavailable. The session focused on the existing CKB workspace, devnet and contract templates. No costs claimed. (Deliverable 6)
  • Share the available workshop photo gallery and video as supporting evidence.
  • Organize available feedback and identify follow-up questions and issues. (Deliverable 7)

Week 2 (first week after approval): Proposal revision and preparation

  • Finalize the reduced budget and scope in line with the Spark Program committee’s feedback.
  • Confirm the scope and timing of the remaining physical sessions with the Nairobi and Thika developer communities, subject to venue availability.
  • Prepare the technical checklist, participant instructions, survey forms and bug-log template.
  • Review public deployment status and plan the required monitoring and load tests.
  • Publish a progress update on Nervos Talk, distinguishing completed work from pending work. (Acceptance criterion 6)

Week 3 (second week after approval): Technical implementation and Nairobi session

  • Package and integrate the Fiber playground into the IDE, including the three-node workflow, and address priority issues from the initial engagement. (Deliverable 1)
  • Deploy or verify the stable public instance with monitoring and run the planned load test for 15–20 concurrent workspaces. (Deliverable 5)
  • Session 2 — Nairobi: Hold the planned in-person session with the Nairobi Web3 developer community, subject to venue confirmation. (Deliverable 6)
  • Build or refine two to three Fiber starter templates and update the getting-started guide based on test findings. (Deliverables 2 and 3)
  • Publish the weekly progress update on Nervos Talk. (Acceptance criterion 6)

Week 4 (third week after approval): Thika session and iteration

  • Fix issues found during the Nairobi session and verify the Fiber playground’s channel, invoice and payment workflows. (Deliverables 1 and 7)
  • Session 3 — Thika: Hold the planned in-person session at Mount Kenya University (MKU), focused on the Fiber playground and starter templates, subject to venue confirmation. (Deliverable 6)
  • Address issues from Thika, complete the user testing report draft and publish the weekly progress update. (Deliverable 7 and acceptance criterion 6)
  • Consolidate attendance, lab completion and survey data.

Week 5 (fourth week after approval): Final validation and reporting

  • Finalize the public repository, getting-started guide, starter templates and test evidence. (Deliverables 2, 3 and 4)
  • Record and publish the 3–5 minute demo video showing real use of the Fiber playground and fixes made following testing. (Deliverable 8)
  • Finalize the user testing report, including participant numbers, survey results, lab completion rates, bugs found and fixes shipped. (Deliverable 7)
  • Publish the completion report with the line-item funding usage breakdown against the $520 budget and status of deliverables 1–8. (Deliverable 9)

Relevance to the CKB Ecosystem

  • Meets a real ecosystem need: Fiber is CKB’s payment channel network, and growing it depends on more developers building apps on it. Corven removes the setup barrier so new developers can run Fiber nodes and send their first payment from a browser.
  • Grows the developer base in Africa: Testing directly with Kenyan Web3 clubs brings new builders into CKB and creates a feedback loop from an underserved region.
  • Web5 alignment: Corven combines familiar Web2 developer tooling with Web3 infrastructure, following a user-centric process of building, testing with real users and iterating.
  • Open source: All code will be public so other CKB builders can reuse and extend it.
7 Likes

Hi @lestonEth,

Thank you for your continued interest in the Spark Program and for submitting the Corven cloud-native IDE proposal.

After review by the Spark Program committee, your proposal has been assigned a status of Pending. This is not a rejection, but an invitation to revise and resubmit.

The committee acknowledges the value of your work — a browser-based IDE that lowers the barrier for new developers to build on CKB is genuinely useful, and the progress you’ve made on the CKB foundation (workspace management, devnet provisioning, contract templates, transaction debugger) is impressive.

Main Revision Recommendations:

  1. Deliverables clarification: Please explicitly state what the expected deliverables and outputs of this phase are. The committee needs a clear, measurable list of what will be produced by the end of the 4-week period.

  2. Website accessibility: The committee was unable to access the provided website (corvan.space). This raises concerns about whether the project is actually operational and can support the proposed activities. Please confirm the website’s status and provide a working link, or explain the current situation.

  3. Acceptance criteria: The committee would like to be clear upfront that if the final report, test data, and community feedback do not meet the committee’s requirements, the project will not be approved for completion. Please ensure your proposal includes concrete — and verifiable — plans for how you will collect and present this evidence.

  4. Testing plan: Since this phase includes hands-on testing with Web3 developer clubs in Kenya, please clarify how the sessions will be conducted and what specific feedback you plan to collect from participants.

Regarding the website being down — if there are hosting issues or recent changes, please let us know. Please revise and resubmit based on the feedback above. We will arrange a new round of review as soon as possible.

Best regards,
xingtian
On behalf of the Spark Program Committee

1 Like

[Proposal Update]

Hi @xingtianchunyan,thanks to you and the committee for the review.

I’ve revised and resubmitted the proposal to address all four points:

  1. Deliverables — Added a measurable deliverables table (9 outputs, each with a specific metric and publication location), cross-referenced with the to-do list.

  2. Website — Old domain was taken offline to save hosting costs while pending; project moved to https://corvanide.space/.

  3. Acceptance criteria — Added 6 explicit commitments: raw evidence published, 30-day post-report uptime, unedited demo video, honest shortfall reporting. I accept that missing the committee’s requirements means no completion approval.

  4. Testing plan — Added a 3-hour session agenda, 5 feedback instruments, and targets (40+ participants, 70%/50% lab completion, 80% survey response).

Best regards,
lestonEth

1 Like

Corven Spark Program — Week 1 Progress Report

Project: Corven: A Browser-Based IDE for Building on CKB and Fiber Network
Reporting Period: 12–16 October 2026
Status: Week 1 activities underway
Project Website: https://corvanide.space/
GitHub: GitHub - corvenide/corven-fronted: Corven – Cloud Development Infrastructure for CKB · GitHub

1. Overview

During Week 1, I conducted a live Google Meet session to demonstrate the Corven IDE platform to participants associated with the Kisumu developer outreach event. The session lasted approximately one hour and focused on introducing the platform, demonstrating its existing capabilities, and gathering initial feedback on areas that need improvement.

The demonstration provided an opportunity to show how Corven aims to simplify CKB development by bringing the development environment, workspace tools, and blockchain development workflow into the browser.

The feedback received highlighted several improvements that could make the platform more accessible to new developers, improve wallet connectivity, and support community contributions.

A Google Form will also be provided to participants to record attendance and collect structured feedback. The responses will support the project’s user-testing documentation and subsequent progress reports.

2. Activities Completed

Live platform demonstration

A one-hour Google Meet session was conducted as part of the Kisumu outreach activities.

The session introduced Corven IDE, demonstrated the platform, and provided an opportunity for participants to share their experiences, identify usability issues, and suggest additional features.

The demonstration was an initial engagement activity rather than a completed three-hour hands-on testing session. Further structured testing and feedback collection will be conducted as the project progresses.

Initial feedback collection

The demonstration generated six main areas of feedback:

  1. Social login support for wallet connectivity.

  2. External wallet connectivity in the installed web app.

  3. Functionality of the built-in browser tool.

  4. A guided first-time user tutorial.

  5. In-platform video tutorials.

  6. Open-source access and community contributions.

These observations will help inform the project’s development priorities and the design of subsequent hands-on testing sessions.

3. Feedback Received and Planned Responses

3.1 Social login through Corven Connect

Feedback: Participants recommended adding social login options to simplify the wallet connection and onboarding experience.

Planned response: Investigate integration of Corven Connect, a wallet-connectivity tool currently being developed by Corven on top of the CCC wallet-connect infrastructure. The intended direction is to support a more accessible onboarding experience, including social login where supported by the integration.

Status: Feedback received; integration and implementation remain pending.

3.2 External wallet connectivity in the installed web app

Feedback: The installed version of the web app does not connect successfully with external wallets such as MetaMask.

Planned response: Investigate wallet-provider detection, browser compatibility, and connection handling in the installed application. The implementation will need to distinguish between supported wallet providers and browser or installation limitations.

Status: Issue identified; investigation and testing required.

3.3 Built-in browser tool

Feedback: The browser tool within Corven IDE does not work as expected.

Planned response: Investigate the browser preview workflow, workspace connectivity, and any related routing or runtime issues. The goal is to ensure developers can preview and interact with applications running inside their workspaces.

Status: Issue identified; debugging and validation required.

3.4 First-time user tutorial

Feedback: New users would benefit from a guided introduction explaining how to use the platform.

Planned response: Develop an onboarding tutorial covering the essential workflow, from opening a workspace to using the terminal, working with contract templates, building and testing contracts, and deploying to the available development environment.

Status: Planned improvement.

3.5 Video guides within Corven IDE

Feedback: Participants recommended adding video tutorials directly within the platform.

Planned response: Prepare short instructional videos demonstrating important workflows, including workspace creation, contract development, debugging, deployment, and relevant Fiber Network features as they become available.

Status: Planned improvement.

3.6 Open-source contributions

Feedback: Participants recommended making the project openly available to encourage community participation and contributions.

Planned response: Prepare the relevant repository, documentation, licensing, and contribution guidelines so developers can inspect the codebase, report issues, and contribute improvements. The publication process will also clarify which components and configurations are ready for public contribution.

Status: Planned improvement; repository and contribution readiness will be verified before the public release is announced.

4. Attendance and Structured Feedback Collection

A Google Form will be shared with participants to document attendance and gather structured feedback following the demonstration and subsequent testing sessions.

The form will capture relevant information such as:

  • Participant name or preferred handle.

  • Developer club or institution, where applicable.

  • Previous experience with CKB and blockchain development.

  • General feedback on the Corven IDE demonstration.

  • Usability issues encountered.

  • Suggested features and improvements.

  • Interest in participating in future testing sessions.

For reporting purposes, the form responses will be used to distinguish participants who attended the initial online demonstration from those who participate in future hands-on sessions.

The collected information will support attendance records, feedback analysis, and the final user-testing report. Any public release of survey data will be anonymized, and identifiable information or participant quotations will only be published where appropriate consent has been obtained.

Google Form: [Link to be added once the form is available]

5. Progress Against Project Deliverables

Deliverable Week 1 progress
1. Fiber playground Existing Fiber development work remains in progress; integration and verification are pending.
2. Fiber starter templates Planned for development and validation in the upcoming weeks.
3. Getting-started guide Initial user feedback has identified the need for clearer onboarding documentation.
4. Open-source repository Public contribution readiness and documentation are to be addressed.
5. Stable public deployment Deployment stability and the planned concurrent-workspace load test require verification.
6. Three hands-on testing sessions Initial one-hour online demonstration conducted; this is not counted as a completed full hands-on testing session.
7. User-testing report Initial qualitative feedback documented; structured attendance and survey collection is planned.
8. Demo video Planned for a later project stage.
9. Final completion report To be prepared at the end of the project, including deliverable verification and funding expenditure.

6. Priorities for Week 2

Based on the initial feedback and the project’s original timeline, the following activities will be prioritized:

  1. Investigate and address the built-in browser preview issue.

  2. Investigate external wallet connectivity in the installed web app.

  3. Assess the integration requirements for Corven Connect and social login.

  4. Begin implementing the first-time onboarding tutorial and plan the in-platform video guides.

  5. Prepare the repository and documentation for community contributions.

  6. Share the Google Form for attendance and structured feedback collection.

  7. Continue developing and integrating the Fiber playground and starter templates.

  8. Conduct further developer engagement and collect feedback to guide subsequent iterations.

Priorities may be adjusted according to the severity of identified issues and progress on the core Fiber deliverables.

7. Conclusion

Week 1 established an initial feedback loop between Corven and the developer community through a live Google Meet demonstration connected to the Kisumu outreach activity.

The feedback highlighted opportunities to improve onboarding, wallet connectivity, application previews, instructional resources, and open-source participation. These observations will inform the next development and testing activities.

The project will continue to document progress against the published deliverables and collect attendance and feedback evidence through a Google Form and subsequent hands-on sessions. The distinction between initial demonstrations and completed structured testing sessions will be maintained in project reporting.

Further updates will document implementation progress, testing outcomes, and any changes to the project timeline.

Submitted by: Jimleston Osoi
Project: Corven IDE — Spark Program Proposal

GM @xingtianchunyan,

Here is the media evidence from the CKB Kisumu Workshop 2026, documenting the event and community engagement activities.

  • Workshop photo gallery:
  • Workshop video:

The video highlights Corven IDE’s community engagement and efforts to make development on Nervos CKB more accessible.

I’ll also share the attendance records and structured feedback collected through the Google Form once they are available.

Thank you.

1 Like

Hello @lestonEth,

Thank you for continuing to follow the Spark Program and for keeping us updated on the latest progress of the Corven proposal.

After review by the Spark Program committee, your proposal’s status will remain Pending, and they would like you to provide explanations regarding the following two issues.

  1. Scope of coverage for costs related to remote meetings: Your proposal initially included expenses for travel and mobile data charges related to the offline meeting of Kenya’s Web3 Developers Club. Given that the first meeting is now planned to be held remotely, please confirm whether these travel and mobile data costs are still covered by the budget request, and explain how these costs will be adjusted with a remote format.
  2. Feasibility of the proposed goals: Given that meetings will now be held primarily remotely, please confirm whether the data-related goals outlined in the proposal (more than 40 participants in total across 3 meetings; at least 70% completing Experiment A and 50% completing Experiment B; at least 80% filling out the post-meeting survey) can still be achieved. If adjustments to the goals are necessary, please specify what the revised goals should be.

Please make the necessary revisions based on the feedback above and submit it again. We will arrange a new round of evaluation as soon as possible. Additionally, if you find it helpful, the committee is also happy to review your remote meeting plan and assist in coordinating everyone’s expectations before you resubmit it.

We look forward to receiving your reply.

Best,
xingtian
On behalf of the Spark Program Committee

2 Likes

GM @xingtianchunyan,

Thank you to you and the Spark Program Committee for reviewing the Corven proposal and providing an opportunity to clarify these concerns.

I would like to clarify that the decision to hold the first session remotely was made due to the lack of funds available to facilitate my travel to the event location in Kisumu. Rather than postpone or cancel the planned engagement, I decided to proceed remotely and coordinate the session alongside the Kisumu event organized by Umoja Verse. This allowed the community engagement activities to move forward despite the logistical limitations.

1. Scope of coverage for remote meetings and physical events

The original proposal was designed around physical community engagement sessions. The first session was conducted remotely as an adjustment to the available resources, not as a change to the overall implementation plan.

With the requested grant funding, I intend to hold the subsequent planned meetings physically, as initially proposed. The funding would help facilitate travel to the event locations and provide necessary mobile data support for participants where applicable. These resources are important for enabling direct engagement, hands-on demonstrations, collaborative experimentation, and practical support for developers using Corven IDE.

I will revise the budget to distinguish between the costs associated with the first remote session and those required to facilitate the remaining physical meetings. Any expenses that are no longer applicable to the first session will be adjusted accordingly, while the necessary and justified costs for the planned physical activities will remain in the budget.

2. Feasibility of the proposed goals

I believe the original targets remain achievable, particularly if the remaining sessions are conducted physically as planned. In-person meetings will provide better opportunities for guided experimentation, troubleshooting, collaboration, and direct feedback from participants.

The proposed targets remain:

  • More than 40 participants in total across the three meetings.

  • At least 70% of participants completing Experiment A.

  • At least 50% of participants completing Experiment B.

  • At least 80% of participants completing the post-meeting survey.

I will track attendance, experiment completion, and survey submissions to document progress against these targets. I will also use the feedback collected to assess Corven IDE’s usability and identify areas for improvement.

The remote first session demonstrates my commitment to maintaining progress even when logistical challenges arise. However, the remaining physical sessions would benefit from the requested funding, which would enable implementation closer to the original proposal.

I will update the proposal and budget to reflect this clarification and ensure that the implementation plan, costs, and targets are aligned.

I’ve updated the proposal to clarify the budget and travel arrangements, retain the testing targets, and make Weeks 2–5 dependent on the approval date while keeping Week 1 unchanged.

The revised proposal is ready for review. Thank you!

Hello @lestonEth,

Thank you for your continued interest in the Spark Program and for revising the Corven proposal.

Following a review by the Spark Program Committee, your proposal remains pending.

The committee noted that your proposal mentions a budget adjustment, but we did not identify any clear changes in the recent revisions when reviewing the record. Before moving the proposal forward, we would therefore like you to confirm the specific details of the budget adjustment.

Please revise and resubmit your proposal based on this feedback. We’ll arrange another review as soon as possible.

Best,
xingtian
On behalf of the Spark Program Committee

Hello @xingtianchunyan,

Thank you and the Spark Program Committee for the review. You’re right that the previous revision did not make the budget change clear. I have now updated the proposal post with an explicit, itemized adjustment. The details are below.

Summary of the budget adjustment

The total request is reduced from $600 to $520, a reduction of $80.

The only line that changed is session logistics. Session 1 (Kisumu) was held remotely and incurred no travel or venue costs, so nothing is claimed for it. The logistics budget now covers only the two remaining in-person sessions in Nairobi and Thika, and has been trimmed to essentials.

Item Previous (USD) Revised (USD) Change
Cloud hosting and deployment $220 $220 No change
Infrastructure $140 $140 No change
Session logistics $240 $160 −$80
Total $600 $520 −$80

Session logistics breakdown ($160)

Session Line item Amount (USD)
Session 1 (Kisumu, remote) No costs incurred, none claimed $0
Session 2 (Nairobi) Local transport for facilitators and equipment $15
Mobile data support for participants (about 15 attendees) $30
Printed getting-started guides and lab handouts $20
Nairobi subtotal $65
Session 3 (Thika, MKU) Nairobi–Thika round-trip transport for two facilitators $40
Local transfers in Thika $5
Mobile data support for participants (about 15 attendees) $30
Printed getting-started guides and lab handouts $20
Thika subtotal $95
Total $160

Other changes in the proposal to match the new budget

  • The opening summary now requests $520.
  • Deliverable 9 (final completion report) now reports spending against the $520 budget.
  • The Required Funding section includes the per-session breakdown above.
  • The Week 1 entry for the Kisumu session states that no costs are claimed.

All spending will be reported line by line in the final completion report, with receipts where available. Any unspent funds will be reported as unspent and will not be reallocated without the committee’s approval.

Deliverables, testing plan, targets and timeline are unchanged. Please let me know if the committee needs anything else before the next review.

Best,
Jimleston (lestonEth)

2 Likes

Hi @lestonEth (Jimleston),

I’m glad to share that the Spark Program Committee has approved your Corven proposal for a grant of 520 USD.

The committee recognizes the project’s value in lowering the barrier to entry for CKB and Fiber Network development. The revised budget and approval-dependent timeline are also noted, and the committee appreciates the effort to keep costs focused on the essential logistics for the two physical sessions.

Here are the next steps:

  1. Funding & Wallet Address

    • Total grant: 520 USD (approx. 445,205 CKB; $520 * 100% @0.001168 = 445,205 CKB)
    • First installment (20%, 104 USD, 89,041 CKB ): will be disbursed shortly
    • Please provide a CKB wallet address
    • Remaining 80% follows a flexible model
  2. Weekly Sync

    • Text-based updates on this thread at a fixed time each week, with committee feedback.
    • Or a brief live video call.
    • Please let us know your preference and a time that works for you.
  3. Proposal Content Lock

    • We’ll lock the current version of your proposal post as the reference baseline for deliverable verification.

Congratulations and looking forward to your next update!

Best,
xingtian
On behalf of the Spark Program Committee

cc: @zz_tovarishch , @yixiu.ckbfans.bit , @Hanssen

3 Likes

Hi @xingtianchunyan and the Spark Program Committee,

Thank you for the approval. I’m glad Corven’s goal came through.

  1. Wallet address: ckb1qyqwkl9ey453uwr4cxe4shwzwszxy02mkaysrjdkfp
  2. Weekly sync: I prefer a brief live call at [day, time, timezone]. I’ll also post a written text update on this thread every Sunday.
  3. Content lock: Agreed. I’ll report any shortfall against the locked version openly.

Thanks also to @zz_tovarishch, @yixiu.ckbfans.bit and @Hanssen for the review.

Best,
Jimleston

Hello, @lestonEth (Jimleston):

20% of the down payment has been paid.

Transaction hash: 0x1ad89f77bfa849bc6bffd670d3233693c567cbeaef9a5ebdef9269cee9474751

Please confirm receipt.

Additionally, you mentioned that you’d prefer to provide weekly updates via brief live calls, but it seems you weren’t able to enter the specific times correctly.

Best regards
xingtian
On behalf of the Spark Program Committee

1 Like

Hi @xingtianchunyan and the Spark Program Committee,

Thank you for sending the first installment. I confirm I have received the 20% payment (transaction 0x1ad89f77bfa849bc6bffd670d3233693c567cbeaef9a5ebdef9269cee9474751 ).

Sorry about the missing time in my earlier message. Here is the weekly sync schedule:

  • Live call: every Friday at 2:00 PM EST
  • Written update: every Sunday on this thread

Does Friday at 2:00 PM EST work for the committee? If another time suits you better, I’m happy to adjust.

Best,
Jimleston

1 Like

Hi @lestonEth ,

I understand that you’d like to meet online every Friday afternoon.

But I need to let you know about a recent change to our communication process: individual online calls have been consolidated into a Monthly Call, so we’re unable to schedule a recurring call every Friday.

I apologize for the mistake on my part. Also, to ensure you receive the invitation, please provide your email address and Discord account.

Best,
xingtian

Hi @xingtianchunyan,

Thanks for letting me know, and no problem at all. The Monthly Call works for me.

I’ll keep posting my written update on this thread every Sunday, so the committee still has weekly progress between calls.

Here are my details for the invitation:

Best,
Jimleston

1 Like