A co-signer keeps a ledger per funding output now (schema 35: IcebergChannelLedger keyed by output, with its index, the parent it spent and the purchase that let it). A commitment on an output it has no ledger for is the first commitment on a splice's new one: it must follow the newest output by one index, rebuild from its context, and open from the parent's ledger at the same number with the same HTLCs, the group's balance lower by no more than an open buy-liquidity authorisation's fee cap (CoSignerPolicy.openSplice). The shared input is then held to that authorisation: it spends the pinned output, makes one new output of the group's key with the LSP's under the cap, buys the amount the group named, is paid from the channel balance alone, costs what the first commitment took to the msat and no more than the cap, and the LSP puts in what it is paid for. An authorisation is bound to the parent of the first splice it let, so however many attempts there are, one confirms. While two outputs are live a payment settles on both at one commitment number; each ledger records what its last commitment consumed, and a sibling spends only the difference. Before this the second commitment was refused as under its floor. GroupLightningSpliceCoSigningJvmTest, seven four-device tests on regtest and mainnet: a purchase the group signs and the script interpreter accepts, payments over both live outputs, and each refusal. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This is a Kotlin Multiplatform project targeting Android, iOS, Desktop (JVM).
-
/composeApp is for code that will be shared across your Compose Multiplatform applications. It contains several subfolders:
- commonMain is for code that’s common for all targets.
- Other folders are for Kotlin code that will be compiled for only the platform indicated in the folder name. For example, if you want to use Apple’s CoreCrypto for the iOS part of your Kotlin app, the iosMain folder would be the right place for such calls. Similarly, if you want to edit the Desktop (JVM) specific part, the jvmMain folder is the appropriate location.
-
/iosApp contains iOS applications. Even if you’re sharing your UI with Compose Multiplatform, you need this entry point for your iOS app. This is also where you should add SwiftUI code for your project.
Build and Run Android Application
To build and run the development version of the Android app, use the run configuration from the run widget in your IDE’s toolbar or build it directly from the terminal:
- on macOS/Linux
./gradlew :composeApp:assembleDebug - on Windows
.\gradlew.bat :composeApp:assembleDebug
Build and Run Desktop (JVM) Application
To build and run the development version of the desktop app, use the run configuration from the run widget in your IDE’s toolbar or run it directly from the terminal:
- on macOS/Linux
./gradlew :composeApp:run - on Windows
.\gradlew.bat :composeApp:run
Build and Run iOS Application
To build and run the development version of the iOS app, use the run configuration from the run widget in your IDE’s toolbar or open the /iosApp directory in Xcode and run it from there.
Learn more about Kotlin Multiplatform…