Fiber Dev Log 2026-08-20

[chenyukang]

Updates

Following the v0.9.0 release, development is moving towards: a multi-tenant Hosted LSP design for mobile and intermittently connected wallets, follow-up fixes for on-chain TLC reconciliation, configurable peer-message protection, and continued liquidity management planning.

Meanwhile, fiber-pay has moved to the stable v0.9.0 interface; Fiber documentation has expanded with new interactive tutorials and v0.9 guides.

Features

fiber-pay v0.3.1

Released on August 14, 2026, fiber-pay v0.3.1 updates its Fiber target to the stable FNN v0.9.0 release and refreshes dependencies, with fixes for seven automated security alerts.

• Upgrade the Fiber target to FNN v0.9.0 stable
• Fix Dependabot alerts in the pnpm lockfile

Interactive tutorials and v0.9 documentation

The documentation now includes interactive tutorials for multi-hop and unidirectional payments, along with updated guides and references for Fiber v0.9.0.

• Add multi-hop and unidirectional interactive tutorials
• Update guides and references for Fiber v0.9.0

Improvements & Fixes

End-to-end test stability

Fiber restored a failing end-to-end test by switching its Bitcoin Core dependency to a stable download source.

• Use a stable Bitcoin Core URL in E2E tests

In Pipeline

Multi-tenant Hosted LSP support

A public design and WIP implementation are under review for running multiple isolated hosted tenants behind one public Trampoline node.

The model targets mobile and intermittently connected wallets, with tenant-scoped storage and authorization, real private channels over an in-process transport, durable offline payment delivery, and a remote-signer SDK boundary.

The current work remains a prototype, rather than production-ready LSP support. Remote-signer policy, crash-recoverable continuations, external-signer watchtower recovery, standalone SDK-agent E2E coverage, credential recovery, and additional acceptance testing remain open.

• Design: Multi-tenant Hosted LSP support
• WIP Hosted LSP implementation

Force-close and channel recovery follow-ups

On-chain TLC reconciliation fixes remain under review for terminal final-party sweeps and uncommitted removes. The goal is to prevent channels from remaining indefinitely in settlement-confirmed state and to ensure upstream TLC state is reconciled after force-close settlement.

A separate recovery fix would allow a channel in AwaitingChannelReady with a local commitment to force-close safely.

• Allow force shutdown while awaiting ChannelReady
• Complete on-chain TLC reconciliation for terminal sweeps and uncommitted removes

Peer admission and gossip hardening

Peer-message rate limits are being moved from hardcoded constants into a configurable policy. Defaults preserve current behavior, while operators and performance tests can tune per-peer message and byte rates, temporary bans, and global ingress budgets.

Channel-announcement validation remains under review to reject announcements whose funding cells have already been spent.

• Make peer-message rate limits configurable
• Ignore spent funding cells in channel gossip messages

Migration and installation follow-up

Installation scripts and documentation are being updated for the fnn-migrate workflow introduced with Fiber v0.9.0.

• Update install scripts and documentation for fnn-migrate

Liquidity management

This liquidity-management roadmap starts with a shared CKB/UDT asset model, on-chain swap primitives, durable order recovery, and manual Loop Out before adding Loop In, provider mode, automated planning, and multi-provider discovery.

• Design: Fiber liquidity management milestones