CKB · Fiber Network Payment toolkit

Payments,
from node to interface.

Build on Fiber without stitching the stack together yourself. Use one typed SDK for payment logic, polished React primitives for the browser, and a CLI designed for both people and agents.

Try FiberNodeButton live Explore the toolkit

Real CKB testnet
Browser-hosted node
Typed end to end

Live reference

Don’t imagine the integration. Run it.

Open the actual FiberNodeButton, start a browser-hosted node, and inspect the full component workflow against CKB testnet. No mocked balance, no simulated state.

01 Passkey and password startup
02 Asset-aware channel controls
03 Diagnostics and live events

RUNNING ON VERCEL FiberNodeButton
live preview Launch demo

React-first SDK

A payment interface with the hard parts already wired.

Start with a production-ready component, then drop down to hooks and typed SDK APIs only when your product needs more control.

FiberNodeButton: Node lifecycle, channels, assets, diagnostics, and extensible tabs.
FiberPayQuickCard: A compact path from invoice to completed payment.
useFiberNode: Controlled browser-node state for custom interfaces.

Read the React package docs

WalletPanel.tsx REACT

import {
  FiberNodeButton,
  useFiberNode,
} from '@fiber-pay/react';

export function WalletPanel() {
  const fiber = useFiberNode({
    network: 'testnet',
    walletId: 'my-app',
  });

  return (
    <FiberNodeButton
      fiber={fiber}
      strategy="passkey"
    />
  );
}

REAL COMPONENT 13 LINES

Operator CLI

Node operations that read cleanly in a terminal or an agent trace.

01 fiber-pay node start --json NODE READY

02 fiber-pay channel open ... CHANNEL OPEN

03 fiber-pay payment send ... PAYMENT SENT

04 fiber-pay l402 proxy ... API METERED

Launch and inspect nodes, manage channel lifecycle, send payments, and put an L402 paywall in front of an existing HTTP API. Stable JSON output keeps every workflow automatable.

Profile-aware local runtimes
Channel and liquidity operations
Background jobs, logs, and health checks
Agent-facing calls and L402 proxying

Read the CLI docs

One stack, three entry points

Start where your product is.

UI Ship a payment surface
Use React primitives for the shortest path into a browser app.
SDK Own the product logic
Compose typed payments, channels, funding, and security policies.
CLI Automate the runtime
Run repeatable Fiber operations locally, in CI, or through an agent.

Ready on testnet

See the component work.
Then make it yours.

Open live demo View on GitHub