Fiber Dev Log 2026-10-15

[chenyukang]

Fiber’s v0.10 upgrade preparation advanced alongside invoice-settlement fixes. Ongoing work on Channel V2 and Hosted LSP addresses signing, recovery, and payment handling.

No new release was published. The merged changes below remain unreleased, and v0.10.0-rc1 still does not support upgrading an existing database.

• v0.10.0-rc1 release notes

Improvements & Fixes

Database migration for v0.10

The migration covered in the previous Dev Log has merged into develop. It adds settlement-format information to existing channel and watchtower records, preparing them for the newer software while preserving each channel’s legacy settlement format and on-chain contract.

• Add migration for commitment-contract features

Separate forwarded payments from local invoices

A fix merged into develop excludes forwarded payments from local invoice-status updates and on-chain invoice reconciliation, even when they share a payment hash with a node’s own invoice. This extends the earlier local-payment isolation work, with regression tests for forwarding and reconciliation paths.

• Scope invoice settlement to local payments

In Pipeline

Channel V2 signing and recovery

The new Channel V2 draft introduces independent signing sessions for each direction of a channel’s commitment exchange. It records signing context and protocol messages for replay after interruptions, and adds separate recovery state for cooperative closure. Existing legacy channels retain V1 behavior.

The implementation remains a draft, with crash, reconnect, and network-partition testing under review.

• Introduce Channel V2 nonce sessions

Hosted LSP recovery and payment handling

Hosted LSP work adds recovery for accepted signatures whose channel updates were interrupted, plus limits on messages buffered while waiting for a signer. Watchtower changes keep pending timeout-signing requests stable as chain time advances and prevent concurrent signer-state updates from overwriting one another.

The branch also propagates failed buffered Trampoline payments upstream and supports credential renewal with a fresh root-signer proof, preserving the tenant’s identity and channel bindings. These changes remain on the open, unmerged LSP branch.

• Hosted LSP implementation
• Recover accepted-signature operations after restart
• Handle buffered Trampoline payment failures