Repository navigation
Fiber Dev Log 2026-11-12 #1745
chenyukang
started this conversation in
Dev Log
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Updates
October 29–November 11, 2026
v0.10.0-rc2, published on November 9, includes Channel V2, Fiber’s updated protocol for signing and recovering payment-channel state. The prerelease also brings funding, settlement, and API fixes.
The updated settlement contract is now live on CKB Mainnet. Hosted LSP work remains unmerged, with support for multiple channels and assets per client under development.
Features
Channel V2 reaches the release candidate
Channel V2 provides eeach direction of a channel its own signing session. Peers can now complete their commitment exchange without an extra empty exchange.
Signing context and messages are saved for replay after a restart or reconnect, and eligible queued payment updates can share a commitment.
New channels select V2 when both peers support it, including full 32-byte payment hashes for on-chain settlement. Existing legacy channels keep V1 behavior and their original contract layout.
Commitment-lock update on Mainnet
The commitment-lock contract for on-chain channel settlement is live on CKB Mainnet as of November 9, following its prior testnet deployment.
The release updates the commitment-lock cell while retaining its existing type ID. The new binary matches the repository’s recorded checksum, delivering the updated contract required by Channel V2’s settlement format.
Improvements & Fixes
Core fixes in this section are included in rc2.
More reliable channel funding
Channel funding and the watchtower now coordinate which CKB cells they use as transaction inputs. Both reserve cells during selection and check whether pending transactions already spend them. This prevents them from selecting the same cell while the indexer still shows it as available.
If a funding transaction conflicts with another transaction in the pool, Fiber now reports the failure rather than continuing to retry.
External funding also correctly replaces placeholder signatures with actual peer signatures, enabling the initiator to submit a complete transaction.
Lighter watchtower scans
The watchtower now shares one CKB RPC client across each scan of watched channels. Reusing the client removes repeated setup work, providing a proactive optimization for nodes watching numerous channels.
Reconnect and settlement fixes
Legacy V1 channels enforce the reconnect-handshake timeout via periodic maintenance. If a peer reconnects but never sends its reestablishment handshake, eligible channels can fall back to force closing. Time spent offline does not count toward the timeout.
Payment settlement introduces two corrections. Replaying a hold-invoice settlement now finishes when fulfillment is already queued. For V1 channels, local settlement balances properly account for a payment removal awaiting an earlier acknowledgement.
Developer Experience
More consistent payment queries and notifications
list_paymentsnow filters by a payment’s status after loading stored attempts. Request forCreatedpayments no longer returns payments that are alreadyInflight. Pagination also applies its limit after filtering, so non-matching records do not use up the requested result count.Store-change subscriptions maintain continuity through write bursts. The updated delivery path passes changes directly to subscriber mailboxes, covering RPC notifications and the in-process cross-chain hub.
Cleaner dry-run logs
A successful
send_paymentdry run no longer produces a misleading “missing payment session” error. Dry runs calculate a route without storing a payment session, so the payment actor now stops once that work succeeds. The fix merged intodevelopafter rc2 and remains unreleased.Documentation navigation and loading
Two merged documentation-site updates fix internal links and redirect older URLs to their current pages. They also improve headings and page metadata.
Articles and Pulse updates can now appear while GitHub Dev Logs are still loading. On the homepage, smaller animations reduce download size, and reserved space keeps the feature section from shifting as it loads.
In Pipeline
Hosted LSP expands beyond one channel per tenant
The Hosted LSP branch introduces support for multiple channels per hosted client, including separate CKB and user-defined token (UDT) channels. It tracks readiness per channel and routes incoming payments based on the asset.
Tenants can cancel their own invoices via the standard
cancel_invoiceRPC. Hosted LSP code is optionally excludable at build time. These features remain under review.All reactions