The Lightning wallet now opens on the node's own network, mainnet, where the group's onchain wallet already is, so the separate testnet3 onchain wallet and its row on the group's screen are gone. GroupLightningRollout.allows takes mainnet and regtest, nothing else. This lifts the plan's mainnet gate by decision, ahead of its condition: an outside review of the Iceberg scheme and the DKG, and a month on testnet3. The LSP's signing deadline was never measured either. Meanwhile: - Every co-signer refuses to sign for a mainnet channel over MAINNET_CHANNEL_CAP, 1,000,000 sats, so a bigger one never opens; none grows, since splices are refused. - The opening screen says the scheme is unreviewed and names the cap. Running the co-signing suite on mainnet (now a second test class) found a bug that would have stopped everything there: every key manager was built with a testnet swap-in tpub, which lightning-kmp rejects on mainnet. That covers every co-signer and the operator's node. Mainnet now takes the mainnet LSP's published xpub; nothing derives from it. The full JVM suite (1,578 tests) and the regtest run pass. 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…