The members list on "Sign with the group's key" was the room's roster, and a room is not the set that can sign with its key. A member invited after the ceremony holds no share: the proposal they receive is dropped before it becomes a session on their device, and no nonce or refusal of theirs would count. The screen drew them a row anyway, in a list whose whole purpose is to say whose door to knock on. The list is now the ceremony's share holders -- the members who put a host key into it, read off DkgParticipantMessage through the new FrostSigningRepository.observeShareHolders. That is the same set FrostSigningManager places signer ids over, so what the screen lists cannot disagree with whose messages the session counts, and a ceremony cannot complete without every participant's host key, so for a completed one it is the whole participant set. Names still come off the room, in the room's order; a share holder the room no longer holds keeps a placeholder row, since their share did not leave with them. The view model follows the session to its ceremony with flatMapLatest, and the list is empty until the ceremony has been read rather than falling back to the room -- a fallback would flash everybody and then correct itself. Co-Authored-By: Claude Opus 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…