Gone in 60ms: Fiber Infrastructure Hackathon roundup!

General
,
1

The Gone in 60ms: Fiber Network Infrastructure Hackathon was a two-week builder sprint held from July 1 to July 15, 2026, designed to strengthen the infrastructure surrounding Fiber Network. This thread documents the projects that were developed and submitted over the course of the event.

Organized by the Nervos Community Catalyst, with support from the Fiber team, CKB DevRel teams, and the CKB Association, the hackathon is Part 1 of a broader Fiber builder initiative. Participants were asked to build tools, SDKs, and services that make Fiber easier to use, integrate, operate, or productise for wallets, merchants, node operators, and other developers, across three categories: Wallet and Payment UX Infrastructure, Node, Routing, Cross-Chain, and Diagnostics Infrastructure, and Merchant, Liquidity, LSP, and Multi-Asset Infrastructure.

Platform notes

As with previous events, the hackathon doubled as a live stress test for CKBoost, our quest-style campaign management platform. Running registration, project sharing, and submission entirely through CKBoost again surfaced a number of bugs and areas for improvement, which will feed into the platform’s continued development.

Submissions

We had around 85 registrations (roughly 100 total participants) and received 66 final project submissions across the three categories: 13 in Wallet and Payment UX, 32 in Node, Routing, Cross-Chain, and Diagnostics, and 21 in Merchant, Liquidity, LSP, and Multi-Asset. All submissions are fully open-sourced.

1. Wallet and Payment UX Infrastructure

  • CKB KeyWay: React SDK giving applications email-authenticated CKB accounts and Fiber payments, no CKB wallet or node management required.
  • Clasp: Pairing protocol, wallet policy engine, and allow-listed Fiber gateway that lets any application connect to a Fiber wallet with limited, revocable permissions.
  • Fiber Offers: Reusable payment infrastructure letting merchants and services publish signed, static Fiber payment offers.
  • Fiber Wallet UX Kit: Reusable browser wallet and payment-UX kit for CKB Fiber Network.
  • Fiber WebGL SDK: Unity package that runs a real Fiber payment node inside a WebGL build via WebAssembly, letting any Unity game send and receive CKB payments.
  • Fiberglass: Production-ready React SDK — hooks, components, and a context provider — giving wallets, merchants, and dApps drop-in Fiber payment UX.
  • FiberGuard Session: Scoped payment-intent gateway that lets a Fiber node owner grant external apps limited, revocable spending permissions.
  • FiberKit: Typed TypeScript/JavaScript SDK wrapper for Fiber’s JSON-RPC API, with an in-memory simulator for testing payment flows without a live node.
  • FiberPass: Payment-session infrastructure letting a wallet user create a prepaid, revocable pass with spending limits.
  • FiberPayroll: Payment-UX building blocks for Fiber, demonstrated through a working payroll app.
  • FiberX: Drop-in “Wallet Connect”-style SDK letting any web app accept and send Fiber payments without hand-rolling JSON-RPC.
  • Fikey: Non-custodial session wallet for the Fiber Network.
  • XQlyte: Payment diagnostics and confidence engine helping wallets, merchants, node operators, and agents predict payment success and get actionable fixes when it fails.

2. Node, Routing, Cross-Chain, and Diagnostics Infrastructure

  • Channel Doctor: TypeScript toolkit, CLI, and browser dashboard for safer Fiber channel operations.
  • Fiber Dev Kit (scisamir): Developer infrastructure for installing, running, inspecting, testing, and debugging Fiber nodes.
  • Fiber DevKit (AnihDev): Single Rust CLI giving developers a reproducible local infrastructure layer for building and diagnosing Fiber payment flows.
  • Fiber Diagnostics (Beebozy): Real-time health-monitoring and diagnostics dashboard for the Fiber network.
  • Fiber Doctor (Yahaya911): Diagnostic tool checking whether a Fiber node is reachable and ready to send or receive payments.
  • Fiber Flightcheck: Live payment-readiness gateway for the Fiber Network.
  • Fiber Forge (RJnr6): Local development environment for Fiber, modeled on Polar, the tool Lightning developers use to run local networks.
  • Fiber Incident Recorder (Fiber-IR): Reusable diagnostics infrastructure capturing and explaining Fiber payment incidents.
  • Fiber Lens: Payment observability and diagnostics platform for the Fiber Network.
  • Fiber Preflight (vicgunga): Payment-readiness and route-diagnostics toolkit checking whether an invoice can be paid before funds are sent.
  • Fiber Preflight (bigdella2): Payment-reliability infrastructure answering “will this payment succeed?” before it’s attempted.
  • Fiber Probe (ceciliamulandi): Rust CLI and SDK for Fiber payment diagnostics.
  • Fiber Reliability Kit: Developer infrastructure toolkit answering whether a Fiber payment can succeed before it’s sent.
  • Fiber Route Diagnostics: Diagnostic middleware and dashboard sitting between an app and its Fiber node to explain payment failures.
  • Fiber Route Doctor: Open-source operator toolkit — six composable tools sharing one engine for payment-route diagnostics and node health.
  • Fiber Test Lab: Fully local, one-command test environment for Fiber payment channels.
  • fiber-doctor (meloma_CG): Command-line diagnostic tool running automated health checks and explaining operational issues in plain English.
  • fiber-forge (menxui): One-command toolkit — “Polar for Fiber” — standing up a complete local Fiber Network with a live visual instrument panel.
  • FiberConfidence: Pre-flight reliability SDK and diagnostic tool for Fiber payment channels.
  • FiberDev Studio (lest_ton): Browser-based cloud IDE built specifically for Fiber Network development.
  • FiberGuard: AI diagnostics, monitoring, and reliability platform for Fiber nodes, shipped as a web dashboard and VS Code extension.
  • Fiberman: Developer infrastructure with reusable Java and Go SDKs and a web-based RPC explorer.
  • FiberOps: Read-only operator console and diagnostics engine for Fiber Network.
  • FiberPilot: Rust health-scoring copilot for node operators — monitors channels and peers, recommends and executes liquidity rebalancing, and alerts before problems become failed payments.
  • fiberprobe (Linnette77): TypeScript SDK answering the core question every payment-channel app needs answered: will this payment actually succeed?
  • FiberScope (craxe21): Open-source infrastructure tool for Fiber visibility, route readiness, liquidity intelligence, and payment diagnostics.
  • FiberScope (frankochris): Operator diagnostic console for Fiber Network nodes.
  • FiberTracebox: Diagnostics and observability platform turning Fiber payment attempts into structured, explainable traces.
  • Fibscope (anonivoid): Infrastructure and diagnostics platform for CKB Fiber nodes.
  • Lightr: Live diagnostics and payment-readiness platform for CKB Fiber.
  • Reef: Payment Doctor for Fiber Network: Self-hosted, read-only observability and diagnostics platform for Fiber node operators and support teams.
  • The Fiber Sidecar Protocol (FSP): Layer-2 orchestration and application framework designed to sit directly on top of Fiber Network.

