feat: ldk-node serializable types

[ovitrif]

This PR uses the new serializable types generated in ldk-node PR:

• feat: serializable types in android bindings ldk-node#16

Preview

Transfer	Bolt11	Peers
regtest.mp4

QA Notes

Since this PR changes the balance calculation to use the ldk-node types directly instead of the previous setup with mapping them to a domain model, a regression test for transfer-to-spending & back to savings is recommended, alongside the main core test to build & run, which verified for no compilation or runtime issues.

Then, we also need to check the 2 impacted areas:

• bolt11 strings, which had to be fixed in gobley
• peer details & CJIT startup, because we replaced custom LnPeer type with direct use of PeerDetails

Tests:

1. Transfer to spending & back to savings, check incoming transfer UI still works as expected
   • after LN channel is ready > Receive > Swipe > expect bolt11 string is ok
2. Drawer > App Status > Lighting Node > scroll down > expect peer uri listed
3. On wallet with no LN funds > Receive > Tap Receive on LN > expect cjit not geoblocked

[Copilot]

Pull Request Overview

This PR migrates from custom domain model types to serializable types from the updated ldk-node library, eliminating the need for manual type conversions. The change simplifies the codebase by using ldk-node's native types directly instead of maintaining separate domain models.

Key changes:

• Replaced custom LnPeer, BalanceDetails, and LightningBalance domain models with ldk-node's native PeerDetails, BalanceDetails, and LightningBalance types
• Added extension functions for PeerDetails to provide convenient access patterns and parsing functionality
• Updated all references throughout the codebase including services, repositories, ViewModels, and UI components

Reviewed Changes

Copilot reviewed 22 out of 22 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
gradle/libs.versions.toml	Updated ldk-node dependency version to v0.6.2-rc.4
app/src/main/java/to/bitkit/models/LnPeer.kt	Removed custom LnPeer domain model class
app/src/main/java/to/bitkit/models/BalanceState.kt	Removed custom BalanceDetails and LightningBalance domain models with mapping functions
app/src/main/java/to/bitkit/ext/PeerDetails.kt	Added extension functions for PeerDetails parsing and property access
app/src/main/java/to/bitkit/services/LightningService.kt	Updated to use ldk-node types directly instead of domain model conversion
app/src/main/java/to/bitkit/repositories/LightningRepo.kt	Updated method signatures and state management to use ldk-node types
Multiple ViewModels and UI files	Updated type references from domain models to ldk-node types
Multiple test files	Updated imports and mock objects to use ldk-node types

Comments suppressed due to low confidence (1)

app/src/main/java/to/bitkit/ui/screens/wallets/HomeScreen.kt:1

• This code block appears to be duplicated and should be part of the extracted Widgets composable function. The structure suggests this was moved but some trailing code wasn't properly cleaned up during the refactoring.

package to.bitkit.ui.screens.wallets

[Copilot]

Pull Request Overview

Copilot reviewed 32 out of 32 changed files in this pull request and generated 4 comments.

Comments suppressed due to low confidence (1)

app/src/main/java/to/bitkit/services/LightningService.kt:1

• [nitpick] Logging peers with '$peer' relies on PeerDetails.toString(); using peer.uri would produce a consistent, readable 'nodeId@host:port' format matching other areas. Suggest: Logger.info("Connected to trusted peer: ${peer.uri}").

package to.bitkit.services

[jvsena42]

Tested channel operations and LN node peer URI

[ovitrif]

@jvsena42 need one final re-approval after last merge with master.