Gm guys.
I built Fiber Forge to make local Fiber development faster and easier. It won first place in
Category 2 (Node, Routing & Diagnostics) at the Gone in 60ms hackathon.
Testing a Fiber application locally normally involves several manual steps: starting a CKB dev
chain, mining blocks, funding addresses, creating a configuration file for every Fiber node, connecting the nodes as peers, and opening channels through JSON-RPC. That setup takes time, and it has to be repeated whenever you need a fresh network.
Fiber Forge automates the entire process. Run:
npx @truthixify/fiber-forge up trio
In under a minute, you get a working three-node network with funded nodes, open channels, and a live web interface. From the interface, you can:
- send payments between nodes;
- open and close channels;
- inspect channel balances and states; and
- follow each node’s logs in real time.
You only need Docker running and Node.js 20 or newer. Fiber Forge downloads the required CKB and Fiber images on the first run.
The trio preset is just the starting point. Fiber Forge also includes duo and hub presets,
parametric topologies such as line:N, ring:N, and star:N, and support for custom YAML
topologies. You can create both CKB and UDT channels, run scripted payment scenarios, and keep multiple isolated networks running at the same time.
The GUI and CLI are designed to work together: every action in the GUI shows its equivalent CLI command, and every command that reads data supports --json. You can explore a network visually, then use the same operations in scripts or CI.
Fiber Forge is open source: GitHub - truthixify/fiber-forge · GitHub
If you are building on Fiber, try it against your application and let me know what breaks. Bug
reports, feature requests, and new topology ideas are welcome.