3. Merchant, Liquidity, LSP, and Multi-Asset Infrastructure

  • Conduit: Lets any web API charge per call and get paid over the Fiber Network.
  • Even Keel: Channel liquidity management for Fiber node operators — the Fiber equivalent of the rebalancing tooling Lightning grew (lndmanage, charge-lnd, bos rebalance).
  • Fiber Liquidity Layer: Operability console turning a headless Fiber node into an observable, operable system.
  • Fiber LSP (Cyborgsil): Liquidity service provider daemon helping a new recipient receive a payment before they have inbound channel liquidity.
  • Fiber LSP Kit (Summerhauz): Open-source, modular toolkit for provisioning asset-specific inbound liquidity to merchants and wallets.
  • Fiber Merchant Kit (zynorlawes): Reusable merchant payment infrastructure for Fiber Network.
  • Fiber Merchant SDK (just_hallab): Reusable payment infrastructure for building merchant checkout flows on Fiber.
  • Fiber Merchant Toolkit (salmandev): Open-source merchant infrastructure toolkit providing payment confirmation and cryptographic receipts.
  • Fiber MerchantOps Core: Open-source backend infrastructure for operating merchant payments over Fiber Network.
  • Fiber Paid HTTP: Rust-first gateway and SDK toolkit turning Fiber settlement into replay-safe delivery of paid HTTP resources.
  • FiberFill: On-demand inbound liquidity (LSP) toolkit for the CKB Fiber Network.
  • FiberFlow: Self-hosted payment infrastructure letting merchants accept Fiber payments.
  • FiberGate: Self-hosted, open-source merchant payment gateway for Fiber Network.
  • FiberMeter: Reusable, Stripe-Billing-style metering infrastructure for pre-funded balances and usage-based Fiber payments.
  • FiberNuts: Cashu ecash mint settling over Fiber Network, denominated in RUSD.
  • FiberPayKit: Open-source payment infrastructure toolkit letting any developer or merchant accept Fiber payments the way they’d integrate Stripe — non-custodially, over payment channels.
  • LiquidLane: CKB-native liquidity layer for Fiber payments.
  • Sluice: Installable infrastructure making Fiber receivers payable before a payment is retried.
  • Trickle: Lets you sign off on a spending budget once, then stream tiny payments on Fiber that clear in milliseconds and stop dead at the cap you set.
  • Vert: Payment-readiness and execution-planning SDK for Fiber.
  • Zedify: All-in-one e-commerce and payment infrastructure platform for small and medium-sized merchants in Nigeria and emerging markets.

(NB: I note that 2 repositories are inaccessible as they have been set to private, I have contacted their respective owners for them to be made public)

What’s happening now: judging

Judges are now in the first round of scoring. Projects were first sorted by category and checked for completeness, and judges are now assessing each one against a standardised scoring form based on the criteria published on the campaign page. High-scoring entries will go through a second round to agree the final prize-winning positions.

Given there are 66 projects, with each requiring full consideration, we expect the winners to be announced towards the middle or end of August. As before, we’re not committing to an exact date in case further rounds are needed to reach consensus.

A reminder to participants: projects should not be edited during the judging process, as this may result in a points reduction or ineligibility for prizes. If you want to keep building, fork your project into a new repository and continue there.

Prizes

The $20,000 prize pool is split evenly across the three submission categories. Each category has three prize-winning positions:

  • 1st: $3,000
  • 2nd: $2,000
  • 3rd: $1,000

One of the category winners will then be selected as the overall best project, winning an additional $2,000 bonus. This brings the total pool to $20,000.

What’s next: Part 2

This hackathon was Part 1 of the broader Fiber builder initiative, focusing on infrastructure instead of user-facing products. Part 2 will shift focus to product and consumer solutions built on top of Fiber, hopefully putting some of the infrastructure that surfaces from this event to work in real applications. Planning for this will soon be underway. In the meantime, I wish all participants the best of luck and look forward to the results announcement.

In the meantime, we still have weekly prizes for participation in our ongoing Build on CKB campaigns: the latest one is now live. Developers can also join the Build on CKB telegram group to stay up to date and interact with other builders and CKB Devrel.

20 Likes